User Agent Parser
See your browser's user agent string and break any user agent down into browser, version, rendering engine, operating system and device type. Free, instant and private — parsing happens entirely in your browser.
Your own user agent is loaded automatically. Edit it or paste another string to parse it live.
How to use the user agent parser
- Read your own details. When the page loads, your browser's user agent is parsed automatically and shown in the boxes below.
- Parse another string. Paste any user agent into the box — from a log file, an analytics report or another device — and the breakdown updates instantly.
- Copy what you need. Use Copy string to grab the raw user agent, or read off the detected browser, engine, OS and device.
About this tool
A user agent is a line of text every browser sends with each request that identifies the browser, its version, the rendering engine and the operating system. It looks cryptic — full of names like Mozilla, AppleWebKit, KHTML and Gecko for historical reasons — but it packs a lot of information. This parser applies the same detection patterns analytics tools use to pull out the browser (Chrome, Safari, Firefox, Edge, Opera, Samsung Internet and more), the rendering engine (Blink, WebKit, Gecko or Trident), the operating system with its version, and whether the device is a desktop, tablet or phone.
Parsing runs entirely in your browser with plain JavaScript — no user agent you enter is uploaded, logged or stored, so you can safely analyse strings from private logs. User agent strings are hints, not guarantees: they can be spoofed, frozen for privacy, or reformatted by new browser versions, so treat unusual results as best-effort estimates. For feature decisions, prefer capability detection over reading the user agent.
Frequently asked questions
What is a user agent string?
It is a text label your browser sends to every website describing itself — for example the browser name and version, the layout engine and your operating system. Servers use it for analytics, compatibility tweaks and blocking bots.
Why does Chrome's user agent mention Safari and Mozilla?
For historical compatibility. Early sites checked for "Mozilla" and "Safari/AppleWebKit" to serve modern pages, so Chrome, Edge and others include those tokens to avoid being locked out. That is why nearly every user agent starts with "Mozilla/5.0".
Can a user agent be faked?
Yes. Browsers let users or extensions override it, developer tools can spoof any device, and bots often impersonate real browsers. So a user agent should be treated as a helpful hint rather than proof of the actual browser or device.
Why can't it tell iPad from Mac in newer Safari?
Since iPadOS 13, iPads request the desktop version of sites and send a Mac-style user agent by default. Without other signals the string genuinely looks like a Mac, so any parser (including this one) may report it as a desktop.