Bugpacker records a bug while you reproduce it, then hands you one file to attach: screenshots, console output, failed requests, the state of every form field, and the steps you took — written for you.
A Chrome extension. No account, no upload, no telemetry. The package is built in your browser and saved to your downloads folder.
Writing steps is the friction that produces one-line bug reports. Bugpacker drafts them from what actually happened, and you correct the draft instead of facing an empty box.
1. Clicked "Add to cart" (#add-to-cart) 2. Typed into "Promo code" (#promo) 3. Clicked "Apply" ([data-testid="apply-promo"]) 4. Console error: TypeError: Cannot read properties of undefined (reading 'total') 5. Request failed: POST /v2/discount → 500 6. Navigated to /checkout
The value typed is never recorded — only that a field was typed into.
One ZIP, about a megabyte, attachable anywhere.
BUG-REPRO-STEPS.txt Steps, expected, actual, environmentBUG-REPORT.md The same, for pasting into a trackerreport.json Structured, versioned, with a fingerprint for de-duplicatingscreenshot-*.png The page at the start, the area you marked, and the endconsole.log Logs, uncaught errors, rejections, CSP violationsnetwork-errors.log Real failures, kept apart from ad-blocked noisenetwork.har Opens in DevTools and any HAR viewerform-state.json What each field held and why it was rejectedpage-snapshot.html The DOM, made inert so opening it runs nothingenvironment.json Browser, OS, GPU, viewport, preferences, frameworksYou rarely know where a bug will surface. Record first, then mark the problem area the moment it shows up — even a screen later.
“Rejected an unknown string” is not actionable. Bugpacker reports the length, the shape, the validation flags and the site’s own error text.
Trace headers are lifted to the top of the report, so a backend engineer can jump straight to the matching server log.
Requests an ad blocker killed are counted separately from real failures, so forty blocked pixels never look like a fire.
Every other tool in this category uploads your bug data to its own cloud and asks you to make an account first. Bugpacker builds the package in your browser and saves it to your downloads folder. There is no server of ours in the loop.
Emails, phone numbers, card numbers, tokens and authorisation headers are replaced before you see the package. There is no setting that disables it.
A rejected number reads [PHONE_1: (NNN) NNN-NNNN] — enough to fix
a validator, not enough to identify anyone.
Typed text, passwords, cookie values and storage values are not captured at all. Only that a field was used, and what its name was.
Licence checks with our payment provider. Nothing else — and nothing at all if you have no licence.
Redaction is best effort. Read the privacy policy for exactly what is captured and what is not.
Seven days of everything, free. After that, capturing, reviewing and redacting stay free forever — a licence unlocks the download.