User-Agent Parser

Runs in browser Web

Identify browser family, version, rendering engine, operating system, device class and known crawlers from a User-Agent string, and detect your own browser instantly.

Privacy: This tool runs entirely in your browser. Your input never leaves your device.

How to use User-Agent Parser

  1. Paste a User-Agent string from logs, analytics or a bug report — or leave the field empty to analyse your own browser.
  2. Click Parse (or "Use my browser's User-Agent").
  3. Read the browser, engine, OS and device rows; check the bot row before trusting traffic.
  4. Review the notes for caveats such as reduced UA strings before drawing conclusions.

User-Agent Parser features

  • Browser family and version for Chrome, Edge, Firefox, Safari, Opera, Samsung Internet, Brave, Vivaldi, UC, in-app browsers and more
  • Rendering engine (Blink, WebKit, Gecko, Trident, EdgeHTML) with the Blink/WebKit split at Chrome 28
  • Operating system and version with friendly Windows names, iOS/iPadOS underscores normalised, macOS, Android, Chrome OS, Linux distributions, consoles and TVs
  • Device type (desktop, mobile, tablet, TV, console, wearable, bot) plus Android vendor and model when present
  • Detection of 70+ crawlers, social previewers, AI bots, SEO spiders, monitoring services and headless browsers
  • Programmatic clients (curl, python-requests, okhttp, Go, Postman, axios…) recognised as tools rather than browsers
  • Notes about reduced/frozen User-Agent strings and other ambiguities

User-Agent Parser example

Parse a Samsung Galaxy S24 Ultra string

Input:

Mozilla/5.0 (Linux; Android 14; SM-S928B) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Mobile Safari/537.36

Output:

Browser: Google Chrome 126.0.0.0 (major 126)
Rendering engine: Blink 126.0.0.0
Operating system: Android 14
Device type: mobile — Samsung SM-S928B
Is bot: No
Note: Reduced User-Agent (Chrome 101+): only the major version is real.

Frequently asked questions about User-Agent Parser

How do I see my own User-Agent?

Leave the input empty and click Parse, or click "Use my browser's User-Agent". The string is read from navigator.userAgent in your browser and analysed locally.

Why does Chrome report version 126.0.0.0 and Windows 10 on Windows 11?

Since Chrome 101 the User-Agent is "reduced": only the major version is real and the platform is frozen (Windows NT 10.0, macOS 10.15.7, "Android 10; K"). The tool flags these cases; the exact values are only available through Client Hints.

Which bots are detected?

Search engines (Googlebot, Bingbot, Baiduspider, Yandex, DuckDuckBot, Applebot), social previewers (Facebook, Twitter, LinkedIn, Slack, Discord, WhatsApp), AI crawlers (GPTBot, ClaudeBot, PerplexityBot, CCBot, Bytespider), SEO crawlers (Ahrefs, Semrush, MJ12), monitoring services and headless browsers, plus a generic bot/crawler/spider fallback.

Why is iPad reported as macOS?

Since iPadOS 13, Safari on iPad sends the desktop macOS User-Agent by default. Only touch detection in JavaScript can tell the difference, so the tool notes this ambiguity.

Can I trust the result for security decisions?

No. User-Agent strings are freely spoofable. Use them for analytics and progressive enhancement; verify crawlers with reverse DNS and never use the UA for authorisation.

Technical notes

Parsing is regex based and ordered from most to least specific: tools first (they start the string), then bots, then browsers whose tokens shadow others (Edge before Chrome, Chrome before Safari, CriOS/FxiOS before Safari on iOS). Safari's Safari/6xx token is a WebKit build number, so the version is taken from Version/x.y instead.

The engine, OS and device rule tables are unit-tested against 30+ real-world strings, including reduced UA strings and bots that impersonate browsers.