User Agent Parser
Parse any User-Agent string into browser, OS, device, and bot details
User-Agent parsing is heuristic and should not be used as the sole source of capability detection. Prefer feature detection for production behavior.
Parsed result
What does the User Agent Parser do?
It breaks a User-Agent string into browser and version, rendering engine, operating system and version, device type, vendor and model, CPU architecture, and bot or crawler classification. Every field shows a confidence level, and fields the string cannot reveal are shown as Unknown instead of guessed.
How to use it
- 1.Paste a User-Agent string, or a whole request header block that contains a "User-Agent:" line.
- 2.Or click Use my browser to load the User-Agent of the browser you are using right now.
- 3.Read the field cards, the notes, and the raw token table.
- 4.Copy or download the result as JSON for logs, tickets, or tests.
What it recognizes
Chrome, Edge (Chromium and legacy), Firefox, Safari, Opera, Samsung Internet, UC Browser, Yandex, Vivaldi, Internet Explorer, headless Chrome, and in-app browsers such as Facebook, Instagram, WeChat, Android WebView, and iOS WKWebView. Engines: Blink, WebKit, Gecko, Trident, EdgeHTML, and Presto. Crawlers and clients: Googlebot, Bingbot, DuckDuckBot, Baiduspider, YandexBot, Applebot, link-preview bots, AI crawlers, curl, Wget, python-requests, Go-http-client, and generic bot, crawler, or spider tokens.
Limits of User-Agent parsing
User-Agent strings are self-reported and frequently reduced or spoofed. Brave looks exactly like Chrome, Windows 10 and 11 share "Windows NT 10.0", macOS is frozen at 10.15.7, Apple silicon Macs report Intel, and iPads in desktop mode look like Macs. Use User-Agent Client Hints and feature detection for production decisions. Parsing runs entirely in your browser.
