Input
Paste a user agent
Ready to parse locally.
Developer utility
Identify browser, operating system, device, rendering engine, CPU architecture, and common bots, then inspect tokens and export structured JSON locally.
Input
Ready to parse locally.
Paste a user agent to inspect browser and platform hints.
Parsed identity
Version unknown
Version unknown
Type unknown
Version unknown
Architecture hint
No common crawler or automation signature found
Normalized fields
| Field | Value | Meaning |
|---|
Modern browser data
Client Hints belong only to the browser running this page. High-entropy values are requested only when you press the button.
Press Read current hints to inspect data exposed by this browser.
Raw structure
| # | Type | Name | Version / value |
|---|
Structured output
Examples
| Token | Typical meaning | Important limitation |
|---|---|---|
Mozilla/5.0 | Historical compatibility prefix used by most browsers. | Does not mean the browser is Firefox. |
AppleWebKit/537.36 | WebKit compatibility token used by Chromium browsers. | Chrome and Edge use Blink despite this token. |
Chrome/x | Chromium or Chrome product version. | Also appears in many Chromium-based browsers. |
Safari/x | Safari compatibility or build token. | Use Version/x for the marketed Safari version. |
Windows NT 10.0 | Modern Windows platform token. | Windows 10 and 11 may share this reduced token. |
Mobile | Common mobile form-factor hint. | Its absence does not guarantee a desktop device. |
No. Parsing, token analysis, bot detection, Client Hints display, and JSON generation happen locally.
Not always. Modern Chromium browsers commonly report Windows NT 10.0 on both Windows 10 and 11.
Yes. Browsers, extensions, automation tools, proxies, and HTTP clients can send any string. Treat results as hints.
Prefer feature detection and responsive design. UA parsing is useful for analytics, diagnostics, logs, and crawler classification.