Raw and parsed values
The full string is kept separate from browser family, reported version, operating-system family and version tokens. The parser follows recognizable tokens and does not look up your installed browser or operating system.
BrowserCheck · Browser environment diagnostics
User Agent Checker
View your browser's User Agent, parsed browser and OS family, reported versions and available User-Agent Client Hints side by side.
This checker displays navigator.userAgent and parses recognizable browser and operating-system tokens. When User-Agent Client Hints are available, it shows them alongside the string. The results describe what this page can read, not a verified identity of your device.
Results in this browser
Running local checks…
Copied and printed output omits IP addresses, the full User Agent, exact versions, fingerprint hashes, and precise location.
What is tested and how to read it
Reduction and compatibility
A browser can freeze or reduce version and platform tokens for compatibility and privacy. Chrome-like tokens can appear in other Chromium browsers. A macOS or Windows version token may not match the actual installed system.
Client Hints beside User Agent
Client Hints brands, mobile and platform are a separate source. Higher-entropy fields are requested when available, and omitted or denied fields stay unavailable. Differences between these sources are not automatically evidence of spoofing.
Safe sharing
The live string and exact versions are marked as private for printing. The safe summary shares browser and OS family only; use the support report when asking someone to diagnose a website problem.
Test limitations
- Browser settings, extensions, automation and profile tools can change reported values.
- The local JavaScript User Agent is not a capture of this request's HTTP User-Agent header.
- An absent Client Hints API is common in some browser engines and is not a failed privacy test.
Next steps
- Read the raw token and parsed field together before relying on a version or platform value.
- Use Client Hints for an additional observation, and prefer feature detection when choosing application behavior.
Frequently asked questions
Why can Brave show up as Chrome?
Chromium browsers often share compatibility tokens. A User Agent parser can recognize the Chrome token without identifying the product that emitted it.
Why does the operating-system version look old?
Some browsers report reduced or frozen platform tokens. This checker labels them as reported values and does not infer the installed version.
Should a website use this string for capability checks?
Feature detection is generally a better way to check an API. A string can be modified and a browser family alone does not guarantee a feature.