This page answers โwhat browser am I using?โ precisely: name, version, rendering engine, operating system, platform, user agent, language, time zone, and a capability checklist (JavaScript, cookies, local/session storage, touch, WebGL, WebRTC).
Why capabilities matter more than names
Modern development uses feature detection, not browser sniffing. Two Chrome installs can differ (one with WebGL disabled, one with cookies blocked). The checklist below tells developers what this specific browser can actually do right now โ far more useful than the version number alone.
If something shows โunsupportedโ
First check browser settings and extensions: content blockers disable storage and WebRTC; enterprise policies disable WebGL; private windows restrict storage. Then update the browser โ support varies by browser and version, and older releases lack newer APIs.
How this check works
Open this page and the embedded script queries only documented browser APIs. Nothing is installed, no account is needed, and results reflect your current browser profile โ including extensions, private mode and OS display scaling.
Limitations you should know about
Support varies by browser. Privacy features (tracking prevention, user-agent reduction, fingerprint randomization) can generalize or withhold values. Treat results as a best-effort live snapshot rather than a certified hardware inventory.
Privacy
Detection runs in your browser. We do not store fingerprints or device reports. The only network call any tool makes is the optional public-IP lookup on /my-ip, disclosed in the privacy policy.