Skip to content

Scroll Progress Rail

A reading-progress line pinned to the top of a scroll container, with a side gauge for long pages. Barely code, instantly useful on docs and articles.

1.1k
MIT licensev1.0.01.8 KB gzipzero dependenciesby Motif Studioadded 2026-09-08review due 2026-12-07
Live playground — drag, click, hoversandboxed previewsample copy
Article · scroll to read0%
Post 01reading time · 180s
Post 02reading time · 194s
Post 03reading time · 208s
Post 04reading time · 222s
Post 05reading time · 236s
Post 06reading time · 250s
Post 07reading time · 264s
Post 08reading time · 278s
Post 09reading time · 292s
Post 10reading time · 306s
Post 11reading time · 320s
Post 12reading time · 334s
Post 13reading time · 348s
Post 14reading time · 362s
Post 15reading time · 376s
Post 16reading time · 390s
Post 17reading time · 404s
Post 18reading time · 418s
Post 19reading time · 432s
Post 20reading time · 446s
Post 21reading time · 460s
Post 22reading time · 474s
Post 23reading time · 488s
Post 24reading time · 502s

— scroll inside this window —

Ambience
vibes

Ambience is a live light wash over the preview. Full palette re-theming of every demo arrives with Theme Studio (Pro).

deps: zeroJSX + TailwindMIT · original
scroll-progress.tsx
// React — progress = scrolled / scrollable, driven by one onScroll
const el = scroller.current;
const max = el.scrollHeight - el.clientHeight;
setProgress(max > 0 ? el.scrollTop / max : 0);

<div ref={scroller} onScroll={handle} className="overflow-y-auto …">
  {content}
</div>
<div style={{ transform: `scaleX(${progress})`, transformOrigin: "left" }}
     className="fixed top-0 left-0 right-0 h-1 origin-left bg-gradient-to-r …" />

Snippet provenance

lines 1–10 · v1.0.0
v1.0.0Motif Studio2026-09-08the only version the catalog records for this asset

No changelog entry mentions “Scroll Progress Rail”, so the catalog records a single version for it.

Every line above is attributed to the single version this catalog records — we keep no per-line history, so no per-line attribution is invented. See the provenance page for the rule and the gaps.

Review notes · anchored to code lines

Threads attach to a line number in this asset's snippet, so a remark about the focus trap stays next to it.

demo · stored in this browser

Loading notes…

The snippet on this page is 10 lines long, so anchors run 1–10. Notes are per-asset and per-browser; a shared review thread is a server feature, and this panel is the local stand-in that proves the anchoring works.

Design notes from the studio

Why it works — Reading progress is the cheapest 'this page respects your time' signal a docs site can ship.

The idea — Use scaleX instead of width% on every scroll event — compositor-only, zero layout thrash.

When to skip it — Skip it on marketing pages where the page is shorter than two screens; a near-instant bar reads as broken.

Dependency-aware copy: zero packages to install — paste and run. All markup is original Motif UI content (MIT).

Course rail — understand it before you ship it

Theme Studio preview

Theming example — two token themes

Assets are token-driven (100% design-token driven). Here the same scene runs under two theme presets from the token sheet.

Midnight / violet
Article · scroll to read0%
Post 01reading time · 180s
Post 02reading time · 194s
Post 03reading time · 208s
Post 04reading time · 222s
Post 05reading time · 236s
Post 06reading time · 250s
Post 07reading time · 264s
Post 08reading time · 278s
Post 09reading time · 292s
Post 10reading time · 306s
Post 11reading time · 320s
Post 12reading time · 334s
Post 13reading time · 348s
Post 14reading time · 362s
Post 15reading time · 376s
Post 16reading time · 390s
Post 17reading time · 404s
Post 18reading time · 418s
Post 19reading time · 432s
Post 20reading time · 446s
Post 21reading time · 460s
Post 22reading time · 474s
Post 23reading time · 488s
Post 24reading time · 502s

— scroll inside this window —

--accent 262 · dark surfaces

Bone / amber
Article · scroll to read0%
Post 01reading time · 180s
Post 02reading time · 194s
Post 03reading time · 208s
Post 04reading time · 222s
Post 05reading time · 236s
Post 06reading time · 250s
Post 07reading time · 264s
Post 08reading time · 278s
Post 09reading time · 292s
Post 10reading time · 306s
Post 11reading time · 320s
Post 12reading time · 334s
Post 13reading time · 348s
Post 14reading time · 362s
Post 15reading time · 376s
Post 16reading time · 390s
Post 17reading time · 404s
Post 18reading time · 418s
Post 19reading time · 432s
Post 20reading time · 446s
Post 21reading time · 460s
Post 22reading time · 474s
Post 23reading time · 488s
Post 24reading time · 502s

— scroll inside this window —

--accent 40 · paper surfaces

90-second read

Usage recipe — where this fits

Use it as the signature of a single screen — a hero backdrop, an entrance, a transition. One signature per screen; everything else stays quiet.

Compose it with calm content around it: the motion earns attention only when the layout does not compete for it.

belongs in animatedscroll behaviour

Cost honesty

Performance note

1.8 KB gzipcompositor-boundmotion runs on transform/opacity layers; the cost scales with layer count and blur radius.

