Capturing Bugs

Instant Replay

Privacy first
Instant Replay records page activity locally in your browser. Nothing is sent to any server until you explicitly choose to save and share a replay. The recording buffer stays in your browser until you choose to save. Your browsing activity remains private at all times.

How It Works

Instant Replay uses lightweight session recording technology that runs inside the browser. Rather than capturing pixels as video, it records page changes, user interactions, and visual state. This produces lightweight session data that can be played back as a faithful reproduction of the original session.

1

Enable Instant Replay

Open the Crosscheck extension and make sure Instant Replay is enabled in your capture settings. You can enable Instant Replay on a per-site basis and configure the buffer duration to suit your workflow. Once enabled, the extension begins recording page activity in the background as you browse.
2

Browse and test normally

Go about your testing workflow as usual. The recording happens silently in the background with minimal performance impact. A rolling buffer keeps the most recent 1 to 5 minutes of activity, depending on your configured buffer duration.
3

Spot a bug and capture

When you encounter a bug or unexpected behavior, click the Instant Replay button in the extension popup or floating toolbar. The current buffer is frozen and packaged as a replay capture.
4

Review the replay

A preview of the captured replay opens so you can verify it shows the issue. The replay includes synchronized developer context: console logs, network requests, and the user action timeline from the same time window.
5

Save and share

Save the replay to your active project. A shareable link is generated automatically. Team members can play back the replay in the Crosscheck dashboard using the built-in session player.

Instant Replay capture in extension

Capturing an instant replay after spotting a bug

Why Session Data Instead of Video?

Traditional screen recordings capture raw pixel data, resulting in large video files. Instant Replay takes a fundamentally different approach by recording the structure of the page rather than its pixels.

AspectInstant Replay (Session Data)Screen Recording (Video)
File sizeTypically 50-200 KB for a 30-second sessionSeveral MB for the same duration
FormatLightweight session dataWebM video (pixel data)
PlaybackReconstructed in the browser using the session playerStandard video player
InteractivityCan inspect elements, copy text, resize during playbackFixed resolution, view-only
Capture triggerRetroactive: captures what already happenedProactive: must start recording before the bug occurs
Performance impactMinimal: lightweight event listenersHigher: video encoding in real time

Privacy and Data Handling

Instant Replay is designed with privacy as a core principle:

  • The recording buffer stays in your browser until you choose to save. No data leaves your machine until you explicitly save a replay.
  • Password fields are automatically masked in the recorded session data to prevent sensitive information from being captured.
  • You can disable Instant Replay at any time from the extension settings. When disabled, no background recording occurs.
Session player in the dashboard
Replays are played back in the Crosscheck dashboard using an interactive session player. The player supports play, pause, speed control, and scrubbing. Developer context events (console logs, network requests) appear alongside the replay timeline so you can see exactly what happened in the code at each moment.

When to Use Instant Replay

Instant Replay is best for intermittent or hard-to-reproduce bugs. Since it captures retroactively, you do not need to anticipate when a bug will happen. It is also useful during exploratory testing sessions where you want to stay focused on the application without managing recording controls. For longer, planned recording sessions, use Screen Recording instead.

Last updated: March 2026