User Agent Parser
Parse any user agent string — browser, version, engine, OS and device. Yours is pre-filled.
Decode any user agent string into browser, version, engine, operating system and device type. Useful for debugging, web analytics and understanding exactly what is visiting your site.
Parsed locally from the user agent string your browser sends.
How to use the User Agent String Parser
- Paste a user agent string.
- Browser, engine, OS and device are parsed instantly.
- Use it to debug 'unsupported browser' issues or segment your visitors.
Frequently asked questions
What is a user agent string?
A header every browser sends identifying itself: browser, version, rendering engine, OS and device. It is how sites know what you are using.
Where do I find a user agent string?
In your browser's dev tools (Network tab), in server logs, or by searching 'my user agent'. This page also shows your own UA at the bottom.
Can user agents be spoofed?
Yes — browsers, bots and VPN extensions can send any UA. Treat the string as a hint, not proof.
Why does Chrome's UA mention AppleWebKit?
All Blink-based browsers (Chrome, Edge, Opera) keep legacy tokens like AppleWebKit for compatibility.
Fun facts about User Agent Parser
- The User-Agent string was first defined in HTTP/1.0 (RFC 1945, 1996) and has been growing longer and more complex ever since.
- Every major browser's user agent still starts with 'Mozilla/5.0', a leftover from the 1990s, when sites sent advanced pages only to browsers that identified as Mozilla (Netscape).
- User-Agent sniffing (detecting browsers from their UA string) is considered unreliable — feature detection is the recommended approach for web development.
- Google Chrome's User-Agent string contains 'Mozilla/5.0', 'AppleWebKit', 'KHTML, like Gecko', and 'Safari' — a historical artifact of browser compatibility layers.
- The User-Agent Client Hints API (UA-CH) is gradually replacing the User-Agent string, providing browser/OS info in a more structured and privacy-friendly way.