“Fixed” is not the same as verified.
One click captures the screenshot — or the whole recording — with the console, the network and the exact environment. Then BugCapture carries the bug the rest of the way: triage, assignment, and a Verified state that records who checked the fix.
Free forever · 25 reports a month · No card · Works on any web page you can open
Bug reports are broken.
Most tickets are missing the exact information needed to fix them — so they bounce between QA and engineering for days.
“Works on my machine.”
No console. No network log. No environment. The one report that could be fixed in minutes gets bounced back for more info.
Repro steps, written by hand.
QA retypes the same click path on every ticket — and still gets asked which build, which browser, which env.
Context that never arrives.
The details that would explain the bug live in the tab that's already closed. So the ticket ships half-empty.
From one click to a verified fix.
Capture
One click grabs the screenshot and the console, network, DOM and device context — automatically.
Enrich
Add severity, environment and numbered steps. Blur anything sensitive right on the image.
Share
Send a link, copy as markdown, or push straight to Jira, Linear or GitHub.
Verify
When the fix lands, the bug moves to Ready for QA — and Verified records who checked it. Closing is a decision someone signed.
Most trackers treat “Fixed” as the end of the line.
It isn’t. Someone still has to check. BugCapture makes that step part of the bug’s life instead of a message in a thread — and puts the checker’s name on the report.
- New
- Triaged
- In progress
- Ready for QA
- Verified
- Closed
Ready for QA → Verified · by Priya N. · 14 Aug, 16:12
Ready for QA is a state, not a label
The two steps between a fix landing and a bug closing get their own place in the flow — not a custom status somebody has to build, and not a tag someone has to remember to set.
The verifier is on the record
Moving a bug to Verified stamps who did it, and when, onto the report. Reopen it and the stamp clears — so a name never outlives the state it belongs to.
The trail can’t be quietly rewritten
Every transition appends to an activity log no client can write to — not the reporter, not an admin, not the person who moved it. A status cannot change without a line saying who changed it.
Record the whole reproduction. Land on the error.
Recordings carry the same console and network trace as a screenshot — and the timeline is marked where the errors happened, so nobody watches three minutes to find the second that matters.
- Tab or region — never your whole screenRecord one tab, or drag a region of it. Desktop capture was removed deliberately, so nothing else you have open can end up in a bug report.
- Repro steps, written from the recordingThe clicks and the page changes become numbered steps automatically, so the ticket reads like a reproduction instead of a video link.
- Trim and pause before you sendCut the dead air at either end, or pause mid-take while you set something up. What arrives is the reproduction, not the rehearsal.
Everything your engineers need to debug — attached.
No more asking what the user was doing. BugCapture records the technical context of the tab the moment the bug happens.
✕ TypeError: cart.total is undefined
⚠ Deprecated API: computeTax() → useTax()
› render Checkout (app.bundle.js:1180)
› fetch /api/cart — masked auth header [REDACTED]
Everything a report needs to be actioned on arrival.
Structure, evidence, privacy — and the triage workflow around them, so a report doesn't stop being useful the moment it lands.
QA metadata that ships with the bug
Environment (Dev / UAT / Prod), severity from Blocker to Trivial, and priority P1–P4 — fields your tracker can filter on, not prose someone has to read. Change one after filing and the activity trail records who did.
The same bug, filed twice, marked once
Reports matching one already filed arrive tagged “Seen 4×”, so it gets triaged once instead of four times.
Annotate and redact
Pen, shapes, text and a real canvas blur — plus click-to-mask elements on the live page, before the screenshot is even taken.
Numbered step pins
Mark the exact click path, right on the screenshot. The reproduction travels with the evidence.
Assign it, discuss it — then verify it
Status, assignee, comments and @mentions, on an activity trail that can’t be edited from the app. And a Verified state that records who checked the fix, so “closed” means somebody actually looked.
Copy as markdown
Paste a complete report into a pull request, a Slack thread, or a tracker we don’t integrate with.
Share in one click
A link anyone on the team can open — no account, no install. Set an expiry, and revoke every link at once when the engagement ends.
Private by construction, not by policy.
BugCapture is built so sensitive data can’t make it into a report in the first place. It’s enforced in code — not a checkbox someone has to remember to tick.
Automatic redaction is pattern-based, so we don’t ask you to treat it as a compliance control — which is exactly why the manual tools and the off-by-default settings above exist.
Bodies & headers, never read
The capture layer records method, URL, status and timing — never response bodies or request headers, so tokens can't leak into a report.
PII masked before upload
Emails, JWTs, Bearer tokens, long hex and card-like numbers are redacted in the page, before anything is buffered or sent.
Off by default
Request bodies, local storage and cookies are not captured at all unless your workspace turns them on. The safe setting is the one you start with.
Blocked sites
Name the domains BugCapture must never capture. It won't — for anyone in the workspace, not just the person who set it.
Blur anything else
A real canvas blur on the screenshot, and click-to-mask on the live page before capture, for anything the automatic scrubber can't reach.
Where it lives
Reports and screenshots in Google Cloud, in India. Screen recordings on Cloudflare R2. Kept 30 days on Free; for as long as you subscribe on Team.
Bug context your AI can actually read.
The BugCapture MCP server pipes structured bug context straight into your AI agent or IDE — the console trace, the failed request, the environment — with no copy-paste. Let the agent read the report and propose the fix.
- Works with any MCP-compatible client
- Structured, redacted context — not raw dumps
- Included on the Team plan
$ npx bugcapture-mcp
✓ connected · workspace acme
agent › read bug bug_9f2a
severity critical
error cart.total is undefined
request POST /api/tax → 500
env Chrome 141 · UATFits the stack you already use.
Send a bug straight into your tracker — no re-typing, no context lost in the handoff. Every integration is on the free plan; no tier gates the thing the product exists to do.
Jira
Create an issue
GitHub
Open an issue
Linear
File an issue
ClickUp
Create a task
Notion
Add a page
Slack
Post to a channel
Need a tracker or internal tool we don’t support yet? Book a demo and we’ll scope a custom integration with you.
Start free. Upgrade when your team does.
Every integration is free. Team adds AI agent access, no reporter limit, and reports that don't expire.
Free
Viewers always freeCapture, triage and verify — the whole bug, start to finish. Free forever.
No card required
Add to Chrome- 25 reports a month, per account
- 5 reporters · unlimited free viewers, who read and comment
- One-click capture: screenshot + console + network
- QA metadata — environment, severity, priority
- Ready for QA → Verified, with the verifier named on the report
- Annotate, blur/redact and numbered step pins
- Copy as markdown
- Shareable public report links
- Google and Microsoft sign-in
- File to Jira, GitHub, Linear, ClickUp, Notion, Slack and more
- 5 screen recordings a month, up to 60 seconds each
- Screenshots & recordings kept 30 days
At the limit, new captures pause until the 1st. Nothing is deleted and every report stays readable.
Team
Launch offerMCP server, no reporter limit and screenshots that never expire while you subscribe.
Two months free · regular ₹7,990 once launch ends
Start free, upgrade anytime- Everything in Free
- Screenshots & recordings kept while subscribed — 1 year after you cancel
- No reporter limit, priced per reporter · 500 reports per workspace each month
- 100 minutes of screen recording a month · up to 3 min
- MCP server for AI agents & IDEs
- Team members & shared workspace
- Email support
At the limit, new captures pause until the 1st. Nothing is deleted — and if you need more, email us and we'll raise it.
Enterprise
For organisations that need SSO, audit trails and custom retention.
Not available to buy yet — talk to us
Book a demoPLANNED:
- SAML SSO & SCIM provisioning
- Audit log export
- Custom retention
- Webhooks and API
- Priority support
Prices shown in INR, per reporter — viewers are always free, and they can read and comment. Yearly is billed once and works out at two months free. Launch pricing applies now; the regular price applies later. No one is ever charged a struck-through price.
Questions, answered.
Chrome, Edge, Brave and other Chromium browsers, and Firefox. It captures any web page you can open, including staging and localhost. It can't capture browser-internal pages like chrome:// or the extension stores, and a page with a very strict content security policy may block part of the console capture.
Turn your next bug into a report in one click.
No SDK to install, no code to change. Free forever plan, no card — your engineers will wish every ticket looked like this.