Configuration

Desktop vs Tab Recording

Crosscheck offers two recording modes: tab recording and desktop recording. Each mode uses a different browser API and captures content differently. Understanding the differences helps you choose the right mode for your situation.

Feature Comparison

FeatureTab RecordingDesktop Recording
Capture scopeSingle browser tabEntire screen or application window
Capture methodBrowser tab captureSystem screen capture
AudioTab audio included automaticallySystem audio (requires user permission)
Multiple tabsNo, single tab onlyYes, if sharing the full screen
Non-browser contentNoYes, can capture any application
Resource usageLower CPU and memoryHigher CPU and memory
Permission promptNone (extension permission)Chrome sharing dialog each time
ResolutionMatches tab viewportMatches screen or window resolution
DevTools contextCaptured for the recorded tabCaptured for the active tab only

Tab Recording

Tab recording captures the contents of a single browser tab. It uses the browser's built-in tab capture capability, which is available exclusively to Chrome extensions. This mode is lightweight, does not require a permission prompt each time, and automatically includes audio playing within the tab.

When to Use Tab Recording

  • You are testing a web application and only need to capture that one tab.
  • You want minimal resource usage during recording.
  • You want tab audio captured automatically without extra permissions.
  • You need devtools context (console logs, network requests) aligned with the recording.

Desktop Recording

Desktop recording uses the browser's built-in screen sharing capability to capture your entire screen or a specific application window. Chrome will prompt you to choose what to share each time you start a desktop recording. This mode captures everything visible in the selected area, including non-browser applications and multiple browser tabs.

When to Use Desktop Recording

  • You need to show interactions across multiple browser tabs.
  • You want to capture non-browser applications alongside the web app.
  • You need to demonstrate a workflow that spans multiple windows.
  • You want to include system audio in the recording.
Recommendation
Use tab recording for most bug captures. It produces smaller files, uses fewer system resources, and keeps devtools context tightly synced with the recording. Switch to desktop recording only when you need to capture content outside a single tab.

Switching Between Modes

You can switch between tab and desktop recording from the extension popup before starting a recording. Open the Crosscheck popup, look for the recording mode toggle, and select your preferred mode.

Desktop recording and devtools context
When using desktop recording, devtools data (console logs, network requests, user actions) is still captured, but only for the tab that was active when the recording started. If you switch between tabs during a desktop recording, devtools data from other tabs will not be included.
Last updated: March 2026