User-Agent Parser
Parse any User-Agent string into browser, OS, device, and engine
How it works
- 1Paste a User-Agent string
From server logs, an analytics export, or a support ticket.
- 2Click 'Use my browser'
Instantly fill your own UA to see what your browser reports.
- 3Read the breakdown
Browser, OS, device type, vendor, model, and rendering engine each broken out.
About User-Agent Parser
Free online User-Agent parser. Paste any UA string to see the browser name and version, operating system, device type (mobile / tablet / desktop / TV), vendor, model, and rendering engine. Auto-fills your own User-Agent. Runs entirely in your browser. User-Agent Parser on 712 Tools runs entirely inside your browser using modern JavaScript APIs — no server ever sees your data. That means instant results, complete privacy, and no upload limits.
Whether you need to parse any user-agent string into browser, os, device, and engine for a debugging session, a quick sanity check, or a production incident, this tool is free to use as many times as you need. There are no watermarks, no sign-up, and no ads inside the tool itself.
Frequently asked questions
How accurate is UA parsing?
UA strings are messy — Chrome pretends to be Safari, Edge pretends to be Chrome. This parser covers the common cases; fringe browsers and bots may not match precisely.
Are UAs still useful?
For basic browser/OS breakdown in analytics, yes. For feature detection, always prefer real feature checks (typeof x !== 'undefined') over UA sniffing.
What about Client Hints?
This tool parses the legacy User-Agent string. Modern Chromium browsers also send high-entropy Client Hints (Sec-CH-UA-*) which are more reliable but out of scope here.
Read more
ASCII art in READMEs, CLIs, and terminals: a practical guide
Every popular open-source project has an ASCII banner in its README or CLI startup. Here's how to make one that looks right, keeps its shape in Markdown, and doesn't break in narrow terminals.
User-Agent strings in 2026: parsing, Client Hints, and privacy
The User-Agent string is a mess — Chrome pretends to be Safari, Edge pretends to be Chrome. But it's still what your analytics reads. Here's how to parse it, when to trust it, and where Client Hints are taking us.
Related tools
JSON Formatter
Pretty-print, minify, and validate JSON instantly
Regex Tester
Test JavaScript regular expressions with live matches
SQL Formatter
Format SQL queries with proper indentation and keyword capitalization
JSON Diff
Structural diff of two JSON documents — added, removed, changed
Word Counter
Count words, characters, sentences, paragraphs, reading time
Case Converter
Convert text to UPPERCASE, lowercase, camelCase, snake_case, kebab-case, and more