Browser diagnostic
Full report: permissions, Web APIs, codecs, GPU, storage.
Identity
Permissions queried without prompting
Supported Web APIs
Codec support
Video (playback)
Audio (playback)
Storage
Graphics
Network
Hardware
Display & preferences
Locale
Fingerprint surface
Computed locally, never transmitted. This section shows what signals a tracker could use to identify this browser. We hash each signal and discard the inputs — the hashes here never leave your device.
About this tool
A complete snapshot of what your browser can and cannot do. This diagnostic queries permissions without triggering a prompt, feature-detects around 30 Web APIs, reports codec support for the major video and audio formats, and reads storage quotas, GPU info, network conditions, hardware hints, locale, and display preferences. Export the whole report as Markdown to paste into a GitHub issue, or as JSON for programmatic comparison. Useful when a web app works for your colleague but not for you — run this on both machines and diff the reports.
Frequently asked questions
Why does this matter for web development?
When a web app behaves differently for two users on the same site, it's almost always a capability difference: a codec, a permission, a storage quota, an API that isn't shipped in one of the browsers. Running this report on both machines and diffing the output usually finds the cause fast.
What's the fingerprint surface section about?
It shows what signals a tracker could in principle use to identify this browser across sites — canvas rendering, WebGL renderer, audio processing. We hash each signal locally and display the hash; the raw inputs and the hashes never leave your device.
Does running this leak my data?
No. Every check runs locally. No network request carries the report or any of the individual signals. The only outgoing traffic is the single cookieless analytics ping for the page view itself.