BugDrop is a screenshot feedback widget for teams that need users to show the problem, not just describe it. A report can include the current page screenshot, annotations, redacted regions, the page URL, and browser metadata.
Best for: visual QA, docs issues, responsive layout bugs, client review, preview deployments, and product screens where a screenshot is faster than a reproduction essay.
Try the screenshot widget or read the screenshot configuration docs.
Website bugs are often visual: clipped text, broken spacing, missing images, wrong colors, hidden buttons, mobile overflow, dark-mode issues, or browser-specific rendering problems. A written report like "the page looks broken" rarely gives developers enough context.
A screenshot turns the report into a concrete artifact. An annotation points to the exact area, and metadata explains the environment where it happened.
data-bugdrop-mask| Capability | BugDrop screenshot widget |
|---|---|
| Screenshot capture | Current page state with reporter context |
| Annotation | User can point to the broken area |
| Redaction | Reporter can hide sensitive regions before submit |
| Developer masking | data-bugdrop-mask covers marked private UI |
| Output | GitHub Issue with screenshot, URL, metadata, and labels |
Screenshots can expose private information. BugDrop supports user redaction and developer-defined masking for sensitive elements. Password and payment fields should be treated carefully, and teams should review screenshot masking before deploying the widget to authenticated product pages.
Instead of sending screenshots to a separate dashboard, BugDrop creates a GitHub Issue. That keeps visual bug reports close to the code, release process, assignees, labels, and comments developers already use.
Start with installation, then configure screenshot behavior in configuration. Use the demo to try the capture and submission flow first.