User Agent Parser
Parse any user-agent string into browser, engine, operating system and device — or detect your own. Runs entirely in your browser.
About the User Agent Parser
This user-agent parser breaks a UA string down into its meaningful parts: the browser and version, the rendering engine, the operating system and version, and the device type (desktop, mobile, tablet or bot). Paste any user-agent from a server log, or click a button to parse your own browser's.
User-agent strings are notoriously cryptic — a single Chrome-on-Windows string mentions Mozilla, AppleWebKit, KHTML, Gecko and Safari for historical compatibility. This tool cuts through that noise and tells you what actually sent the request.
Parsing runs entirely in your browser with pattern matching, so nothing is uploaded. It's useful for debugging analytics, reproducing user issues and understanding traffic in your logs.
How to Use the User Agent Parser
- 1Paste a user-agent string, or click to use your own browser's.
- 2Run the parser to break it into components.
- 3Review the browser, engine, OS and device details.
- 4Copy the parsed summary.
Frequently Asked Questions
What information can be extracted from a user-agent?
The browser name and version, the rendering engine (Blink, WebKit, Gecko), the operating system and version, and the device category (desktop, mobile, tablet or bot). It's an approximation, since UA strings are self-reported and can be spoofed, but it's accurate for the vast majority of real traffic.
Why do all browsers claim to be 'Mozilla'?
For historical reasons. In the 1990s servers sent richer pages to 'Mozilla'-compatible browsers, so every browser started its UA string with 'Mozilla/5.0' to qualify. The tokens for AppleWebKit, KHTML, Gecko and Safari that follow are similar compatibility leftovers. The parser knows to look past them.
Can user-agent strings be trusted?
Not fully. A UA is set by the client and can be freely changed, so it's fine for analytics and debugging but should never be used for security decisions. Bots and privacy tools often send generic or fake strings. Treat parsed results as best-effort, not proof.
How do I find my own user-agent?
Click the button to parse your current browser's navigator.userAgent — the tool reads it directly and shows the breakdown. This is a quick way to see exactly what your browser reports to the sites you visit.
Is the user-agent I paste uploaded anywhere?
No. Parsing runs entirely in your browser with local pattern matching. Nothing is sent to a server, so it's safe to paste strings from private server logs.