Paste any User-Agent string, or use your own browser's, and see the browser, rendering engine, operating system and device type parsed out in plain language.
| Category | Detected value | Matched pattern / text |
|---|
Parsing runs entirely in your browser with regular expressions — nothing is sent anywhere.
Detects Chrome, Edge, Firefox, Safari, Opera and Samsung Internet in an order that avoids common misdetection.
Reports the rendering engine and operating system version alongside the browser itself.
Flags mobile, tablet or desktop based on the tokens real browsers actually send.
Start with your own browser, or paste one you found in a server log or support ticket.
The User-Agent header has accumulated three decades of compatibility tokens, so almost every browser's string contains references to other browsers it is pretending to be compatible with. Chrome's string says Safari. Edge's string says Chrome and Safari. This tool checks the most specific, hardest-to-fake tokens first (like Edg/ or OPR/) and only falls back to a generic Safari match once every Chromium-based browser has been ruled out.
Identified from an ordered list of tokens, checking newer or more specific browsers before generic ones.
Blink, Gecko, WebKit or Trident, inferred from the same tokens used for browser detection.
Windows, macOS, Linux, Android, iOS and iPadOS are each detected from their own distinct substring.
A best-effort guess from Mobi, iPad and Android tokens, since there is no dedicated device field.
Common questions about accuracy and how detection works.
Many non-Safari browsers include a Safari/ version token for compatibility with sites that only check for it, and Chrome-based browsers keep an AppleWebKit and Safari token from their WebKit origins. Reliable detection has to check for Chrome-specific and other engine-specific tokens before falling back to Safari, which this tool does in order.
Yes, completely. Any browser or script can send whatever User-Agent string it wants, and DevTools lets you override it with one click. Treat parsed results as a hint about what a visitor is reporting, never as proof of what software they are actually running.
Device type is inferred from heuristics such as the presence of Mobi, iPad or Android in the string, since there is no dedicated field. Some tablets identify as desktops and some desktop browsers in responsive mode add mobile-like tokens, so this is always a best guess.
The rendering engine is the underlying software that parses HTML and CSS and paints the page. Blink powers Chrome, Edge, Opera and most Android browsers; Gecko powers Firefox; WebKit powers Safari; older Internet Explorer used Trident.
No. Parsing happens entirely with regular expressions in your browser. Nothing you paste or your own browser's live string is transmitted anywhere.