Start free

Session replay for bug reports

See the minutes before a user wrote to you: clicks, navigation, rage clicks and the console at the moment it broke. Inputs are always masked.

Start free See the exact behaviour

Included on every plan · the plan caps how long replays are kept

Retention

Free
30 days
Pro
90 days
Scale
180 days, configurable

Rage clicks recorded as their own event: three clicks on one target inside a second

How it works

  1. 01

    Recording starts when the page is ready

    After startup health checks, eligible sessions begin with a snapshot and record DOM changes, pointer movement, scroll and masked input within fixed budgets.

  2. 02

    The report freezes the buffer

    Available replay is linked to the ticket alongside captured console and network activity. The player explains missing intervals.

  3. 03

    Your team scrubs the film

    The player runs the session beside the log, and clicking a line seeks to it.

Reproduce without asking

Beside the film runs the same session as a log: captured clicks, requests and console errors in order, coloured by level. Steps to reproduce stop depending on the reporter's memory.

Honest about what it could not capture

When the widget stands down under host load, or a page is too large to snapshot, the ticket says so: the interval it missed, why it missed it, and the recording that stopped at its own ceiling. Nothing is stitched over.

Exact behaviour

Capture
Full DOM snapshot, then mutations, pointers, scroll and masked input; flushed every 10 s
Retention
Replay follows the project window, capped at Free 30 days, Pro 90 days, Scale 180 days, configurable; captured logs 30 days; idle sessions 90 days
Privacy
Input masking always on; secrets scrubbed from logs; mask and block rules per selector
Browsers
Chromium, WebKit, Firefox; desktop and mobile
Plan
Every plan; the plan caps how long a replay is kept: Free 30 days, Pro 90 days, Scale 180 days, configurable
MCP tool
get_ticket · list_sessions · get_session · get_masking_rules

Works with

Evidence capture Console and network in the same ticket. Screen recording When the reporter wants to show it live. Board & pipeline Where the replay gets watched.

Questions teams ask before installing

Does replay record what users type?

No. Input masking is always on and is not a setting, so a replay carries the shape of a form and never the characters typed into it.

How much CPU does it use on the host page?

Recording uses bounded cooperative work and pauses when the host page is under pressure. The Host Isolation Contract defines measurable limits and fallbacks; it does not promise unchanged performance metrics on every page.

Can I turn replay off, or keep part of a page out of it?

Replay belongs to a project's capture settings, so it is switched on or off per project, either in the panel or with the update_project_settings MCP tool. Inside a page the unit is the selector, not the URL: mask selectors, block selectors, scrub keywords and a mask-everything switch, read with get_masking_rules and changed with set_masking_rules. Those rules can only ever reduce what is captured.

The thinking behind it

The hard part of session replay Recording a page is the easy half. The constraints a recorder inside somebody else's page must satisfy, the two ceilings behind them, and what a replay gives.A plan limit has three surfaces Gating a paid tier is three decisions: what gets served, what gets accepted, and what gets reported. The costly failure is those three drifting apart.The gap in a ticket's evidence has an owner Writing back to the reporter is the reflex when a ticket's evidence has a gap. It is the right move only when the gap belongs to that reporter's visit.

See the replay on your own site today.

Free plan includes session replay.

Start free See pricing
<script src="…/widget.js" data-key="pb_pub_…">