Developer Tool
Paste any HTTP User-Agent header. Get browser, version, OS, engine, device class, bot detection and stale-version warnings — parsed instantly, entirely in your browser.
It runs a set of regular expressions against the raw string, matching known browser tokens (Chrome/, Edg/, Firefox/), OS markers (Windows NT, Mac OS X, Android, iPhone OS), engine signatures (AppleWebKit, Gecko, Blink), and device hints (Mobile, iPad, Tablet). The first match wins per category, so order matters — Edge is checked before Chrome, Chrome before Safari, because their UA strings overlap.
What is a user agent? — why every UA starts with "Mozilla/5.0" and what Client Hints replace.
Common user agent strings — reference list for every mainstream browser and platform.
What is my user agent? — see your own UA with one click.
Am I unique? — how much your UA plus other signals identifies you.
It's a tool that takes a raw HTTP User-Agent header and breaks it into human-readable pieces: browser name and version, operating system, rendering engine, and device class. It's what developers, QA engineers and analysts use when a log line says 'Mozilla/5.0 (…) AppleWebKit/…' and they need to know who that actually is.
For mainstream browsers on real devices, it's ~99% accurate on the fields shown here. It becomes unreliable when a user has manually spoofed their UA, when a browser sends the reduced UA (Chromium 101+) without Client Hints, or for niche/embedded browsers. Always treat UA as a hint, not a source of truth for security decisions.
Chromium's reduced User-Agent, rolled out from version 101, freezes the minor and patch numbers to '0.0.0' to reduce passive fingerprinting. The real version is exposed via Sec-CH-UA-Full-Version-List headers only if the site explicitly requests them via Client Hints.
Open the browser console (F12) and run navigator.userAgent, or visit our What Is My User Agent page for a formatted view with copy button.
Not yet — this decoder targets the legacy User-Agent header, which is still what 99% of server logs and analytics tools contain. Client Hints require a different parser because they arrive as multiple structured headers rather than one string.
Yes. Parsing happens entirely in your browser with regular expressions — nothing is sent to a server, logged, or stored. Reload the page and the input is gone.
Look for a bot name (Googlebot, Bingbot, GPTBot, ClaudeBot, etc.), a URL in the UA (`+http://…`), the token 'compatible' followed by a name, or the absence of a real browser signature. This decoder highlights the bot token in red when it detects one.
The Chrome/… token appears in every Chromium-based browser: Chrome, Edge, Opera, Brave, Samsung Internet, Vivaldi. The distinguishing token comes after — Edg/, OPR/, SamsungBrowser/, etc. If you only see Chrome/ with no follow-up brand token, it's actual Google Chrome or a Chromium fork that didn't rebrand its UA.