๐Ÿ•ต๏ธ User-Agent Parser

User-Agent string
BrowserChrome 128.0.0.0
OSWindows 10/11
Device typeDesktop
Rendering engineBlink

Enter a User-Agent string and this tool parses out the browser type and version, OS type and version, device type (desktop/mobile/tablet), and rendering engine. Use the "Use my browser" button to instantly parse the User-Agent of the browser you're using right now. Handy for analyzing access logs or testing browser-detection logic.

How to use

  1. Paste the User-Agent string you want to parse into the input field.
  2. Use the "Use my browser" button to auto-fill your current browser's info.
  3. The parsed browser, OS, device type, and engine are shown automatically.

How the calculation works

A user agent (UA) string is how a browser identifies itself to web servers. This tool looks for characteristic tokens in the string to work out the browser, operating system, device type and rendering engine. โ€ข Browser: checked in an order that avoids false matches โ€” Edg/ for Edge, OPR/ for Opera, Firefox/ for Firefox, Chrome/ for Chrome (Edge and Opera UAs also contain Chrome/). It also recognises Chrome (CriOS), Firefox (FxiOS) and Edge (EdgiOS) on iPhone, and Samsung Internet. โ€ข OS: Windows NT 10.0 โ†’ Windows 10/11, Mac OS X 10_15_7 โ†’ macOS, Android 14 โ†’ Android, and so on. โ€ข Device: iPad or Tablet โ†’ tablet; Mobi or iPhone โ†’ phone; otherwise desktop. โ€ข Engine: Blink for Chromium browsers, WebKit for Safari and every iOS browser, Gecko for Firefox.

Worked example

Input: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36 Browser: Chrome 128.0.0.0 OS: Windows 10/11 Device: desktop Engine: Blink The string also contains "AppleWebKit", "Safari" and "Gecko", but these remain only for compatibility with old sites; Chrome's actual engine is Blink.

Things to be aware of

  • Windows 11 also reports "Windows NT 10.0", so the UA alone cannot tell 10 and 11 apart. Likewise, recent macOS versions are frozen at "10_15_7".
  • Chrome and others are reducing UA detail and moving richer information to User-Agent Client Hints (Sec-CH-UA headers).
  • Users can change their UA freely, so never rely on it for access control or security decisions.

FAQ

How accurate is the parsing?

It's a lightweight parser based on common patterns for major browsers (Chrome, Firefox, Safari, Edge, Opera) and major OSes (Windows, macOS, Android, iOS, Linux). Unusual browsers or custom User-Agents may not be detected correctly.

Is the entered User-Agent sent to a server?

No, all parsing happens entirely in your browser โ€” nothing is sent anywhere.

What is a "rendering engine"?

It's the underlying software a browser uses to interpret HTML/CSS and draw the page (e.g. WebKit, Gecko, Trident).