Resources
Feature overview
English
Parsing
Parse any User-Agent string into a structured, human-readable format. Whether it's Safari on iPad, Chrome on Windows, search engine spiders, automation tools, or security scanners – we provide accurate identification of the browser, device, and operating system information.
-
-
-
-
-
-
-
-
-
Not detected
-
How do I read a User-Agent string? What information is in it?
The UA is a line of text sent with every request. It typically carries the browser name and major version, the rendering engine, the operating system and its version, and the device type. Drop it into a parser and you get those fields broken out one by one — much faster than reading the raw string, and much easier for spotting version mismatches.
Why does my UA mention both Chrome and Safari?
Legacy compatibility. Chromium-based browsers (Chrome, Edge, Opera and so on) keep a Safari token in the string so that older sites keying off it still behave. The Mozilla/5.0 prefix is the same story — a historical leftover, not a sign you're running Firefox.
Can a User-Agent identify one specific person?
Not on its own. UA strings have very low entropy — hundreds of thousands of people can share the exact same Chrome version and OS combination. It's better understood as a claim. The real risk is whether it agrees with everything else: a UA that says Windows while the rendering traits and platform fields say something else is where it becomes a problem.
How can I tell whether a UA belongs to a bot or a real browser?
How do User-Agent and Client Hints relate to each other?
