Skip to content
Zoyku

User-Agent Parser

Parse any User-Agent string into browser, engine, OS and device — recognize bots, WebViews and mobile shells, all locally in your browser.

Browser

Unknown

Rendering engine

Unknown

Operating system

Unknown

Device type

Desktop

This tool runs entirely in your browser. Your data never leaves your device — it is not uploaded to any server.

How to use

  1. 1Paste the User-Agent string into the input box — or click the sample to analyze your own.
  2. 2Read the parsed fields: browser name and version, engine, OS, device type, and bot flag.
  3. 3Check edge cases like WebViews and unusual prefixes — they're labeled explicitly rather than guessed.

User-Agent Parser

Every HTTP request announces itself with a User-Agent string, and reading one correctly is a small art: Chrome pretends to be Safari which pretends to be Mozilla; Edge hides inside Chrome's token list; bots, WebViews and mobile shells each leave their own signature. Paste a UA here and the parse splits out the browser family and version, the rendering engine (Blink/Gecko/WebKit), the OS and version, and whether the device is desktop, mobile, tablet or a known crawler.

The rules are maintained as a table of explicit patterns — Chrome-family detection runs before the generic fallback, Edg/OPR/Samsung Internet get their own entries, and Googlebot, bingbot and friends are recognized by name rather than guessed as desktop browsers. Where a UA is truncated or malformed, the result says so instead of inventing a guess.

Everything parses in your browser; the UA string never leaves the device — useful when inspecting headers from a log file you're not ready to share. Your own UA is available as a one-click example.

Frequently asked questions

Why does Chrome claim to be Safari and Mozilla?

Historical compatibility. Netscape-compatible sites were served to browsers advertising 'Mozilla', and Chrome inherited that pretense to get the same content — which is why the modern Chrome UA reads 'Mozilla/5.0 … AppleWebKit/537.36 (KHTML, like Gecko) Chrome/…'. Parsers work from the end of the chain (the Chrome token), not the beginning.

How do you tell bots from real users?

Known crawlers publish their token explicitly — Googlebot, bingbot, DuckDuckBot, Applebot, facebookexternalhit and others appear verbatim in the UA. This parser names them by signature rather than guessing from mobile or desktop fields; anything unrecognized stays labeled as a normal browser, not flagged as a bot.

Is User-Agent sniffing reliable enough to gate features on?

Not for critical paths — UA strings lie by design and are easy to spoof. Use UA parsing for analytics, logging and non-security decisions (showing a mobile layout, counting bot traffic), and feature-detect in the page for anything functional. This tool is for reading UAs, not for trusting them.

Is the output safe to paste into production code?

Yes. Formatting, escaping and conversion follow the relevant specs (RFCs, W3C, JSON Schema), and nothing is sent anywhere — you can verify the output locally before committing it.

Does it work on large inputs?

Yes — everything runs locally. A multi-megabyte JSON file or a long regex session is limited only by your machine, not by a request size cap.

Is this tool free to use?

Yes, completely free — no signup, no subscription, no daily limits, and no watermarks on the output.

Embed this tool

Put this tool on your own site with one line — it runs entirely in the visitor's browser.

<iframe src="https://zoyku.com/en/tools/user-agent-parser?embed=1" width="100%" height="640" style="border:0;border-radius:16px" title="Zoyku — user-agent-parser" loading="lazy"></iframe>
100% local processing