User Agent Parser

Your own User-Agent is already in the box. Paste someone else's from a log and see what it really says — the string is full of names that no longer mean what they say.

Parsing happens in the page: your string is not sent anywhere and not stored.

How to use

  1. Your own string appears automatically; paste a different one to check it.
  2. Read the browser, engine, operating system and device below.
  3. Press «Copy» to take the string, for example into a bug report.

Good to know

Why the string lies on purpose

Every browser claims to be Mozilla. Chrome claims to be Safari, Edge claims to be Chrome, and Safari claims to be KHTML. None of this is a bug: each layer was added so that a site written for the previous browser would not lock the new one out. The consequence is that the order of checks decides the answer — look for Chrome before Edge and every Edge in your logs becomes a Chrome.

Where the string stops being enough

Since iPadOS 13, an iPad reports exactly what a desktop Mac reports. The only difference a page can see is that the iPad has touch points, and that is what this parser uses. Chrome now freezes the version and the platform in the string as well, which is why a modern browser tells you less than one from ten years ago.

Frequently asked questions

Why does the version look wrong or too round?

Browsers have begun freezing the minor version in the string to make fingerprinting harder. The major number is real; the digits after the dot often are not.

Can I trust the User-Agent for access control?

No. Anyone can send any string, and the developer tools of every browser let you change it in two clicks. Use it for statistics, never for decisions.

The string is marked as a bot — what does that mean?

It contains a known crawler or tool marker: a search engine, a monitoring service, curl or a script library. This is how a log tells visitors from machines.

Is my string sent anywhere?

No. Parsing happens in the page — nothing is transmitted or stored.

Related tools