User Agent Parser

Parse any browser User-Agent string into browser, OS, device, and engine details. Includes your own UA. 100% client-side. Free and privacy-first.

How to use

  1. Use Your Own UA — Your browser's User-Agent is loaded automatically on first visit.
  2. Or Paste One — Paste any User-Agent string from logs, headers, or another device.
  3. Read the Breakdown — Browser, engine, OS, device type, and bot detection update instantly.
  4. Use in Analytics — Compare with server-side parsing to validate your logs.

Frequently asked questions

Is User-Agent parsing reliable?

It's approximate. Browsers freeze and spoof the UA for privacy, so treat results as best-effort.

Why does Chrome show 'Safari' too?

Chrome's UA includes 'Safari' for historical compatibility — many sites originally only checked for WebKit.

Can I detect bots accurately?

We match common keywords like 'bot' and 'crawl'. Sophisticated bots can disguise themselves; UA-based detection isn't security.

Are Client Hints supported?

Not yet. Modern detection should also read Sec-CH-UA headers and User-Agent Client Hints API on the server side.

Is this 100% accurate?

Heuristic — covers 99%+ of real-world strings. Newer browsers may need parser updates.

Why is everything claiming to be Mozilla?

Compatibility scar tissue from the 1990s. Every browser preserves the 'Mozilla/5.0' prefix.

Will the User-Agent string disappear?

Eventually yes — Chrome is phasing out detail in favour of Client Hints.

Should I feature-detect or UA-detect?

Always feature-detect. UA is unreliable for real capability checks.

Is the UA sent to a server?

No — parsing runs locally.

Free User Agent Parser

Decode any browser User-Agent string into a readable breakdown. Useful for log analysis, bug reports, analytics validation, and learning how browsers identify themselves.

Common Uses

  • Debug analytics that look off
  • Understand error reports from users
  • Test mobile vs desktop rendering rules
  • Identify bot traffic in logs
  • Teach how HTTP headers work

How It Works

We run pattern matches against well-known browser, OS, and rendering engine signatures, then bucket the device as Desktop, Tablet, or Mobile. The parsing is heuristic — same as most server libraries.

Privacy

Your UA strings are parsed locally. Nothing is uploaded or stored.

Related: MIME Type Lookup, HTTP Status Lookup, URL Parser.

Related free tools

  • XML Formatter & Minifier — Beautify or minify any XML — SOAP, RSS, SVG, sitemap. Browser-based parser.
  • XML to JSON Converter — Parse any well-formed XML into a clean JSON tree with attributes and arrays.
  • JSON to XML Converter — Convert JSON to well-formed XML — supports attributes, custom root, declaration.
  • CSV Viewer — Open CSV or TSV files in your browser — sort, search, paginate, export filtered view.
  • JSON to CSV Converter — Convert JSON data to CSV format. Export to spreadsheets easily.
  • CSV to JSON Converter — Convert CSV data to JSON format. Useful for API development.
  • JSON Formatter — Format, beautify, or minify JSON with customizable indentation.
  • JSON Validator — Validate JSON syntax and find errors with line and column numbers.
  • HTML Minifier — Compress HTML by removing comments, whitespace, and line breaks.
  • CSS Minifier — Minify CSS by stripping comments, whitespace, and unnecessary characters.
  • JavaScript Minifier — Compress JavaScript by removing comments, whitespace, and empty lines.
  • Base64 Encoder/Decoder — Encode text to Base64 or decode Base64 back to text. UTF-8 support.

Browse all free tools · Guides and tutorials · PDF tools · Developer tools · Text tools · SEO tools