piapia123
en

User-Agent Parser

Web & Network

Everything runs locally in your browser — nothing is uploaded

Input
Output

Read a user agent string into a browser, version, operating system, device type and rendering engine — and see exactly which rules matched, so the conclusion is inspectable instead of a bare name. That matters, because a user agent is a line of text the client writes about itself: browsers copy each other on purpose (Chrome claims to be Safari, Edge claims to be both Chrome and Safari) and anything automated is free to lie. Treat the result as a rough hint, never as an authoritative check, and read the NOTES section before you rely on any of it.

Features

  • Browser and version, covering Edge, Opera, Samsung Internet, Vivaldi, Yandex and UC
  • Rendering engine: Blink, WebKit, Gecko, Trident, EdgeHTML or Presto
  • Operating system and version: Windows, macOS, iOS, iPadOS, Android, ChromeOS, Linux
  • Device type: desktop, mobile, tablet, bot or command-line client
  • Lists the matched rules so you can see what the conclusion was based on
  • Every result carries notes: which two systems cannot be told apart, which token is an imitation
  • Reports how many browser markers the string carries and which one won
  • Switch to JSON output to feed the result straight into a script

How to use

  1. Paste a user agent string into the input box
  2. Choose the output: a readable report or JSON
  3. Tick "List the matched rules" when you want to see the reasoning
  4. Read the NOTES section — it says what this particular result cannot tell you

FAQ

Can I trust this result?
No. A user agent is written by the client and can say anything: crawlers routinely pretend to be Chrome, and browsers deliberately borrow each other’s tokens. So "what was parsed" tells you what the string says, never what the client actually is. For anything that matters, use capability detection (checking whether an API exists) or User-Agent Client Hints instead of parsing the string.
Why does Edge claim to be Chrome and Safari?
It is a compatibility relic. Sites used to sniff the user agent to decide what to send, so new browsers copied existing tokens to be treated as something recognisable. Edge copied Chrome and Safari; Chrome copied Safari. This tool therefore matches the most specific rule first — Edge before Chrome — and reports how many markers the string actually carries.
Why can it not separate Windows 10 from Windows 11?
Microsoft never changed the NT version number for Windows 11, so both report Windows NT 10.0. Nothing in the string tells them apart, so the result says Windows 10 / 11 rather than guessing.
Why is Brave not detected?
Brave deliberately adds no token of its own; its user agent is byte-for-byte identical to Chrome’s, and several other Chromium-based browsers do the same. That is a design choice on their side, not a gap in this tool.
How is the device type decided?
Mainly from the Mobile token, keywords such as iPad or iPhone, and whether an Android string carries Mobile. One caveat worth remembering: since iPadOS 13, an iPad in desktop mode sends a string identical to a Mac’s, byte for byte — so any macOS result might really be an iPad.
Is the user agent uploaded?
No. Everything runs locally and the page makes no network requests.

Related tools