Bug Report

by Frankard Marc · Developer Tools

Manifest V3 Free

View in Chrome Web Store Data as of 16 Oct 2026

Captures JavaScript and network errors to quickly generate a bug report.

Users

+1 in 30 days

Rating

0.0 / 5

unchanged in 30 days

Ratings

0 in 30 days

Store rank

#253K

#212K among extensions

Version

1.0.0

updated 19 Aug 2026

Users

monthly, 2 months

Latest, 16 Oct 2026: 5 usersMove the mouse over the chart for any month

Ratings count

monthly, 2 months

Latest, 16 Oct 2026: 0 ratingsMove the mouse over the chart for any month

The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.

About Bug Report

Bug Report turns any page into a ready-to-share bug report — in one click. Stop copy-pasting console errors by hand or trying to describe a network failure from memory. Bug Report captures everything a developer needs to reproduce an issue, right when it happens: • JavaScript errors, uncaught exceptions, and unhandled promise rejections, with file, line, and column when available • Failed network requests (404s, 500s, timeouts, DNS failures) with method, URL, and status code • A screenshot of the page exactly as the user saw it • Page URL, title, viewport size, and browser environment Everything is assembled into a clean report — viewable on its own page, and exportable as Markdown with one click, ready to paste into GitHub, Jira, Linear, Slack, or an email. WHO IT'S FOR Developers, QA testers, and support teams who need to turn "it's broken" into an actionable bug report without switching tools. PRIVACY BY DESIGN Bug Report runs entirely on your device. Nothing is uploaded to any server — the report stays in your browser's local storage until you choose to copy and share it yourself. No accounts, no tracking, no analytics. See the full privacy policy for details. HOW IT WORKS 1. Run into a bug on any page 2. Click the Bug Report icon, then "Create report" 3. Review the captured errors, network failures, and screenshot 4. Copy the generated Markdown and paste it wherever you track bugs