Hey Product Hunt 👋 Bugmark came out of a loop I got tired of. Someone reports a bug. I get a screenshot. Then I ask what the console said. Then I ask what the API returned. Then I ask what they clicked before it broke. Three round-trips later I finally have enough to reproduce it — and by then they've moved on to something else. The information I needed was sitting right there in their browser the whole time. It just wasn't in the report. So Bugmark captures all of it in one shot. You annotate the screenshot (or record your screen with voice), and the report automatically carries: • Console logs and JavaScript errors • Every network request — with payloads and responses, copyable as cURL or exportable as HAR. • The steps that led to the bug, recorded for you • The element's CSS selector and computed styles Then you file it straight to a GitHub issue, or export it as HTML, PDF, CSV or Markdown for someone who doesn't live in your issue tracker. Two things I'd point out, because they're deliberate: **It's local-first.** Screenshots, recordings and network logs live in your browser's storage. I don't run a server that receives them — which means it works on localhost, staging and internal apps behind a login, and nothing needs approval from your security team. Passwords, tokens, API keys and card numbers are masked to [redacted] before a request is ever saved, and you can pixelate anything else on the screenshot. **It's a one-time $15, not a subscription.** Free gets you every feature on up to 2 saved a time — not a crippled trial, the whole product. $15 removes the limit forever. I didn't want to bill people monthly for a thing that runs entirely on their own machine. Works in Chrome, Edge, Brave and Arc. No account needed to start. I built this alone and I'd genuinely like to know where it falls short — especially if you client work, where I suspect the white-label reports matter more than I've assumed. I'm here all day. Why it's built this way: - Opens with a specific frustration, not a feature list. Everyone reading has lived that three-round-trip loop. Recognition earns you the next paragraph. - The differentiators come before the features run out of welcome. Local-first and one-time pricing are your only two real moats against Jam — burying them below a feature dump wastes them. - It ends with a question, not a sign-off. Comments weigh heavily in PH ranking, and an easy-to-answer question aimed at a specific group (QA and agency folks) generates threads. A "thanks for reading!" generates nothing.

Bugmark

Stop asking "what does the console say?"

Stop asking "what does the console say?"