User-Agent Detector

The User-Agent Detector reads the User-Agent string your current browser sends, shows it exactly as it is, and uses a small set of rules to identify the browser, operating system and device type (mobile or desktop). It only inspects the browser you are using right now. You cannot paste someone else's string into it, and it cannot change or spoof your UA. The detection is a few lines of pattern matching, a rough but useful guess rather than a full UA-parsing library.

How to use it

1. Open the page. There is nothing to type, and your browser information appears automatically.
2. Under "Detection result" you will see three items: Browser, OS and Device type.
3. Under "Full User-Agent string" you can see the raw string your browser sends.
4. Click "Copy" at the top right to copy the string to the clipboard. The button briefly changes to "Copied". If the browser blocks clipboard access the copy silently fails, and you can select and copy the text by hand.
5. To see the UA of a different browser or device, open this page in that browser or device.

Detection rules and examples

The browser is decided in order: Edg/, EdgA/ or EdgiOS/ means Microsoft Edge, then OPR/ means Opera, then Chrome/ or CriOS/ means Google Chrome, Firefox/ or FxiOS/ means Mozilla Firefox, and Safari/ without Chrome/ means Safari. The OS is checked as Windows NT, then Mac OS X (excluding iPhone and iPad; a Macintosh string with multi-touch is treated as iPadOS and shown as iOS), then iPhone/iPad, Android, CrOS (ChromeOS) and finally Linux. Anything containing Mobile, Android, iPhone or iPad, or detected as iPadOS, counts as a mobile device. We ran these rules on a few typical strings: Chromium-based Edge on Windows with Edg/ gave Microsoft Edge, Windows, Desktop; Safari on an iPhone gave Safari, iOS, Mobile; Firefox on Linux gave Mozilla Firefox, Linux, Desktop; and Chrome on a Pixel phone gave Google Chrome, Android, Mobile.

Supported features and known limits

• Only five browsers (Edge, Opera, Chrome, Firefox, Safari) and six OS families (Windows, macOS, iOS, Android, ChromeOS, Linux) are recognised. Anything else shows "Unknown browser" or "Unknown OS".
• Chrome on iOS (CriOS/), Firefox on iOS (FxiOS/) and Edge on Android and iOS (EdgA/, EdgiOS/) are recognised. Samsung Internet and in-app browsers such as WeChat or QQ are still grouped under Chrome or another category.
• Safari on recent iPads identifies itself as a Mac by default; the tool treats a Macintosh string with maxTouchPoints above 1 as an iPad (shown as iOS, Mobile). It can be wrong if touch information is hidden or on desktop browsers in touch-emulation mode.
• It gives only the browser name. Version, engine and device model are not parsed; read the version in the full string.
• Some browsers are reducing the detail in the User-Agent, and users or extensions can change it, so the output may not reflect the real environment.

Why does Chrome's UA say Mozilla and Safari?

It is historical compatibility. Early websites used the UA to decide whether to serve full features, so later browsers added Mozilla, AppleWebKit and Safari tokens to avoid being excluded. That is why the tool must test for Edg/, OPR/ and Chrome/ before it can test for Safari.

Can I use the result to decide how to adapt my website?

Only as a hint. Modern front-end practice favours feature detection and responsive layouts over branching by UA. UA detection is handy for quickly confirming the environment of yourself or a user, for instance when passing details to a developer.

My device was identified wrongly. Is the tool broken?

Most likely it is one of the cases in the limits above. Copy the full string and look for keywords to work out what it really is.

Can it parse a UA string someone sent me?

No. It only reads navigator.userAgent from the current browser, and the page has no input box.

Privacy and how your data is handled

The User-Agent is read by your browser and shown only on your page. The code makes no request that sends it to a server and does not store it. Note that your browser already sends its UA to every website you visit along with each request, so it is not secret, though you may still want to think before sharing it with others.