Your user agent, shown as soon as the page opens
A user agent is the short ID card your browser hands to every website it visits: one line of text naming the program, its version, the operating system and sometimes the kind of device. This page answers "what is my user agent?" straight away: the full string appears at the top, under "Your user agent", exactly as your browser reports it.
Nothing is sent: every value is read by your browser and stays on your device, and the tool keeps nothing between visits.
What the tool shows
- Browser and device: the device type worked out from the string, the reported system, the likely browser and the rendering engine (as tokens taken from the string), the main and accepted languages, the time zone with its UTC offset, the reported cores and memory, and touch support.
- Client hints: the platform, the "Mobile" flag, the brands and versions reported and, when the browser allows it, the platform version, architecture and model.
- Screen and preferences: screen resolution, pixel density, window size, preferred dark mode and reduced motion.
- Supported features: cookies, local storage, WebGL, Web Audio, Service Worker, WebAssembly and the built-in PDF viewer, each with "Yes" or "No".
"Copy report" puts every line on your clipboard, ready to paste into a support ticket. For a detailed look at your display, open what is my screen resolution.
Parsing a pasted user agent
- Copy a string, for example from a web server access log or a bug report.
- Paste it into "User agent to parse", then click "Parse" or press Enter. "Use mine" fills the box with your own string.
- Read the table: "Device type", "Reported system", "Architecture", "Rendering engine (token)", "Likely browser (token)", "Products and versions" and "Details in brackets".
The parser works with patterns found in the text, so every answer is a piece of the string itself; nothing is made up. Two made-up strings show how it works:
| Pasted string | Device type | Other results |
|---|---|---|
MonRobot/2.1 (+https://exemple.fr/robot) | Bot or automated program | Likely browser: MonRobot/2.1 |
Lecteur/1.0 (Tablet; armv7l) | Tablet | Architecture: 32-bit (armv7l) |
How to read a user agent
A string is made of "Name/Version" tokens separated by spaces, plus details in brackets separated by semicolons. The brackets usually hold the system, its version and the architecture, such as x86_64 for a 64-bit processor. The tokens that follow name the rendering engine and then the browser. To stay compatible with old websites, nearly every browser copies its rivals' tokens. That is why one string often lists three or four products, and why the tool speaks of a "likely" browser.
Recent browsers also freeze part of the string to make tracking harder: the system version may be stuck on an old value, and the phone model may be replaced by a single letter. Client hints take over with more reliable values. A strange-looking brand full of dots and slashes is there on purpose: it checks that websites read the list properly instead of matching exact text.
What it is useful for
- Giving an online shop's or your bank's help desk the exact version of your browser.
- Checking that an extension which changes your user agent really works, or that your developer tools' mobile device mode is switched on.
- Spotting a crawler in your server logs, then writing the right "User-agent" rule with the robots.txt generator.
- Understanding why a website keeps sending you its mobile layout on a tablet.
FAQ
Can my user agent identify me?
Not on its own: millions of people share the same string. Combined with your language, time zone, screen resolution and supported features, though, it adds to a more distinctive "fingerprint". That is exactly what this page lets you see.
Why is my tablet detected as a computer?
Some recent tablets ask for the desktop version of websites by default, and send a desktop user agent to get it. The number of touch points under "Touch screen" still gives the touch screen away.
Why do client hints say "Not reported"?
Not every browser offers them, and some only expose them on HTTPS pages. In that case, only the classic string is available.
Is my information sent anywhere?
No. As on any website, your browser sends its user agent when the page loads, but the tool sends nothing back: the values shown and the parsing are worked out on your device.