Results are provided for informational purposes only and may contain errors. Please verify important information independently. Use of this tool is at your own risk.
What the User Agent Parser does
The User Agent Parser reads a browser's User-Agent string and shows the browser, the rendering engine, the operating system and the device type (desktop, mobile or tablet). The page opens with your own browser's User-Agent, so you can see how your current setup is identified; paste any other string to parse it instead.
It recognises Chrome, Edge, Opera, Firefox, Safari and Internet Explorer; the Blink, WebKit, Gecko and Trident engines; and Windows, macOS, iOS, Android and Linux. Chromium-based browsers still include the word AppleWebKit for historical reasons, so the parser reports their real engine, Blink. The analysis is pattern-based and runs in your browser.
When to use it
- Reading User-Agent strings from server logs or analytics exports.
- Checking which browser and OS a customer used when they reported a bug.
- Testing browser-specific code with User-Agent strings of other devices.
- Spotting crawlers and bots, whose strings do not match any real browser.
Worked example
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36
Browser: Chrome Engine: Blink Operating System: Windows Device type: Desktop
Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.5 Mobile/15E148 Safari/604.1
Browser: Safari Engine: WebKit Operating System: iOS Device type: Mobile
Common questions about the User Agent Parser
Why does every browser string start with Mozilla/5.0?
It is a leftover from the 1990s, when servers sent better pages only to Netscape (Mozilla). Other browsers copied the token to get the same pages, and it has stayed for compatibility ever since.
Why does Windows 11 show as Windows NT 10.0?
Browsers froze the Windows version in the User-Agent, so Windows 10 and 11 send the same string. Sites that need the difference must use User-Agent Client Hints.
Can I trust the User-Agent for security decisions?
No. Any client can send any string, and browser extensions and bots routinely fake it. Use it for statistics and debugging, never for access control.
Should my site detect browsers by User-Agent?
Prefer feature detection, such as checking whether an API exists in JavaScript or using CSS @supports. It keeps working when new browsers or versions appear.
Is this tool free?
Yes, it's free to use. No signup, no email required. Get results on this page.
How do I get my result?
Use the tool on this page. Your result appears here; no email delivery is required.