User-Agent parser
Browser, OS and engine extracted from a User-Agent string.
- Instant
- Free
- Private (processed locally)
- No sign-up
Read your browser’s ID card
On every visit, your browser announces itself with a cryptic “User-Agent” string. This tool translates it into plain language: browser and version, operating system, rendering engine and device type. Yours is already loaded — edit it to analyse any UA.
-
Your UA is prefilled
Or paste a string pulled from a server log.
-
Read the analysis
Four cards: browser, system, engine, device.
-
Spot the robots
Crawlers and bots are flagged separately.
What the tool extracts
- Browser and version: Chrome 120, Firefox 121, Safari 17…
- System: Windows, macOS, Android, iOS, Linux.
- Rendering engine: Blink, WebKit, Gecko.
- Device: desktop, mobile, tablet or robot.
Pattern-based detection: reliable for common cases, but a User-Agent can be faked. Everything is analysed locally, no string is sent — handy for dissecting logs without leaks.
Frequently asked questions
What is a User-Agent?
It is a text string your browser sends to every site it visits to identify itself: its name, its version, your operating system. Sites use it (sparingly) to adapt the display or for statistics.
Why do all User-Agents contain “Mozilla”?
For historical compatibility reasons. In the 1990s, sites reserved features for Netscape (code name “Mozilla”). Every browser ended up pretending to be it, and the legacy stuck: “Mozilla/5.0” opens almost every modern UA.
What is the rendering engine?
It is the component that turns HTML/CSS into pixels. Three dominate today: Blink (Chrome, Edge, Opera), WebKit (Safari) and Gecko (Firefox). Knowing the engine often explains why a site renders differently across browsers.
Is detection always accurate?
No: User-Agents can be modified, and their format has changed a lot. This tool recognises common cases by pattern, but an exotic or deliberately faked UA may give a partial result. It is a hint, not a proof.