Loading…
Decode user-agent strings into browser, OS, engine, and device.
Paste any User-Agent string above, or click Load my UA to parse your current browser.
🔒 Parsing is 100% local — the string never leaves your browser. UA sniffing is heuristic by nature: clients can lie about any field, and Windows 10 vs 11 is intentionally indistinguishable (both report Windows NT 10.0).
Every HTTP request your browser sends carries a User-Agent header — a dense string identifying the browser, rendering engine, operating system, and device type. This parser decodes that string into readable fields plus a structured JSON result. It auto-detects your own browser on load, accepts any pasted string for testing, flags known search-engine bots, and runs entirely in your browser — nothing is sent anywhere.
UA parsing is really pattern matching with precedence traps. Microsoft Edge, Opera, and Samsung Internet all contain Chrome/… in their strings, so they must be checked before Chrome — and Chrome before Safari, since every Chromium browser also ends with Safari/537.36. The same applies to operating systems: Android UAs contain the word Linux, and iOS UAs contain like Mac OS X, so mobile platforms must win over desktop ones. This tool encodes exactly that ordering.
The engine field (Blink, Gecko, WebKit) often matters more than the browser brand for CSS and JavaScript compatibility. Device type is inferred from tokens like Mobile and iPad — an Android UA without Mobile is treated as a tablet, matching how the browsers self-report. Two honest limitations: Windows 10 and 11 both report Windows NT 10.0 and are indistinguishable from the UA alone, and iPadOS pretends to be desktop macOS by design.
Paste the UA from a server log to identify what a visitor or bot actually was — the bot detector covers Googlebot, Bingbot, DuckDuckBot, GPTBot, and a dozen more. It is also handy when building test fixtures or debugging "works on my machine" issues. For production feature support, though, prefer feature detection ('clipboard' in navigator) over UA sniffing: strings are trivially spoofed, browsers freeze or shuffle tokens regularly, and Client Hints are gradually replacing the UA header in Chromium.
The User Agent Parser handles user agent parserdirectly in your browser. Paste or type your input, and the tool processes it instantly — no upload, no signup, no waiting. It's built for the moments when you need a quick transformation and don't want to leave your workflow.
Because the tool runs client-side, it's fast and private. Your text never touches a server, which makes it safe for sensitive content. The interface is keyboard-friendly and works on any device with a modern browser.
Common uses: people reach for this tool when they need to use a what is my user agent string, user agent parser online, detect browser from user agent, or user agent lookup tool.
Browser-based tools like this one have a few real advantages over installed software or manual methods:
More tools you might find useful