User-Agent Parser
Paste any user-agent string to break it down into the browser, rendering engine, operating system and device. Your own browser's UA is parsed automatically.
About this tool
A user-agent parser takes the cryptic User-Agent header a browser sends and decodes it into readable parts: the browser and version, the rendering engine, the operating system, and the device type. UA strings are notoriously messy — every browser pretends to be several others for historical reasons — so a parser saves you from deciphering them by hand.
What you can learn
From a single UA string you can identify whether a visitor used Chrome, Firefox, Safari or Edge, on Windows, macOS, Linux, Android or iOS, and whether it was a phone, tablet or desktop. This is useful for analysing server logs, debugging device-specific bugs, and understanding the traffic hitting your site.
Why UA strings look so strange
Most user-agents start with "Mozilla/5.0" and mention multiple engines (like "AppleWebKit" and "Gecko") even when only one applies. This is decades-old compatibility cruft, which is exactly why automated parsing is more reliable than reading them yourself.
Frequently asked questions
It decodes a User-Agent string into structured information — the browser and version, rendering engine, operating system and device type — so you don't have to interpret the raw string manually.
For historical compatibility. In the 1990s servers checked for 'Mozilla' to send modern pages, so every browser began claiming to be Mozilla-compatible. The convention stuck, which is why UA strings are confusing and need parsing.
Yes — the tool pre-fills your current browser's user-agent automatically, so you can see exactly what your browser reports to every website you visit.
It is good for broad browser/OS/device breakdowns, but UA strings can be spoofed or frozen (browsers increasingly reduce their detail), so treat parsed results as a strong signal rather than absolute truth.