Progress Bars

Progress bars are tracks with a fill that report where something stands as a share of a whole the reader can see. The five compositions here stretch that further than a loading bar. A stepped compression control lands a square knob on one of five stops, a spending meter runs a second bar behind the first, a semicircular ring of segments carries a level stepper, an intensity bar is scaled from low to high, and a dial reads its highlighted arc as an angle.

What separates them is who owns the value. Every one of these can be dragged or stepped, which makes them controls that happen to look like meters, and a control owes things a readout does not: a handle you can see, keyboard steps, and a value read back as a number. The inverse matters more. A quota meter is not progress. Nothing is completing, so a full bar means the ceiling has been hit, and drawing that like a finished download says the opposite of the truth.

20 blocks

Compression Progress Bar

File compression, quality sliders, stepped settings

Compression, shrink

One file compressed to a chosen level, where the size is the story

Compression, queue

Batch jobs where every file has its own progress

Spending Progress Bar

Budgets, quota meters, usage-vs-limit dashboards

Spending, pace

Budgets where the date matters as much as the amount

Spending, allowance

Budgets that should answer how much can I spend today

Graph Progress Bar

Capacity dials, radial KPI meters, goals counted per period

Graph, history

A KPI that should show its shape over the period

Graph, versus

A KPI judged against the same point of last period

Intensity Progress Bar

Sensitivity controls, difficulty sliders, effect strength

Intensity, auto

Settings a device can tune itself, with a way to take over

Gauge Progress Bar

Roll/tilt indicators, telemetry dials, vehicle dashboards

Gauge, horizon

Orientation readouts where the vehicle itself should tilt

Gauge, level

Two-sided readings where the worst case matters

Usage against a target

Plan limits and quotas, where the target matters as much as the cap

Usage against a target, pace

Quotas where the date decides whether usage is a problem

Usage against a target, set the target

Setting several quota targets in one place

Readings in their normal range

Lab results and any reading judged against its own reference range

Readings, one ruler

Panels where how far out each reading is matters more than its unit

Readings, trend

Results followed over time, where the direction matters

01

Using Progress Bars

Reach for it when

  • A multi-step flow where the person should see how many steps remain
  • A quota or budget shown against the ceiling it is measured from
  • A setting with a continuous range whose value is worth reading back
  • A single operation whose total size is known before it starts

Reach for something else when

  • The total is unknown: a spinner or an elapsed counter is honest where a guessed fill is not
  • You are comparing several values against each other. That is a bar chart
  • The exact number matters to the person setting it: pair the track with a number field or a stepper
02

Where it shows up

01

Storage and seat quotas

An account page showing space used against the plan's ceiling, with a second bar behind the first for what is pending. The footer states both figures so nobody has to estimate the fill by eye.

02

Checkout step meter

A multi-step purchase or signup where the bar answers the only question anyone has at step two, which is how many more there are. Steps are countable, so the fill is exact rather than estimated.

03

Compression settings

Export and encoding dialogs where quality is picked along a handful of named stops rather than a free range. The knob lands on a stop and the readout names it, so the value is never stranded between two labels.

04

Telemetry dials

Vehicle and robotics dashboards where a value swings around a centre instead of filling from zero. The arc reads as an angle, and the stepper beside it lets the same control be nudged by hand during setup.

03

Questions

When should a progress bar be used instead of a spinner?

Use a progress bar when the total is known and the fill can be trusted: a file of known size, a form with a fixed number of steps, a quota against its limit. Use a spinner when there is no total to divide by. A bar whose fill is guessed is worse than a spinner, because it makes a promise about time that it then breaks.

How do you make a progress bar accessible?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.