User-Agent Parser (Browser, OS & Device Detector)
Shows the navigator.userAgent of your browser automatically and breaks it down into browser, OS, rendering engine, and device type. You can also paste a User-Agent string from a server log or a support request to identify it. Everything is processed in your browser, and the UA is never sent to a server. For screen size and DPR, use the Screen Size & Viewport Checker; to inspect full HTTP headers, try the HTTP Header Analyzer.
🔒 Runs in your browser · Your data is never sent to a server
Your browser
| Browser | |
|---|---|
| Rendering engine | |
| OS | |
| Device type | |
| Device model |
Client Hints (userAgentData)
This browser does not support navigator.userAgentData (for example Firefox and Safari), so Client Hints are not available.
| Brands and versions | |
|---|---|
| Platform | |
| Architecture | |
| Device model | |
| Mobile device |
Parse a User-Agent string
Enter a User-Agent string and the result will appear here.
Notes
- A User-Agent is self-reported and easy to spoof or change. Detection here is a regular-expression estimate, so do not rely on it for security decisions or access control.
- Chrome and some other browsers reduce the User-Agent: Windows 10 and 11 look identical ("Windows NT 10.0"), macOS is always "10_15_7", and Android device models may show as "K".
- Safari on iPad identifies itself as "Macintosh" by default, so a pasted string alone cannot be told apart from a Mac. For your own browser, the touch point count is also used to detect iPadOS.
- Browsers that look like another browser (mostly Chrome) in the UA, such as Brave, Arc, and many in-app browsers, cannot be told apart reliably. Anything not recognized is shown as "Unknown".
Glossary
User-Agent
A string identifying the browser, OS, and device, sent in the HTTP `User-Agent` header and exposed as `navigator.userAgent`. For historical compatibility reasons it starts with `Mozilla/5.0` and has a convoluted format.
Client Hints (userAgentData)
A more structured way to read device information, introduced as User-Agent strings are being reduced. `navigator.userAgentData` gives basic data and `getHighEntropyValues()` returns details such as the OS version and architecture. Mostly supported by Chromium-based browsers.
Rendering engine
The core of a browser that interprets HTML and CSS and draws the page. Chrome, Edge, and Opera use Blink, Firefox uses Gecko, and Safari uses WebKit. On iOS, every browser uses WebKit.
FAQ
Why can't Windows 10 and Windows 11 be told apart?
Both report "Windows NT 10.0" in the User-Agent string. Telling them apart requires the platformVersion from Client Hints (userAgentData), which the "Your browser" section shows as "Windows 11" in browsers that support it.
Why is my iPad detected as a Mac?
Safari on iPadOS 13 and later identifies itself as "Macintosh" by default, so a pasted string alone looks like a Mac. For your own browser, this tool also checks the touch point count to detect iPadOS.
Brave or Arc shows up as "Chrome".
These browsers send a User-Agent that is almost identical to Chrome's, so they cannot be distinguished from the string alone. Detection is an estimate based on the tokens in the string.
Why are Client Hints not shown?
navigator.userAgentData is mainly supported by Chrome, Edge, and other Chromium-based browsers; Firefox and Safari do not provide it. High-entropy values may also be unavailable on non-HTTPS pages.
Share this page