glitched.wtf · Developer Tools
5 items
Local-first bug reporting tool. Capture screenshots, record tabs, and collect debug info — all stored locally. Glitch — Local-first bug reporting for developers Stop sending "it's broken" tickets. Capture a bug once and get everything a developer needs to reproduce it — a screenshot or screen recording plus a complete technical debug log — saved right on your own machine. Glitch is local-first: your screenshots, recordings, and debug data stay on your device by default. Nothing is uploaded during capture, and nothing leaves your machine unless you explicitly share it — or turn on the optional Google Drive backup, which saves to your own Google Drive. 📸 WHAT YOU CAN CAPTURE • Screenshots — full-page or a selected area • Screen recordings — record any tab, with optional microphone narration • Instant replay — capture the moments right before the bug happened • Self-contained reports — saved as a single HTML file you can open offline or attach anywhere 🔍 AUTOMATIC DEBUG CONTEXT The details that actually make bugs reproducible, captured for you: • Console logs (log, warn, error, info, debug) • Network requests — URLs, methods, status codes, request/response headers and bodies • User actions — clicks, inputs (passwords masked), scrolls, and navigation • Performance — Core Web Vitals (LCP, CLS, INP, FCP, TTFB), long tasks, navigation timing • WebSocket messages • Storage snapshot — localStorage, sessionStorage, and cookies • Environment — browser, OS, viewport, device pixel ratio, memory, CPU cores, network type, timezone, locale 🔒 PRIVATE BY DEFAULT • Everything is stored locally — your browser storage and your Downloads folder • No Glitch server receives your captures • Sensitive values (authorization headers, API keys, tokens, cookies, and known vendor secret formats) are automatically redacted before anything is saved 🔗 SHARE TO YOUR TEAM'S TOOLS (only when you choose) When a report is ready, send it straight to the issue tracker or chat tool your team already uses — Glitch works with Slack, Jira, GitLab and a lot more. Each report goes directly from your browser to the service through your own access token, so Glitch never receives it. 💎 PLANS • Free — unlimited captures, forever. All the core capture and debug features above, with no monthly limit. • Pro — everything in Free, plus team integrations, all recording quality tiers, longer recordings and instant replay, and Google Drive backup (auto-save your captures to your own Drive and share them with one link). Sign in with Google to manage your plan and upgrade anytime. Built for developers, QA engineers, and support teams who are done with vague bug reports. Capture the bug. Share the fix. 💬 SUPPORT & CONTACT Questions, bugs, or feature requests? We read every message. • Help & FAQ — https://glitched.wtf/support • Website — https://glitched.wtf • Email — support@glitched.wtf
Jul 8, 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.