BrowserTrace

Reproduce the bug. BrowserTrace records what happened. BrowserTrace is a privacy-first debugging recorder for your browser. It automatically captures and correlates the errors, network failures, console messages, and navigation events that happen during a bug, so you can understand exactly what went wrong without keeping Chrome DevTools open the whole time. Intermittent bugs are hard to catch. By the time you open DevTools, reproduce the issue, and scroll through hundreds of network requests, the moment has passed or the page has already redirected and the evidence is gone. BrowserTrace solves this by quietly recording in the background, so the full picture is there the moment something breaks. HOW IT WORKS Click "Start Recording" Use your site normally Something breaks Click "Stop Recording" Review a clear, correlated timeline of exactly what happened Generate a shareable bug report in one click WHAT IT CAPTURES • JavaScript errors and unhandled promise rejections • Console errors and warnings • Failed network requests and resources • Page navigations and redirect chains • Tab creation, switching, and cross-tab activity • Page lifecycle events KEY FEATURES • Chronological, correlated timeline:- see errors in the context of what led to them, not as an isolated stack trace • Automatic failure-chain detection:- links related events like a failed API call → console error → redirect, so you can trace root causes faster • Session health summary:- instantly see if a page is Healthy, has Warnings, or is Broken • One-click bug report generation:- copy or export a structured report (JSON/TXT) to share with your team • Search and filter events by severity, type, request, or error message • Works across tabs and redirects, so you don't lose context when the page changes PRIVACY BY DESIGN BrowserTrace is local-first. Your debugging data stays on your machine in local browser storage, nothing is sent to a server, and there's no telemetry by default. Sensitive data like passwords, cookies, authorization headers, API keys, and request/response bodies are never recorded. You control which sites are recorded with domain allow/block lists, and you can pause recording or delete sessions at any time. WHO IT'S FOR • Frontend developers (React, Vue, Angular, Next.js, Svelte, and more) • Full-stack developers tracing issues across frontend, API, and auth layers • QA engineers documenting reproduction steps • Support engineers who need to understand "what happened in the customer's browser" without asking them to open DevTools BrowserTrace isn't trying to replace Chrome DevTools, it's a lightweight flight recorder that sits alongside it, so you never have to guess what happened before the crash.