How-to · Developer
How to use a screen recorder Chrome extension for bug reports
The short answer
Press record in the extension popup, reproduce the bug, then stop. Alongside the video, the extension captures the console output, the network requests as a HAR, your environment and your repro steps into one bundle — auto-redacted locally and reviewed by you before anything is shared.
- 1
Install ReproKit in Chrome or Edge — no account needed.
- 2
Open the popup and press record; the HUD confirms capture is running.
- 3
Reproduce the bug — screen, console, network and your steps are recorded together.
- 4
Stop and review the capture; tokens and PII are auto-redacted locally, and you confirm what’s masked.
- 5
Export the repro bundle and attach it to your ticket, or file it to Linear/GitHub on the paid tier.
A screen recorder Chrome extension is the fastest way to show a bug instead of describing it. But a plain video still leaves the follow-up questions open: what did the console say at that moment? Which request returned the 500? What browser and OS was this? If the recorder only captures pixels, someone still has to reproduce the bug a second time with DevTools open.
Start recording from the toolbar
Open ReproKit’s popup and press record. A small on-screen HUD confirms the capture is running. Now reproduce the problem the way you normally would — click through the flow, submit the form, trigger the error. You don’t need DevTools open; the capture happens alongside your normal browsing.
What gets captured with the video
While the screen records, the extension also logs the console output, the network requests and responses as a HAR file, your environment details (browser, OS, viewport) and the steps you took. That’s the difference between a screen recorder and a bug recorder: the video shows what happened, the logs show why. When the developer scrubs to the moment the page broke, the failing request and the console stack trace are right there in the same bundle — no “please reproduce it again with DevTools open”.
Review and redact before anything leaves
Stop the recording and review the capture. Sensitive values — auth tokens, headers, cookies, PII — are auto-redacted on your machine, and you get a chance to check what’s masked before the bundle goes anywhere. Redaction happens locally, not on a server, and nothing uploads without your explicit action.
Export one shareable bundle
The result is a single repro bundle: recording, console log, network HAR, environment and steps. Attach it to a ticket or hand it to a teammate — they get the full picture in one file instead of a video that raises more questions than it answers. On the paid tier you can also file the capture straight into Linear or GitHub Issues.
No signup, no all-sites access
ReproKit works without an account — for you and for anyone you ask to capture a bug, which matters when the reporter is a client or a tester who won’t sign up for a tool. It runs with minimal permissions and assembles everything in the browser, so the recording is yours until you decide to share it.