User-Agent Parser

User-Agent string

Browser
Engine
OS
Device type

<iframe src="https://olltools.com/embed/dev/user-agent-parser" width="100%" height="400" frameborder="0"></iframe>

Break a User-Agent string down into browser, engine, OS, and device type — and get flagged when it matches Chrome's frozen mobile pattern ("Android 10; K"), so a fixed placeholder value isn't mistaken for the device's real OS version or model.

How it works

Paste any User-Agent string, or click "Use my browser's UA" to fill in your own
Browser, engine, OS, and device type are broken out instantly
If the UA matches Chrome's reduced/frozen mobile pattern, a warning explains why the OS version and device model shown may not be real

Frequently asked questions

Why does the OS always show as "Android 10"?

Since Chrome 110, mobile User-Agent strings have their OS version and device model frozen to generic placeholders ("Android 10", "K") for privacy — it may not reflect the real device. This tool flags that pattern explicitly.

How do I get accurate device info?

Use Client Hints (the Sec-CH-UA-* HTTP headers) instead — the User-Agent string itself is being phased down in favor of this newer, opt-in standard.

How accurate is this parser?

Mainstream browsers and OSes parse reliably, but mobile device model/brand detection from a UA string alone is wrong or empty around 22% of the time industry-wide, according to device-detection research — treat results as a debugging aid, not ground truth for production decisions.

Is my User-Agent string sent to a server?

No — parsing runs entirely in your browser.

#UserAgentParser#UserAgentStringDecoderOnline#ChromeUserAgentReductionAndroid10K#UserAgentVsClientHints#ParseUserAgentStringFree

Related tools

From the blog

dev

"Android 10; K" isn't a real device — it's what Chrome shows everyone now

Since Chrome 110, most mobile User-Agent strings report a fixed, fake OS version and device model. A parser that doesn't flag this is quietly handing you placeholder data as if it were real.

2026-08-30

Update history

2026-08-30 Added: a cover image (a smartphone unrolling a UA string as a wavy-line ribbon through a magnifying glass, splitting into browser/engine/OS/device badges, one stamped with a warning triangle) — used as the card thumbnail, social share image, and blog title image.
2026-08-30 Launched: live User-Agent parser (no button) — browser/engine/OS/device-type breakdown with an explicit warning when a UA matches Chrome's frozen "Android 10; K" mobile pattern, plus honest accuracy caveats about UA-based device detection. Entirely client-side.