User Agent Parser
Parse any User Agent string into browser, version, engine, OS and device type, or read your own.
User Agent string
Parsed fields
| Property | Value |
|---|
Notes
Parsed locally from the string you paste. UA strings are self-reported by clients and can be edited, so treat them as a hint, not proof.
How to use it
- Paste a User Agent string into the box, or press Read this browser to fill in the string your own browser sends.
- The fields update as you type; the Parse button re-runs the same analysis on demand.
- The table shows the browser and version, the rendering engine and its version, the operating system and version, and the device type.
- Read the notes below the table: they flag quirks such as shared Chrome and Safari tokens, Windows 10 and 11 reporting the same NT version, and iPad strings that look like a desktop Mac.
- Copy the report when you need to attach it to a bug report or a log entry.
Common use cases
- Log triage - turn raw access-log UA strings into readable browser and OS labels.
- Support replies - ask a user to paste their UA and read it without guessing.
- Bot screening - spot crawler and automation tokens before treating traffic as human.
- Compatibility checks - see the engine behind a string when a page misbehaves on one client.
Why it stays private
Parsing is plain string work done in this tab. The UA you paste is never sent anywhere, and the read-this-browser button only reads navigator.userAgent from the current page.
FAQ
Q: Why does a Chrome UA string contain Safari? A: Chrome and other Chromium browsers keep the AppleWebKit and Safari tokens so that sites with old sniffing code do not break. The parser checks Edge, Opera and Samsung tokens before Chrome, and Chrome before Safari.
Q: Can it tell Windows 10 from Windows 11? A: No. Both report Windows NT 10.0 and the build number is not part of the string, so the OS version column shows the shared label instead of guessing.
Q: My iPad shows up as a Mac. Is that wrong? A: iPadOS 13 and later can request the desktop site by default and reports a Macintosh string. The note under the table calls this out; a touch-only check on the device itself would be needed to be sure.
Q: Can the parser be fooled? A: Yes. A UA string is self-reported and any client can send an edited one, so treat the result as a hint. Bot patterns are checked first, but a custom client can hide them.
Your data stays on this device
User Agent Parser runs 100% locally. Everything you paste or drop is processed by your own browser and never transmitted. Nothing is stored on our servers — close the tab and it is gone.
Nothing you type is sent to a server, logged, or used for analytics. The page works even with your network disconnected after first load.