4 items
Capture screenshots, console/network logs, and environment info in one click — annotate, export, or submit a structured bug report. BugSnap Pro: Capture a screenshot, console errors, failed network requests, and full environment details from any webpage — annotate what matters, fill in a structured report form, and export or submit directly to your team's tracker. All without leaving your browser, and without an account. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 📷 CAPTURE EVERYTHING THAT MATTERS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • Full-page or selected-region screenshots — one click from the toolbar or right-click menu • Console errors, exceptions, and warnings captured automatically (including uncaught exceptions and unhandled promise rejections) • Failed and errored network requests (URL, method, status, timing) • Complete browser, OS, viewport, and screen specifications • Local storage, cookies, locale, timezone, and network status details • Custom build version and environment labels you define (e.g. "staging / production") ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ✏️ ANNOTATE LIKE A PRO ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Draw directly on the captured screenshot before exporting: • Arrows — point to exactly what broke • Rectangles — highlight regions of interest • Numbered steps — walk reviewers through the reproduction sequence visually • Text callouts — add inline notes • Redact sensitive details — one drag to pixelate customer data (passwords, PII, payment info); the blurred pixels are baked permanently into every export so the original is never exposed • Full undo history (up to 50 steps) • Select and remove individual annotations • Rename or delete screenshots from the filmstrip ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 📋 A COMPLETE STRUCTURED REPORT ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Every report organizes captured evidence into editable fields for everything a triage team needs: Title · Summary · Build version · Environment label · Preconditions · Steps to reproduce · Expected result · Actual result · Severity · Priority · User impact · Root-cause hypothesis · Suggested owner · Reproduction notes · Redaction summary All fields are saved automatically to your browser's local database as you type — close the tab and reopen it without losing work. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ✨ OPTIONAL AI ASSISTANCE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Connect your own third-party API key to receive intelligent suggestions for title generation, rewritten summaries, clear reproduction steps, missing-info alerts, and triaging recommendations. All AI suggestions are completely optional and must be approved by clicking "Apply" before changing your draft. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 📤 EXPORT AND SUBMIT ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • Download your bug reports in formatted text documents, structured JSON files, or print-ready layouts. Formats are optimized to look clean when copy-pasted directly into popular developer issue trackers, wiki pages, and team documentation hubs. • Set up tracker credentials in Settings to submit tickets directly. BugSnap Pro always displays a complete preview of the exact JSON payload before firing a request, preventing accidental submissions or ticket spam. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 🔒 PRIVACY — LOCAL BY DEFAULT ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • No account, no sign-up, no telemetry • All data (screenshots, logs, drafts, API keys) stored locally in chrome.storage.local only — never synced, never uploaded • Network calls happen only when you explicitly trigger an AI-assist request or a ticket submission to your configured tracker • No analytics, no ads, no remote logging
Aug 17, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.