> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cognite.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Progress

> Shows how far through a task or process the user is. Use when completion is measurable and expressing it as a percentage or fraction is meaningful to the user.

## Progress

<Badge color="blue">v1.0.0</Badge> | [View in Storybook](https://master--695bb4b1b8041ae09768950a.chromatic.com/?path=/docs/primitives-progress--docs)

### When to use

* Multi-step flows where the user benefits from knowing how much is left (uploads, installations, form wizards).
* Long-running operations where a percentage or step count can be calculated.
* To indicate storage or data usage.

### When to use something else

* Unknown duration: use [Page loader](/aura-design-system/primitives/page-loader) / skeleton / shimmer patterns instead of a fake percentage.
* Very fast operations (under \~1s): skip the bar to avoid flicker.
* Decorative metrics: use charts or static labels, not a determinate progress bar.

### Dos and don'ts

* Do pair with a label that describes what's in progress — "Uploading files" is more useful than a bar alone.
* Do update the value in real time if possible; a static progress bar reads as broken.
* Don't reset to 0 and run again to imply ongoing activity — use [Page loader](/aura-design-system/primitives/page-loader) / indeterminate patterns for unknown completion.
* Don't use multiple progress bars in close proximity unless each clearly maps to a distinct parallel operation.

### Behavior

* If the operation can be canceled, provide a cancel action alongside the bar — not after it completes.
* Avoid showing a percentage if the underlying estimate is unreliable; or show a step indicator ("Step 2 of 4") instead.

### Often used with

* Visible status label; optional cancel [Button](/aura-design-system/primitives/button); pairs with [File upload](/aura-design-system/primitives/file-upload) or long jobs.