What's new

Claim links transfer a demo to another account in one click. Record a demo for a client or teammate, send them a single-use claim link, and ownership moves to their account when they accept — no shared logins, no re-uploading.

Claim links ship with the new Company tier, built for teams and agencies producing demos for others.

The demo editor now has a Tour mode that shows exactly how your recording projects onto a live guided tour: which steps are included, what each spotlight will anchor to, and the copy users will read.

• Per-step include toggles — keep a step in the screenshot demo but drop it from the tour.
• Tour copy overrides — the callout that works next to a screenshot isn't always the one that works on the live page; override tour text without touching the demo.

Blurred regions are burned into the screenshots the public receives. The served image contains the blurred pixels — not an overlay drawn on top — and the untouched originals stay vaulted behind owner-only access.

Public demos also don't carry typed-input captures unless you explicitly opt a demo into tours. What you redact is what everyone gets, including anyone who opens the image URL directly.

Live guided tours grew up fast:

• Analytics funnel — see where users start, advance, and drop off, step by step.
• Cross-page resume — tours survive full page navigations, so multi-page flows work end to end.
• Drift-tolerant anchors — if your UI changed since recording, fallback anchors keep the tour attached instead of breaking on the first moved selector.
• stepshots tour export — inspect and version the guided-tour track derived from a recording.
• Select-element steps can advance the tour on change, and first-run auto-start is built in.

Any recorded demo can now drive a live guided tour on your actual site. Paste one script tag on your page, and Stepshots spotlights each recorded step in sequence — a "light the way" overlay that walks users through the real UI instead of showing them screenshots of it.

Tours run once per browser by default so returning visitors aren't nagged, and every tour is derived from a demo you already recorded — no separate tour builder to maintain.

• Recordings now follow tabs opened by target="_blank" links. Flows that jump to a new tab — OAuth consents, external checkouts, docs links — record as one continuous demo instead of stopping at the tab boundary.
• React SDK 0.3.0 — embed demos as a component with typed props instead of hand-rolling the iframe.

stepshots verify replays your tutorials against the live app without writing a bundle — if the UI drifted and a step can't complete, it fails with a report. Wire it into CI with --fail-on and you'll know a demo broke before a customer does.

Also in this release:

• stepshots schema prints a JSON Schema for stepshots.config.json — editors autocomplete and validate your config.
• list, doctor, and shell completions commands.
• upload --public publishes a demo in one step.
• Persistent browser profiles for recording behind a login.

• stepshots login opens your browser and signs the CLI in via OAuth — no more copying API keys around. logout and whoami included.
• Screenshots are now WebP, cutting bundle sizes roughly in half without visible quality loss.
• One-line install script — grab the CLI with a single shell command (see the installation docs).
• Recordings now track annotation drift, so you hear about selectors that moved before your screenshots go stale.

First public release. Record clickthrough product demos two ways:

• CLI — describe the flow in stepshots.config.json, run stepshots record, get a .stepshot bundle of annotated screenshots recorded in a headless browser. Deterministic and repeatable.
• Chrome extension — click through your app in your own browser; every click becomes an annotated step.

Upload either to the dashboard to edit, share, and embed.