Read a user-agent string: browser, engine, OS, device type and whether it is a bot
Runs in your browser. Nothing you type is sent anywhere. Updated on 25 Oct 2026.A user-agent string is a decades-old mess that still identifies every visitor. Paste one to read the browser, engine, operating system, device type and whether it is a bot, 5 facts from 1 line. Parsed in your browser, so a log line stays private.
Paste a user-agent string into the box, or choose one under "Common strings to try".
Read What it says: browser, version, engine, operating system, device type and any bot.
Check the badge under the box to see how much of the string was recognised.
Press Copy result, or Ctrl+Enter, to take the parsed fields as text.
Paste a user-agent string and this parser tells you the browser and version, the rendering engine, the operating system and version, the device type, and whether the sender is a known bot. It reads the string in a fixed order, most specific token first, because every browser puts other browsers' names in its own string on purpose.
Use it when an access log throws up a line you do not recognise, when you are testing how your own detection code behaves, or when a support ticket arrives with a string attached. The bot list covers search crawlers, AI crawlers, SEO tools, social link previews, uptime monitors, headless browsers and plain HTTP libraries such as curl, Postman and python-requests.
The tool is deliberately honest about what the string cannot tell you. Windows 11 still reports Windows NT 10.0. Safari has reported macOS 10.15.7 since Big Sur, whatever version is really running. Chrome on iOS is WebKit, because iOS allows nothing else. Chromium froze the version digits at 0.0.0 in 2022. An Android tablet is told from a phone only by the absence of the word "Mobile". Each of these appears as a note against the string you paste.
Anything you paste stays in the page: there is no lookup service behind this, no database call and no network request of any kind. For anything you plan to act on, use feature detection, and use the Sec-CH-UA client hints listed on the page for platform details the string cannot give you.
Read it from the most specific token backwards. Chrome sends Mozilla, AppleWebKit, Chrome and Safari; Edge adds Edg on the end. The last brand token is usually the real browser. Paste the string here and each part is separated for you, with the parts that are only compatibility fossils marked as such.
No. Microsoft kept the platform token at Windows NT 10.0 for Windows 11, so no user-agent string distinguishes them. The only reliable source is the Sec-CH-UA-Platform-Version client hint, which your server must request with an Accept-CH header first.
Apple froze the version reported in the user-agent string when Big Sur shipped, to stop sites blocking new releases they had not tested. Chrome on macOS does the same. So 10_15_7 means "macOS, version withheld", not Catalina.
Only for polite bots. Anyone can send any string, including Googlebot's. Real verification is a reverse DNS lookup on the requesting IP address, checked forward again, against the ranges the search engine publishes. Treat the name in the string as a hint, never as proof.
Feature detection for anything about capability: test for the API you want to call. For platform facts, use User-Agent Client Hints, which give brands, mobile flag, platform, platform version, full versions and device model, and are requested per site rather than broadcast to everyone.
No. The whole parser is JavaScript in this page and it makes no network request. Nothing is logged, stored or looked up in a remote database, which is also why it works offline once the page has loaded.
Still stuck? Ask about User-Agent Parser and anybody who knows can answer. No account needed.
On the related tools: Readability Checker – Flesch reading ease and grade level, with what to change · Commitlint Online – Run commitlint with config-conventional on a commit message, without installing anything.
Also works as: User-Agent Lookup.
In the collection Debug and Inspect.