User-agent parser
Detect and parse Browser, Engine, OS, CPU, and Device type/model from an user-agent string.
About User-agent parser
Decodes a browser User-Agent string into the browser name and version, rendering engine, operating system, device type and model, and CPU architecture, using the ua-parser-js library. Your own browser's string is filled in by default.
When you would use it
- Finding out which browser and OS a user had when reading a bug report or a server log line.
- Checking what your own browser announces about itself.
- Building or testing device-detection rules against real User-Agent strings.
How to use it
- Paste a User-Agent string, or keep the one pre-filled from your browser.
- Read the cards: Browser, Engine, OS, Device and CPU.
- Empty fields mean the string does not carry that information.
Things worth knowing
- User-Agent strings are self-declared and often misleading on purpose: every modern browser claims to be Mozilla, Chrome-based browsers include Safari and AppleWebKit, and Edge includes Chrome. Trust the parsed result over the raw text.
- Since 2021 Chrome freezes parts of its string (reduced User-Agent): the Android and Windows versions are no longer precise, and the minor browser version is always 0. Device model is usually missing on Android.
- Desktop browsers rarely report a device type; empty Device fields are normal on a PC.
- Parsing is heuristic and depends on the library's rules, so very new browsers or unusual apps may be partly misidentified.
Frequently asked questions
- Why does my iPad show up as a Mac?
- Since iPadOS 13, Safari on iPad requests desktop sites and uses a Mac-like User-Agent string. The string itself no longer says iPad, so no parser can tell.
- Why does the OS version look wrong?
- Chrome and Chromium-based browsers report frozen, generic OS versions (for example Windows 10 for Windows 11). The precise version is only available through Client Hints, not the User-Agent string.