Product overview
BugCapturer is a visual bug reporting tool: anyone on your team — or a visitor on your website — can capture what they see, annotate it clearly, and turn it into a structured report that lands straight in the tools your team already uses.
Two capture modes
Section titled “Two capture modes”BugCapturer offers two ways to capture, depending on what the problem looks like:
- Screenshot & annotation — for static problems that are obvious at a glance: select a region and mark it with rectangles, arrows, pen or text, reproducing exactly what you saw at pixel level
- Screen recording — for multi-step interactions that are hard to describe: record the current tab for up to 60 seconds, then trim the key part on the timeline
Either way you get the same structured report, with technical context (console errors, failed network requests) attached automatically.
Two ways to use it
Section titled “Two ways to use it”We provide two ways to use BugCapturer — the browser extension or the Web SDK. Pick by who is actually looking at the screen.
| Browser extension | Web SDK | |
|---|---|---|
| Who uses it | Testers, QA, colleagues, clients who can install it | Site visitors — no install, no account |
| Where it runs | Chrome / Edge extension | One <script> tag on your site |
| How it captures | Pixel-accurate screenshots, no permission prompt | Real pixels via the browser’s own screen-share confirmation (skipped when the visitor has the extension) |
| Best for | Internal acceptance testing on test / UAT environments | Feedback from real visitors on production or UAT pages |
Both paths produce the same kind of report and can target the same destinations — a tester’s screenshot and a visitor’s feedback can end up in the same table.
What a report contains
Section titled “What a report contains”- Screenshot — real pixels of the page, including the region you annotated (rectangle, arrow, pen, text)
- Recording — optional, up to 60 seconds, trimmable on the timeline
- Description — free text
- Reporter identity — contact details when submitting anonymously, or name / email / uid when known (see Reporter identity)
- Technical context — collected automatically: page URL and title (sensitive parameters masked), browser, operating system, screen size, plus console errors and failed network requests
How the data flows
Section titled “How the data flows”- Captured locally — screenshots, annotations and recordings are created in the browser; nothing leaves the device unless someone actively shares or submits
- Submitted or shared — either submitted to a destination, or published as a public share link
- Stored — submitted reports and share content are stored server-side; every item can be deleted from the console at any time
- Dispatched to integrations — reports bound to an integration are written into the target (Feishu Bitable or a generic webhook)
Opens the feedback widget — the page URL and title are attached automatically