User-Agent Parser Online — Free
Runs 100% in your browser — your files never leave your device.
User-Agent strings compress browser, engine, platform, device, and compatibility history into one difficult line. Paste any string—or start with your current browser—to get the useful fields separated into a readable table.
How it works
- 1
Use or replace your User-Agent
- 2
Read the parsed browser details
- 3
Inspect platform and device fields
About this tool
What the parser extracts
Paste any User-Agent string and the tool breaks out what it claims: browser name and version, operating system, device type, and rendering engine. The parse runs on the same established patterns server libraries use, entirely in your browser.
Why UA strings deserve skepticism
User-Agent strings are self-reported and historically messy: browsers copied each other's tokens for compatibility, and privacy tools spoof or freeze them. Parse for trends and compatibility decisions, never for security or precise identification.
The modern direction
The industry is moving to Client Hints, which ask for reduced, explicit data instead of parsing a legacy string. For new work, prefer Client Hints or feature detection; keep UA parsing for analytics buckets and bot identification.
Frequently asked questions
Why does my browser claim to be another browser?
Historical compat: browsers copied rival tokens so old server checks would not block them, and the aliases stuck. The real identity sits in the meaningful tokens, which the parser extracts.
Can I detect bots reliably from the User-Agent?
Honest bots identify themselves (Googlebot, GPTBot) and the parser catches them — but self-declared identity is not proof. Verify important bots by reverse-DNS or IP ranges.
Do all browsers on my device parse to the same result?
They share the OS and engine tokens but differ in browser tokens. Freeze a couple of real strings and compare — the differences are the browser-specific part.