Bugtify — Visual Bug Reports with Debug Data

Record your screen while Bugtify silently captures console logs, network requests, and environment details. When you stop, everything is bundled into a single .bugtify file you can share through Slack, Jira, email — whatever your team already uses. Developers drop the file at bugtify.com/viewer and get a synced timeline: video playback alongside console output and network activity, displayed in a familiar DevTools-style interface. No signup. No cloud upload. Everything stays in the browser. WHAT BUGTIFY CAPTURES — Screen recording (WebM) of exactly what happened — Console logs, warnings, and errors with source locations — Network requests with headers, payloads, status codes, and timing — Page navigation: every URL visited during the session so developers can retrace the exact path — Browser version, OS and viewport size AI BUG DESCRIPTIONS (OPTIONAL) When enabled, Bugtify uses Chrome's built-in Gemini Nano model to draft a bug description from the console errors, network failures, and navigation events captured during your session. The model runs entirely on your device — nothing is uploaded — and the feature can be toggled off any time from the popup settings. HOW IT WORKS 1. Click the Bugtify icon and start a session 2. Reproduce the bug — Bugtify records in the background 3. Stop the session and click Download — that's it A title is generated automatically. With AI descriptions enabled, the description is drafted for you. Review, tweak the severity if needed, and the file is ready to share. THE .BUGTIFY FILE A single portable file that packages your screen recording and all debug data together. Share it any way you like. The recipient opens it at bugtify.com/viewer — drag, drop, done. BUILT FOR PRIVACY — Capture, AI generation, and export all happen locally in your browser — No data is sent to any server — No account needed — Sensitive data (passwords, tokens, API keys) is automatically masked WHO IS IT FOR — QA testers who want to create clear bug reports without technical knowledge — Developers who need full context to reproduce and fix issues fast — Teams tired of "can't reproduce" and "what browser were you using?"