BugMojoBugMojo
Get started
How-to

Capture modes: screenshot, replay, and full capture

Learn what each BugMojo capture mode records and pick the right one for the bug you are reporting.

Applies toPlans:FreeProBusinessEnterpriseWhere:ExtensionWeb app

Not every bug needs the same evidence. A layout glitch might only need a screenshot, while an intermittent error needs the full picture. BugMojo lets you choose how much to capture when you file a report, so you can move fast on simple bugs and stay thorough on hard ones.

Choose the right mode

Pick a mode based on how much context the fixer will need:

  • Screenshot: a single image you can annotate with arrows and notes. Best for visual and layout bugs where a picture says everything, like a broken style or misaligned button.
  • Session replay: an rrweb DOM replay of your recent activity, so a teammate can watch the exact steps that led to the bug. Best for interaction and flow problems that are easy to reproduce visually.
  • Full capture: the replay plus console logs, network requests (method, URL, status, timing, and masked headers), a screenshot, and your device, OS, browser, and viewport details. Best for hard-to-reproduce, timing, or backend-related bugs, and the mode AI agents get the most from.

Start a capture

Capture a bug in your chosen mode

  1. Reproduce the bug. Open the page where the problem happens and make it happen again. BugMojo keeps a rolling recording of your recent activity, so you do not need to press record first.

  2. Open the extension. Click the BugMojo icon in your browser toolbar, then choose Capture.

  3. Pick a mode. Select Screenshot, Session replay, or Full capture for the report you are about to file.

  4. Annotate if needed. On a screenshot, add arrows, boxes, or notes to point out exactly what is wrong before you continue.

  5. Describe the bug. Add a short title and what you expected to happen, then pick a project or select Quick Capture to skip setup entirely.

  6. Submit. Click Submit. BugMojo masks sensitive text and inputs in your browser first, then uploads the report and opens it in the dashboard.

Common questions

Which capture mode should I use by default?

Use full capture. It attaches the replay, console logs, network requests, a screenshot, and environment details, which is what a teammate or an AI agent needs to reproduce and fix the bug.

Does full capture record a video of my screen?

Not by default. Full capture records an rrweb DOM session replay, a reconstructed recording of the page, not a screen video. The Chrome extension can additionally record an opt-in, real-pixel video of the current tab when you turn it on for a capture; the widget and SDKs stay DOM-only.

Is my sensitive data safe in every mode?

Yes. Text and input values are masked in the browser before anything is sent. Client-side PII redaction runs in every capture mode, so private data never leaves your machine unredacted.

Was this helpful?
Updated Jul 10, 2026 · Still stuck? Contact support

Related articles