How to use a screen capture Chrome extension that keeps everything local

Most screen capture Chrome extensions are cloud products in disguise: you capture, the file uploads, and you get back a link. Convenient — but it means whatever was on your screen now sits on someone else’s server. For a developer that’s often DevTools with auth tokens visible, staging URLs, or a customer’s account open in the tab. Before installing a capture tool, it’s worth asking one question: where does the capture go?

Capture without an upload

ReproKit answers it simply: nowhere, unless you send it. Open the popup and capture — a screenshot of the visible tab or a screen recording of the bug happening. The capture is assembled entirely in your browser. There’s no account to create first, and no background sync shipping your screen to a dashboard you’ll never audit.

What “local-first” actually means here

Three concrete things. The bundle — screen capture, console output, network HAR, environment, steps — is built on your machine. Redaction of tokens, cookies and PII runs locally, before any sharing, with your review of what’s masked. And the extension runs with minimal permissions: no all-sites access sitting in the background reading every page you visit.

Review before anything leaves

When you stop a capture, you see what was recorded and what was redacted. That human check is deliberate — auto-redaction catches known patterns like auth headers and tokens, but you’re the one who knows that the spreadsheet in the corner of the frame is payroll. Confirm the capture, then decide where it goes.

Share on your terms

Export the bundle as a file and attach it to a ticket, hand it over in chat, or — on the paid tier — file it directly into Linear or GitHub Issues or share it via a secure link. Every one of those is an explicit action you take. The default state of a capture is: on your machine, and nowhere else.

Why this matters for bug reports specifically

Bug captures are the worst kind of screen content to spray into a cloud: they’re taken precisely when something is broken, often on internal tools, with real data on screen. A local-first capture flow means you can record freely during an incident and sanitize before the capture travels — instead of hoping the upload didn’t include anything it shouldn’t have.