Why BugCapturer
How painful traditional bug feedback is
You spot a problem on a website and want to report it. The traditional flow looks like this:How BugCapturer does it
Core features
Region screenshot
Click the extension icon, then drag anywhere on the page to select an area. No full-screen capture and no cropping afterwards — you pick exactly the region you want to report.- 8 resize handles for precise selection
- Everything outside the selection is dimmed automatically
- Right-click menu shortcut ("Screenshot feedback")
5 annotation tools
After capturing, the annotation editor gives you five tools:| Tool | Use | Example |
|---|---|---|
| Arrow | Point at the problematic element | A red arrow at overlapping buttons |
| Rectangle | Frame the problem area | A box around a broken layout block |
| Text | Add a written note | "Text is cut off here" |
| Brush | Draw freely | Circle, underline, tick |
| Mosaic | Blur sensitive information | Mask usernames, emails, API keys |
Automatic technical metadata
When a report is submitted, BugCapturer captures the following automatically — nothing to type:| Data | Why it matters |
|---|---|
| Page URL | Pinpoint the exact page |
| Browser name and version | Diagnose browser compatibility issues |
| Operating system | Diagnose OS-specific problems |
| Screen resolution | Diagnose layout issues at different resolutions |
| Viewport size | Judge responsive layout problems |
| Device pixel ratio (DPR) | Diagnose Retina/HiDPI rendering issues |
| Timestamp | Record when the problem happened |
Automatic console error capture
When a webpage breaks, the browser console almost always has something to say. But most people don't know how to open it, let alone copy the error. BugCapturer captures console errors for you:- Only
errorlevel (info/warn noise is filtered out)
- Includes the error message plus source location (file:line:column)
- Up to the last 10 entries
- Captured when the report is submitted, with no background listening
- You can uncheck it — full control stays with you
Automatic failed-request capture
Many webpage problems aren't rendering bugs at all — an API call failed and the data never arrived. BugCapturer captures failed network requests:- Only requests with status ≥ 400 (real failures)
- Includes URL, HTTP method, status code and status text
- Up to the last 5 entries
- Sensitive URL parameters are redacted automatically (
token,key,secret,passwordand similar become*)
- Captured when the report is submitted, with no background listening
One-click share, or straight into your team's workflow
Once the description is in, a report can go one of two ways — your choice:- Generate a share link: one click gives you a public link. The recipient doesn't install anything and doesn't need an account — they open it in a browser and see the annotated screenshot, page URL and full diagnostics. Drop it in a chat, an email or a ticket.
- Route it to a destination: with the destination dropdown, send the report straight into Lark Bitable or your own webhook. Screenshots, console errors and failed requests arrive with it, so it becomes a row in your team's table — or it kicks off any flow in your own systems.
Team collaboration: configure once, everyone shares it
- Teams and members: the owner configures an integration once and the whole team can use it. Invites require an explicit accept step.
- Credentials stay private: team members can submit through a shared integration but never see the credentials themselves.
- Projects and domains: one project per site, with a whitelist of domains allowed to submit — which keeps your SDK keys from being abused.
- Share links stay manageable: signed-in users can manage or delete any report link they've shared from the "My shares" page.
Integrations: reports flow into the tools you already use
| Integration | Best for | Notes |
|---|---|---|
| Lark Bitable | Teams in China | No Lark app needed — write into your table through an automation webhook and use Lark's native automations for group notifications |
| Generic webhook | Teams with their own systems | Signed, versioned JSON payloads that plug into n8n / Zapier / Make / your own services, with automatic retries, a delivery log and manual replay |
7 languages
BugCapturer supports 7 interface languages:- 中文（简体）
- English
- Deutsch
- Français
- Español
- Português (Brasil)
- 日本語
Data security and privacy
BugCapturer is a cloud collaboration platform, and it turns "what gets processed, how long it's kept and who can see it" into explicit rules:| Practice | How it works |
|---|---|
| Encrypted in transit and at rest | Reports travel over HTTPS and are stored encrypted on the server |
| Automatic URL redaction | token, key, secret, password and similar parameters in request URLs become * |
| Link retention | Anonymous share links last 30 days, signed-in links 90 days, then they're cleaned up automatically — and you can delete them by hand any time |
| Unguessable links | Share links use random IDs, so nobody can enumerate other people's reports |
| Permission isolation | Team integrations are configured by the owner; members use them without ever seeing the credentials, and projects are visible only inside the team |
| Captured on submit | Console errors and network requests are captured when a report is submitted, not continuously in the background |
| User control | Technical diagnostics are on by default but can be unchecked in one step |
Who BugCapturer is for
QA / test engineers
The core audience. Reporting a lot of bugs every day, BugCapturer cuts each report from 5-15 minutes to 30-60 seconds while attaching the technical diagnostics that prevent "can't reproduce" back-and-forth.Front-end developers
When debugging cross-browser issues you need to record how a page behaves in each browser. BugCapturer captures browser version, resolution and viewport automatically, so there's nothing to write down.Product managers
When feedback is vague, you need to see it. Embed the Web SDK on your site and visitors can point at the problem directly, with the technical context attached so there's nothing to chase.UI/UX designers
For visual review you need to mark the difference between the design and the live page. BugCapturer's five annotation tools are precise enough for visual issues, and the share link can go straight to a client for sign-off.Team leads / project managers
The UAT and acceptance stage suffers most when feedback is scattered across everyone's own devices. BugCapturer routes it into one place — your Lark table or your existing system — so progress, owners and status are all visible in one spot. This is exactly where organisational efficiency tends to stall.Everyday web users
Anyone who spots a website problem and wants to report it. No technical background, no DevTools, and 30 seconds to submit a professional report.BugCapturer vs other approaches
| Dimension | Manual screenshot + email | Phone photo in a chat | Dedicated feedback platform | BugCapturer |
|---|---|---|---|---|
| Time | 5-15 minutes | 2 minutes | 3-5 minutes | 30 seconds |
| Annotation | None / weak | None | Strong | 5 tools |
| Technical info | Typed by hand | None | Captured automatically | Captured automatically |
| Console errors | Requires DevTools | None | Partial | Captured automatically |
| Network errors | Requires DevTools | None | Partial | Captured automatically |
| Where reports land | Personal inbox | Group chat | Inside the platform | Lark table / webhook / share link |
| Team collaboration | Weak | Weak | Strong | Shared integrations + public links |
| Price | Free | Free | Paid | Free to start |
Install and use
Install
Use
FAQ
Is BugCapturer free?
It's free to start. The free plan includes 1 seat, 3 projects and 1 integration, and covers the core features: screenshot annotation, recording, automatic diagnostics and share links. Upgrade only as your team grows. No trial countdown.Is my data safe?
Reports travel over HTTPS and are stored encrypted; sensitive URL parameters are redacted to*; share links have a retention period (30 days anonymous, 90 days signed-in) and can be deleted any time; team integration credentials are visible only to the owner. See the privacy policy for the full picture.