Menu Home
ProductReplay & DevToolsSignalsCall qualityWhy (AI)Live AssistCanvas recordingPrivacy & complianceSelf-hosted
SolutionsHealthcare & virtual careEngineeringSupportProduct teamsKiosks & monitoring
MorePricingDocsCompareTrust centerGlossaryAboutContactPress kit
Log inStart free
Replay & DevTools

Full DevTools for a session that already happened.

Backstory does not record video. It captures the DOM and every change to it, then rebuilds the page in a sandboxed player with the panels an engineer expects, all synchronized to the scrubber.

Signals 0 fired

    Why generated from this session

    Loading explanation…

    A synthetic checkout session. Watch the promo-code struggle, the slow request, and the layout shift that displaced a click.

    How it works

    Structure, not pixels.

    1. Snapshot DOM tree with stable ids
    2. Mutations every change, coalesced per frame
    3. Interactions pointer, input, scroll, navigation
    4. Context console, network, errors, vitals
    5. Mirror sandboxed reconstruction
    A full snapshot starts each checkpoint; mutations replay on top of it. Seeking jumps to the nearest checkpoint and rolls forward, so a four-hour segment seeks in under 300 ms.
    Correct or honest

    If the recorder had to shed data under memory or bandwidth pressure, the replay shows a hatched gap with the reason instead of a wrong picture.

    Checkpoints

    A fresh snapshot every five minutes, on heavy route changes, and at segment boundaries keeps seeking cheap and recovery possible.

    Asset archive

    Stylesheets, fonts, and images are archived per release, so replays stay correct after your next deploy.

    Panels

    Everything DevTools shows, for the past.

    Elements

    Inspect the reconstructed DOM at any instant: computed styles, box model, attributes, shadow roots. Copy a selector or find every session that clicked it.

    Console

    Every log with stack traces symbolicated through your uploaded source maps, plus a server tab with correlated backend logs.

    Network

    A waterfall synchronized to playback, GraphQL operation names, WebSocket frames, and the backend span tree under each request.

    Performance

    Web Vitals with attribution: the LCP element is highlighted, layout shifts are drawn as rectangles, the INP interaction is marked.

    State

    Redux, Zustand, Pinia, NgRx, TanStack Query, Apollo. Click an action and the replay jumps to it.

    Application

    Storage keys, cookie names, service worker state, routes, feature flags, experiments, release and device.

    Accessibility

    An axe-style audit of the reconstructed DOM at any time, focus order, missing labels, contrast failures.

    Issues & Why

    Every Signal in the session with a jump-to, and the AI explanation for any moment you select.

    Fidelity

    What we test, so you do not have to.

    Nightlyseven real public pages are recorded and replayed in Chrome and in Safari's engine, then compared with the live page. Firefox runs in the same check.
    97%+of the live page's text is in the replay, and element counts stay within 12%. Pixels differ by 0–20%, mostly third-party frames and fonts the page did not let us fetch.
    34 KBgzipped SDK including console, network, vitals, consent, and sampling. The recording worker loads separately.

    The story behind every bug.

    Free for 1,000 sessions a month. Strict masking, conditional recording, and Signals are all included.

    Get started

    Replay your first session in five minutes.

    Free for 1,000 sessions a month, no credit card. Or leave a work email and we will reach out about the private beta for healthcare and support teams.