Cheaper alternative — the static preview variant removes the animation loop and keeps the layout — a quieter, cheaper sibling.

What it needs

Browser support strip

CSS transformsopacity compositingcustom propertiesprefers-reduced-motionwill-changeall evergreen browsers

No polyfills ship with the asset — if a listed feature is missing in a target browser, the graceful fallback is the static layout.

prefers-reduced-motion

Reduced-motion fallback

With prefers-reduced-motion: reduce, the animation loop and travel are removed; state changes keep working through opacity and colour (≤ 300ms). The demo you see above honours the switch — try it in your OS settings and the loop will quiet down.

Design rule: the reduced branch is a second design, not a stripped page — every state change stays visible.

Pressable step-through

Keyboard walk demo

Step through what a keyboard user experiences with this asset.

1

Tab to the scene — motion is paused or non-essential for keyboard users

Auto-suggested

Composition map — what pairs well

One original micro-case

Inspiration context

The hero that held attention for one beat longer

A marketing page's hero used a stock fade-in that finished in 200ms — invisible to the eye, useless to the story. Re-timed with a slow settle (0.6s, ease-out-quart) and one typographic wipe, the hero read as 'alive' without a single new asset. The change was purely a curve and a delay.

Written in-house — no screenshots, no borrowed imagery. The pattern, not the pixels.

Every version, why

Changelog — this asset

v1.0.02026-09-08

Current release — this page documents the asset as shipped.

v1.0.02026-08-18

Token pass: colours and radii moved to the design-token sheet; a11y score raised to the current bar.

v0.1.02026-07-02

Initial release to the library — original markup, MIT licensed.

30-day sparkline

Copy history

1,150copies this month

Sample series from this asset's usage fingerprint · last 12 days shown.

Future queue

Community remixes

Queue opens after launch. Remixes arrive as alternate versions of this asset — same job, different voice — submitted by users and audited by the studio before they appear beside the original.

0 remixes yetaudited by studiocredit + link back to the remixer

Star / favourite

Save this asset

Your collection is stored in this browser (localStorage) — no account needed.

Build a page around it

Pairs well with a prompt

This asset belongs inside a bigger build — here is the prompt that would generate a page containing it:

Motion-spec page — the animation before the layout

Spec sheet · Timing table · Easing curves

beta

Exact tree

Bundled dependencies — disclosed

scroll-progress.tsx0.4 KB raw · ~1 KB gzip
(no runtime dependencies)the CSS ships with the snippet

Full snippet ≈ 0.6 KB raw, ~1 KB gzip — before any framework you already load.

Download

Export as single file

Grab the asset as one file, ready to paste into your project.

Files are generated in your browser from the snippets on this page — nothing leaves the tab.

Scale, not clutter

Sizing system — three densities

Density is a token decision, not a per-page override — pick one density per product surface and hold it. Active: Default.

Runnable copy

Open in a sandbox

Opens this asset in a new tab with its stylesheet injected — a real, editable HTML document in your browser. No account, no upload.

If the tab is blocked, use the single-file export instead — same content, saved locally.

Written version first

Tutorial transcript

This asset does not have a video yet — so the written version stands in: the code line walk below narrates the snippet line by line, and the design rationale on this page explains the default decisions. When a video ships, this exact panel hosts its full transcript.

video: not yettranscript: line walk belowformat: markdown, searchable

Annotated snippet

Code line walk

The lines that matter, with the reason they matter. Click one:

Trade-off, visible

Size vs. quality slider

~2 KB~6 KB~12 KB

Standard · CSS + hover states

~6 KB

adds transitions, focus-visible and reduced-motion rules

The slider is honest: the slim tier has no JS, the pro tier pays for behaviour. Start slim, upgrade only the surfaces that need it.

HTML → React, priced

Stack-switch cost note

Taking the HTML/CSS version into a React component costs real work — and the cost is predictable:

Event wiring

Hover, focus and click become handlers — the CSS stays, the state appears.

Props for the knobs

Every inline value that should vary becomes a prop with a default — the defaults must match the CSS exactly.

The estimate

A clean port of this asset is 20–45 minutes for a React developer — the 138-character stylesheet is the easy half.

Find it the way you say it

Tag synonyms

Search on this site resolves synonyms globally — "dropdown", "select" and "picker" land on the same asset, so you never need to know the catalog's internal vocabulary.

When to pick which

Sibling comparison

Data table — data table
CompareScroll Progress RailAurora VeilHalo Trail
KindAnimatedAnimatedAnimated
Bundle1.8 KB gzip2.6 KB gzip5.8 KB gzip
a11y99/100100/10093/100
Dependenciesnonenonenone
Copies / mo1,1508,9406,330
Interactionsscrollscrolldrag, hover

The honest verdict — Scroll Progress Rail is the lighter default here; reach for Aurora Veil when its extra weight buys an interaction this one lacks.

Read next — two guides and a prompt

picked by tag overlap, not by hand

How these three were chosen: essays scored on shared tags (2 and 1 matches), then prompt scored on block/vibe overlap (0 matches). The rule lives in src/lib/spine.ts, so the same asset always links to the same three pages and a second reader can reproduce the choice.

Was this helpful?