# Loading State

A loading state communicates that work is in progress, preserves context, and sets an honest expectation while content or an operation is not ready.

- Type: artifact
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/loading-state/>)

## What it means

A loading state is the temporary interface between an initiated request and a usable result. It may use immediate feedback, progress indicators, skeleton structure, retained content, or staged rendering. The right pattern depends on duration, predictability, importance, and whether people can safely continue other work.

## Why it matters

Without timely feedback, people may assume an action failed and repeat it. Good loading behavior reduces uncertainty, supports continuity, and makes real progress accessible without blocking more of the interface than necessary. Performance still matters: a polished spinner does not reduce latency.

## When to use it

Use loading states for navigation, fetching, uploads, processing, saves, and asynchronous work. Define the threshold and pattern per operation: brief work may need control feedback, while longer or measurable work benefits from progress, cancellation, backgrounding, or notification.

## How it works

1. Acknowledge the action immediately where it began.
2. Keep useful existing content visible when it is not stale or dangerous.
3. Use determinate progress when measurable; otherwise use restrained indeterminate feedback.
4. Expose status programmatically without repeatedly interrupting screen-reader users.
5. Handle slow, offline, canceled, timed-out, successful, and failed outcomes explicitly.

## A practical example

During a video upload, the selected file appears with name, size, percentage, and cancel action. The library remains usable. Processing is a separate stage, and completion is announced once. If the network drops, retry resumes rather than restarting silently.

## Where it breaks

Indeterminate animation cannot tell people how long work will take, and fake precision damages trust. Blocking overlays trap users during background work. Frequent live updates create noise, while elaborate loaders consume CPU and data. Optimize requests, caching, and rendering before polishing the wait.

## Common mistakes

- Showing a full-page spinner for a small local update
- Replacing useful content with a loader during refresh
- Announcing every progress tick or ignoring reduced motion

## Sources

1. [Loading pattern](<https://v10.carbondesignsystem.com/patterns/loading-pattern>) — Carbon Design System · Institutional design system
2. [Understanding SC 4.1.3: Status Messages](<https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html>) — W3C Web Accessibility Initiative · Accessibility guidance

## Related topics

- [Skeleton Screen](<https://wiki.soroush.uk/topic/skeleton-screen/>)
- [Optimistic UI](<https://wiki.soroush.uk/topic/optimistic-ui/>)
- [Error Recovery](<https://wiki.soroush.uk/topic/error-recovery/>)
