How-to · Developer
How to use a screenshot Chrome extension that captures more than pixels
The short answer
Take the screenshot from the extension popup, and capture it as part of a repro bundle: the image plus console output, network requests and environment details. Sensitive values are redacted locally, and you review the capture before sharing it.
- 1
Install ReproKit in Chrome or Edge — no signup required.
- 2
Open the popup and capture the visible tab.
- 3
Let the capture include console, network HAR and environment details alongside the image.
- 4
Review the capture; sensitive values are auto-redacted locally and you confirm what’s masked.
- 5
Export one bundle and attach it to your ticket or share it with your team.
A screenshot Chrome extension solves the easy half of a bug report: here’s what the page looked like. The hard half is everything the picture can’t show — the console error behind the blank component, the request that came back empty, the browser it happened in. If you’ve ever sent a screenshot and been asked “can you check the console?” or “which browser is this?”, you’ve hit that wall. The fix isn’t a better screenshot — it’s a capture that carries the evidence alongside the image, taken in the same click.
Take the screenshot
Open ReproKit and capture the visible tab. That’s the honest scope: it screenshots what’s on screen. If you need a stitched, scrolling capture of an entire long page, use a dedicated full-page tool — ReproKit’s screenshot exists to document a bug, not to archive a page.
Attach the context a picture can’t show
The screenshot is one part of a repro bundle. Alongside it, the extension can capture the console output, the network requests and responses as a HAR, your environment (browser, OS, viewport) and the steps you took. A developer opening the bundle sees the visual state and the failing request that caused it — no second round trip to reproduce with DevTools open.
Redact locally before it leaves your machine
Screenshots leak. A capture of a dashboard can carry customer names, emails, tokens in a query string. ReproKit auto-redacts sensitive values on your machine and lets you review what’s masked before anything is shared. That review step is yours — the tool proposes, you confirm. Nothing uploads silently in the background.
Share it as one bundle
Export the capture as a single shareable bundle and attach it to your ticket. The reporter doesn’t need an account — which is the point when the person seeing the bug is a client or a tester. On the paid tier, the bundle can be filed straight into Linear or GitHub Issues so the screenshot lands where the work happens.
When a screenshot is enough — and when it isn’t
For copy tweaks and layout nits, a plain screenshot is fine. The moment behavior is involved — something didn’t load, didn’t save, didn’t respond — reach for the capture that includes the logs. It costs you the same one click and saves the “cannot reproduce” reply — and the day you lost waiting for it.