Replay-to-refresh

Click Replay. Refresh every screenshot. Done.

The Workflow Replay loop: Capture, Polish, Share, Replay, Refresh.A horizontal flow of five states. Capture, Polish, and Share form the standard pipeline. Clicking Replay triggers Refresh, which rehydrates every screenshot against the live product and loops back into Share to keep the workflow current.Auto refresh on every product releaseeditpublishclickrunCapture: Chrome extension records clicks, inputs, navigation, and full-page screenshots.01CaptureClicks, inputs, screenshotsPolish: Annotate, redact, and reorder steps in the visual editor.02PolishAnnotate, redact, reorderShare: Secure read-only link or self-contained offline HTML export.03ShareLink or offline HTMLReplay: A user clicks the Replay button on the workflow.04ReplayOne click triggers itRefresh: Every screenshot rehydrates against the live product in seconds.05RefreshEvery screenshot rehydrates
Capture once. Click Replay any time. Every screenshot rehydrates against the live product in seconds.

Every other documentation tool gives you a snapshot. We give you a runnable artifact. Open any workflow from your Workflow Replay dashboard, click Replay, and we open a real browser, execute every captured step against your live product, and rehydrate every screenshot in seconds. No re-record. No re-click. No second tool. Click Replay → workflow is fresh.

Why static guides rot

The average team now uses 150 SaaS applications, up from 20 a decade ago. Every one of those vendors ships UI changes weekly, and every change quietly breaks a screenshot somewhere in your docs. Static-guide tools fix it the only way they can: re-record the entire workflow from scratch.

What happens when you click Replay

Workflow Replay opens a real browser, walks the captured steps against the live product, re-captures every screenshot, and writes the fresh result back to the workflow. Share links and exports automatically reflect the new screenshots.

Selector resilience

Multi-strategy element resolution — accessible name → role+text → semantic XPath → DOM hash → coordinate fallback — keeps the replay completing even when selectors shift. When a step does need attention, we flag exactly which one.

Visual diffing

See exactly what changed step-by-step between the old screenshots and the freshly captured ones.

You decide when to refresh

Refresh after a vendor release, before a customer training, when an author flags drift. Replay is user-triggered — the execution is automated, but the trigger is always you.

Side-by-side: stale vs fresh

Same workflow, captured 90 days ago and rehydrated by one click of Replay.

Replay Updated· just now
Captured 90 days ago
After a single Replay click

Stop maintaining docs by hand.

Install the Chrome extension in one click. Capture your first workflow in 60 seconds. From there, one click on Replay keeps it current — forever.