Collecting structured bug reports from an open source community is one of the most persistent challenges maintainers face. Users file vague issues with titles like "it's broken" or "doesn't work for me," forget to include system information, and rarely attach screenshots. Maintainers then spend more time triaging and requesting additional context than actually fixing bugs. For projects that depend on volunteer effort, this wasted time is especially costly.
Most open source projects rely on GitHub issue templates to guide reporters through providing useful information. In theory, templates prompt users to include their browser version, operating system, steps to reproduce, and expected versus actual behavior. In practice, many community users skip the template entirely, delete the placeholder text, or fill it in with one-liners that leave maintainers guessing.
Even well-intentioned reporters struggle. Describing a visual bug in words is inherently difficult. "The sidebar overlaps the main content on mobile" could mean a dozen different things depending on the viewport width, browser, and which sidebar element is involved. Without a screenshot, the maintainer has to reproduce the issue blind — often on a different operating system or browser than the reporter is using.
The result is a growing backlog of issues that are difficult to act on, frustrated maintainers who feel like they spend all their time asking clarifying questions, and frustrated users who feel like their reports disappear into a void.
BugDrop adds a lightweight feedback button directly to your project's demo site, documentation pages, or any web-based interface. When a community member encounters a bug, they click the button, type a short description, and a screenshot of the current page is automatically captured. The reporter can then annotate the screenshot — circling the broken element, drawing an arrow to the misaligned text, or highlighting the area that looks wrong. Once they submit, a well-formatted GitHub issue is created in your repository with the description, the annotated screenshot, and automatically captured system information.
There is no signup, no account creation, and no friction. The reporter never leaves your site.
Imagine a user browsing your project's documentation site. They notice that a CSS transition is broken on the code example tabs — clicking between tabs causes a flash of unstyled content. With BugDrop embedded on the docs site, the user clicks the feedback button in the corner, types "Tab switching flashes unstyled content," and the widget captures a screenshot of the exact state of the page. The user circles the tab area in the annotation tool and submits. Thirty seconds later, you have a GitHub issue with a clear description, a visual reference, and the user's browser and OS information — everything you need to investigate and fix the bug without a single follow-up question.
Adding BugDrop to your documentation or demo site takes a single script tag:
<script
defer
src="https://bugdrop.dev/widget.js"
data-repo="your-org/your-repo"
></script>
Replace your-org/your-repo with your GitHub repository. The widget appears as a small feedback button in the corner of the page.
BugDrop works with both public and private GitHub repositories. For public repos, issues are visible to the community. For private repos, issues are only visible to collaborators — useful for projects that want to collect feedback from a public demo site but keep their issue tracker private during early development.