Bugpacker: QA bug reports with screenshot, console, network & repro steps
bugpacker.com · Developer Tools
Media
6 items
Description
Record a bug while you reproduce it. Screenshot, console, network and repro steps in one ZIP, on your machine. Nothing is uploaded. Bugpacker turns "it's broken" into a bug report a developer can act on. Press record, reproduce the problem, mark it when it appears, and Bugpacker hands you a single ZIP to attach to Jira, GitHub, Linear or an email. WHAT IT CAPTURES • Screenshots of the page, with the area you marked highlighted • Console output, uncaught errors and Content Security Policy violations • Failed network requests, with the server's own request id when it sends one • The steps you took — drafted for you, ready to edit • The state of every form field and why the browser or the site rejected it • Browser, OS, GPU, viewport, zoom, colour scheme and framework versions REPRO STEPS, WRITTEN FOR YOU Writing steps is the friction that produces one-line bug reports. Bugpacker drafts them from what you actually did: 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 Correct the draft instead of facing an empty box. NOTHING LEAVES YOUR MACHINE No account. No upload. No telemetry. The package is built in your browser and saved to your Downloads folder. Every other tool in this category uploads your bug data to its own cloud first; Bugpacker never does. PRIVACY SCRUBBING IS ALWAYS ON Email addresses, phone numbers, card numbers, tokens and authorisation headers are replaced before you ever see the package — and there is no setting that turns it off. Placeholders keep the shape and drop the content, so a rejected phone number reads [PHONE_1: (NNN) NNN-NNNN]: enough to fix a validator, not enough to identify anyone. Screenshot scrubbing masks password and payment fields automatically. That part is best effort, so you review everything before it is saved. ANNOTATE BEFORE YOU SEND Boxes, arrows, numbered pins, text labels, and a mask brush for anything the automatic pass missed. Bugpacker turns "it's broken" into a bug report a developer can act on. Press record, reproduce the problem, mark it when it appears, and Bugpacker hands you a single ZIP to attach to Jira, GitHub, Linear or an email. WHAT IT CAPTURES • Screenshots of the page, with the area you marked highlighted • Console output, uncaught errors and Content Security Policy violations • Failed network requests, with the server's own request id when it sends one • The steps you took, drafted for you and ready to edit • The state of every form field and why the browser or the site rejected it • Browser, OS, GPU, viewport, zoom, colour scheme and framework versions REPRO STEPS, WRITTEN FOR YOU Writing steps is the friction that produces one-line bug reports. Bugpacker drafts them from what you actually did: 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 Correct the draft instead of facing an empty box. NOTHING LEAVES YOUR MACHINE No account. No upload. No telemetry. The package is built in your browser and saved to your Downloads folder. Every other tool in this category uploads your bug data to its own cloud first; Bugpacker never does. PRIVACY SCRUBBING IS ALWAYS ON Email addresses, phone numbers, card numbers, tokens and authorisation headers are replaced before you ever see the package, and there is no setting that turns it off. Placeholders keep the shape and drop the content, so a rejected phone number reads [PHONE_1: (NNN) NNN-NNNN]: enough to fix a validator, not enough to identify anyone. Screenshot scrubbing masks password and payment fields automatically. That part is best effort, so you review everything before it is saved. ANNOTATE BEFORE YOU SEND Boxes, arrows, numbered pins, text labels, and a mask brush for anything the automatic pass missed. TRY IT IN THE FIRST MINUTE Installing a bug reporter when nothing is broken is an awkward moment, so there is a bug waiting for you. demo.bugpacker.com is a checkout that rejects a valid promo code (SAVE20), because the same element id is used twice and the page reads the copy the customer never typed into. Record it, and see what the package says about why. PRICING Fourteen days of everything, free. After that, capture, review and scrubbing stay free forever and a licence unlocks the export: $79 a year or $9 a month.