Give every frontend error a replay button
rrweb records what happened in the browser around an error. Link the recording to your alert and open it inside your product at the exact moment the failure occurred.
Session replay built on rrweb.
See the path to the error
A stack trace identifies the function that failed. The replay shows the clicks and interface states that led to it.
- Align console output and network activity with the recording timeline.
- Open the recording at the exception timestamp from an alert, issue, or trace.
- Review the interface states and user actions before the failure.
session #8241 · event stream
console.error · 14:32:07
jump to error →
Connect your telemetry to the replay
Attach a session ID and timestamp to the error your SDK already captures. rrweb events travel through your backend or rrweb Cloud, then the replay opens inside your existing issue view.
rrweb recorder
DOM state, mutations, and user interactions become an open event stream.
Infrastructure
Transport, storage, indexing, queries, and access control.
rrweb Platform provides the containerized backend for deployment in your own cloud.
Your product
Replay embedded in your error, support, or customer-facing workflow.
Give customers a reason to upgrade
Session replay turns clicks, interface changes, and telemetry into a clear account of what the customer experienced. That story helps teams explain a failure faster and gives you a valuable feature to sell as an extension or include in a higher plan.
- Show the journey into an error with the browser context and telemetry aligned on one timeline.
- Give teams one coherent investigation view for user behavior, errors, and releases.
- Package that workflow as a paid extension or a reason to move to a higher plan.
Product catalogue
Session replay
Error replay
Included in your product
Choose the backend that fits your product
Use managed infrastructure or operate the replay pipeline yourself.
Start with rrweb Cloud
Managed ingestion, storage, and replay delivery. Add the recorder, connect your metadata, and keep the investigation experience inside your product.
rrweb Cloud uses 80% less bandwidth and storage.
Build on open source
Use the MIT-licensed recorder and replayer with a backend you operate. Keep the open event format inside your own infrastructure.
Frequently asked questions
Does rrweb replace our observability product?
rrweb supplies the browser recorder, open event format, and replayer. Your product continues to own error tracking, traces, alerts, investigation workflows, authorization, and the customer relationship.
How does an error connect to the right recording?
Give the error and recording a shared session identifier and retain the relevant timestamps. Your application can then open the matching replay at the moment the error occurred.
What can session replay not capture?
Closed shadow roots and third-party cross-origin iframes, payment forms above all, render as blanks by browser design. Backend state stays in your logs and traces and joins the session on id and time. Masked fields are captured as placeholders; the real values never leave the browser.
Can we run the recording data on our own infrastructure?
Yes. The recorder, event format, and replayer are open source, so you can build and operate the backend yourself. rrweb Platform also packages the backend as containers for deployment in your own cloud under a commercial license.