On the item
The replay is
already on the error when you open it.
Session Replay shows you what happened before an error, so you are not guessing or reproducing. The user’s path and the root cause sit side by side on the item.
See exactly what the user saw
DOM snapshots capture the page at the moment of the error, so broken layouts show up right away.
Understand how the bug unfolded
The timeline shows clicks, inputs, navigation, and console messages in order.
Record the sessions that matter
Trigger replays on errors, routes, warning levels, or manual calls, with sampling that fits your budget.
Privacy, built in
Privacy classes mask or exclude inputs, forms, and page elements, so you control what gets captured.
Root cause and fix
The user clicked Clear, then Apply. That is your bug.
The replay shows the path the user took to the failure. Here, two clicks left both date inputs empty before Apply ran the chart update. Your coding agent can pull the same replay through our MCP server and write the fix in your editor. A confusing flow, a missing validation, or a race from rapid clicks goes from a mystery to a change you review.
Built for debugging
Replays sit where you
already debug, right next to the stack trace.
Start with what matters most
Session Replay is on by default for new errors. Add triggers when you need more coverage.
Stay in your debugging flow
Replays are built into the item page, so you never switch tabs or open another tool.
Install with one line
It uses your existing Rollbar setup and links itself to new occurrences.
Get started