Free online user agent parser tool
Use this free user agent parser online tool — no sign-up, no API key. Run a user agent parser check in seconds, or use the Single tab as a free user agent parser test bench for any user agent string. Unlike most user agent parser websites, this one has no backend — and unlike a user agent parser web service that uploads your pastes, everything here runs in your browser. As a browser user agent parser and HTTP user agent parser, it decodes the HTTP user agent line every browser sends (the User-Agent request header) into browser, OS, device, and engine facts — if you searched for a "user agent parser header" tool, this is it: paste the header value, get structured data. Looking for the best user agent parser for log work? The bulk user agent parser is a multiple user agent parser that handles thousands of lines and exports the user agent parser data as CSV or JSON. Wondering what your own browser sends? The my user agent parser tab detects it in one click. Try this user agent parser demo with the sample buttons above. People also search for user agent parser chrome, user agent parser firefox, user agent parser ios, user agent parser mac, user agent parser macos, user agent parser windows, and user agent parser xbox — the user agent parser examples below cover all of them, plus consoles and smart TVs. Unlike the whatismybrowser user agent parser page, which focuses on detecting your own UA, this user agent analyzer online also parses pasted strings in bulk and doubles as a user agent parser and validator with a 100+ signature bot list (small "user agents net parser" clones offer single-string parsing only). User agent parser how to use: the three tabs above cover single checks, bulk log analysis, and one-click detection of your own UA. In short, the user agent parser definition is simple: software that turns the cryptic HTTP user agent line into facts you can act on.
What is a user agent string? (definition)
A user agent string is a line of text sent in the HTTP User-Agent header with every web request. It tells the server which browser, operating system and device is asking — servers use this user agent data for analytics, debugging, and compatibility decisions. A typical Chrome UA looks like this:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36
A user agent string parser (or user agent string analyzer) decodes that cryptic line into structured facts. This online tool does exactly that — plus explains why each segment exists, which no other web parser does.
How to use this user agent parser
- Single check: paste any UA string into the Single tab and hit Parse — you get browser, OS, device, engine, bot detection, a segment-by-segment explanation, and JSON.
- Bulk / multiple: switch to the Bulk parser tab, paste hundreds or thousands of lines from a log, and get share charts + CSV export.
- Your own UA: the My user agent tab reads
navigator.userAgent straight from your browser.
User agent parser examples
Chrome on WindowsMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36→ Chrome 120 · Windows 10/11 · Desktop · Blink
Safari on iPhone (iOS)Mozilla/5.0 (iPhone; CPU iPhone OS 17_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.2 Mobile/15E148 Safari/604.1→ Safari 17.2 · iOS 17.2 · iPhone · WebKit
Firefox on macOSMozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36→ (that's Chrome — Firefox looks like below)
Firefox on macOS (real)Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:121.0) Gecko/20100101 Firefox/121.0→ Firefox 121 · macOS 10.15 · Desktop · Gecko
Chrome on AndroidMozilla/5.0 (Linux; Android 14; SM-G991B) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Mobile Safari/537.36→ Chrome 120 · Android 14 · Samsung Galaxy S21 · Mobile
Googlebot (crawler)Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)→ Bot: Googlebot 2.1
Nintendo SwitchMozilla/5.0 (Nintendo Switch; ShareApplet) AppleWebKit/601.6 (KHTML, like Gecko) NF/4.0.0.5.9 NintendoBrowser/5.1.0.13341→ Nintendo Browser 5.1 · Switch · Console
Xbox (Edge)Mozilla/5.0 (Windows NT 10.0; Win64; x64; Xbox; Xbox Series X) … Edg/120.0.0.0→ Edge 120 · Windows 10/11 · Xbox Console
How this parser works (regex-based, honest about limits)
This is a user agent regex parser: an ordered database of 200+ patterns (bots first, then browsers, OS, engines) plus device heuristics, verified against 259 real-world user agent strings — desktop and mobile browsers, consoles, smart TVs, and 60+ crawlers — with 100% matching their expected classification. Two honest limitations, disclosed rather than hidden:
- Brave is indistinguishable from Chrome (it sends no Brave token by design) — the result says so instead of guessing.
- Windows 10 vs 11 both report
NT 10.0 — reported as "Windows 10 / 11".
Pattern database last updated: October 2026. New browsers and bots appear over time; unrecognized UAs parse as "Unknown" rather than a wrong guess.
Best user agent parser? Comparison
There is no single dominant web-based user agent parser — the space is fragmented, which is why this tool was built to win on depth. Factual comparison as of October 2026:
| Tool | Single parse | Bulk / log analysis | Bot detection | Segment explanations | Export | Client-side |
|---|
| This tool (nrtechstudio) | ✅ | ✅ charts + stats | ✅ 100+ signatures | ✅ | ✅ CSV + JSON | ✅ 100% |
| useragentstring.info | ✅ | ❌ | partial | ❌ | ❌ | ❌ |
| whatismybrowser.com | ✅ (great "my UA" page + API) | ❌ (API only) | partial | ❌ | API | ❌ |
| rapidtoolset.com | ✅ | ❌ | basic | ❌ | ❌ | — |
| Developer libraries (uap-core, Matomo device-detector) | — (code, not a website) | ✅ (self-hosted) | ✅ | ❌ | — | — |
If you need parsing inside your own code, use uap-core or Matomo device-detector. If you want to paste a UA — or a thousand — into a web page and understand the result, this tool is the deepest free option.
Bot & crawler list detected
The parser recognizes 100+ automated clients, including: Googlebot, Googlebot-Image/Video/News, Mediapartners-Google, AdsBot-Google, Google-InspectionTool, Bingbot, msnbot, Slurp, DuckDuckBot, Baiduspider, YandexBot (+Images/Video/Media/Market), Sogou, Exabot, Applebot, facebookexternalhit, Facebot, Twitterbot, LinkedInBot, Pinterestbot, Slackbot, Discordbot, TelegramBot, WhatsApp, plus AI crawlers (GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended, CCBot), SEO crawlers (AhrefsBot, SemrushBot, MJ12bot, DotBot), and dev tools (curl, Wget, python-requests, Postman). Unknown crawlers are still caught by generic bot/crawler/spider signatures.
The full user agent parser list of supported bot signatures is embedded in the page source — unobfuscated, so anyone can audit exactly what is detected.
Frequently asked questions
What is a user agent string?A user agent (UA) string is a line of text your browser sends in the HTTP User-Agent header with every request. It identifies the browser, operating system, and device — for example: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36. Websites use it for analytics, debugging, and serving compatible content.
What is my user agent? How do I find it?Click the "My User Agent" tab above — the tool reads navigator.userAgent directly from your browser and parses it instantly. In Chrome you can also press F12, open the Console tab, and type navigator.userAgent. In Firefox: F12 → Console → navigator.userAgent.
Why does my user agent say Mozilla/5.0 when I use Chrome?Historical compatibility. In the 1990s, sites served richer pages to Mozilla browsers, so every browser started pretending to be Mozilla/5.0 to avoid being treated as inferior. The token stuck for 25+ years and today it means nothing about your actual browser — the real identity is in tokens like Chrome/120.0.0.0 or Edg/120.0.0.0.
Can a user agent parser detect Brave browser?Honestly: no. Brave intentionally sends a standard Chrome user-agent string with no Brave token, so it is indistinguishable from Chrome by UA parsing alone. This tool tells you that instead of guessing — the result notes it could be Brave or another Chromium fork.
Why can't the parser tell Windows 10 from Windows 11?Because Microsoft made them identical on purpose: both Windows 10 and Windows 11 report "Windows NT 10.0" in the user agent (frozen since 2015). No parser can distinguish them from the UA string alone — a tool that claims otherwise is guessing. This parser reports "Windows 10 / 11" honestly.
How does bulk user agent parsing work?Paste up to thousands of UA strings (one per line, e.g. copied from a server log) into the Bulk tab. The tool parses each line locally and aggregates the results into browser share, OS share, and device-type charts, plus a bot-traffic percentage. You can download everything as CSV or JSON for further analysis.
Can it detect bots and crawlers?Yes — the parser checks 100+ bot signatures first (Googlebot, Bingbot, GPTBot, AhrefsBot, SemrushBot, facebookexternalhit, and many more) before browser matching, because crawlers often embed browser tokens. Unknown crawlers are still flagged by generic bot/crawler/spider keywords.
Is it safe to paste user agent strings here? Is my data private?Yes. This tool runs 100% client-side: all parsing happens in your browser with JavaScript, and nothing you paste is ever sent to any server. You can verify this by disconnecting from the internet — the tool keeps working.
How accurate is regex-based user agent parsing?This parser was verified against 259 real-world user-agent strings covering desktop and mobile browsers, consoles, smart TVs, and 60+ bots — 100% matched their expected browser, OS, device, and bot classification. Known honest limitations: Brave is indistinguishable from Chrome, and Windows 10 vs 11 cannot be separated (both report NT 10.0).
What does "Mobile Safari" mean inside a Chrome user agent?Another compatibility token. Chrome on Android includes "Mobile Safari/537.36" purely so old mobile sites that sniffed for Safari keep working. The real browser is identified by the Chrome/ token; Safari/ and Mobile Safari/ are historical baggage.
Is the user agent string being deprecated? What are Client Hints?Chrome has frozen the UA string (it no longer reveals detailed OS/browser versions for privacy) and promotes User-Agent Client Hints (Sec-CH-UA headers) instead. However, the classic UA string is still sent by every browser and remains the standard for log analysis — which is exactly what this tool parses.
How often is the pattern database updated?User agent strings evolve as new browsers and bots appear. The pattern database in this tool was last updated in October 2026. If a brand-new browser or crawler appears, its UA may parse as "Unknown" until the database is refreshed.
Can I use this for server log analysis?Yes — that is what the Bulk tab is for. Extract the User-Agent column from your access log (one UA per line), paste it in, and you get browser/OS/device breakdowns plus bot traffic share, exportable to CSV for spreadsheets or JSON for pipelines.
Is this also a user agent parser validator?Yes. A parser extracts structured facts (browser, OS, device) from a UA string; a validator checks whether a string is a well-formed, recognizable UA. This tool does both: every parse also validates, and malformed or empty input gets a clear error instead of a made-up result.
Does it work for smart TVs and game consoles?Yes. The device detector recognizes Smart TVs (Samsung Tizen, LG webOS, Android TV / Fire TV, HbbTV) and consoles (PlayStation 4/5/Vita, Xbox, Nintendo Switch) — categories most simple parsers lump together as "desktop". Try the samples or paste a console UA to see.
Is this user agent parser free?Yes — a user agent parser online free of charge: unlimited parses, no account, no API key, no rate limits. The bulk tab handles thousands of lines without paying for an API plan.