All tools

User-Agent Parser

Network

Parse a browser User-Agent string into browser, engine, OS, and device type

Paste a User-Agent header value and get back the browser name and version, the rendering engine, the operating system, and a device type (desktop, mobile, tablet, or bot). It works by pattern matching against the well-known token formats every major browser and crawler puts in its UA string, the same technique used to check what a support ticket's UA actually means or to sanity-check a bot's identity in server logs. It is not an exhaustive UA database like a commercial UA-parsing service: obscure browsers, heavily customized embedded webviews, or unusual bot strings may come back with some fields marked Unknown rather than a guessed value.

user-agentbrowser-detectionhttpparser

How to use User-Agent Parser

  • 1.Paste a full User-Agent header value into the input, or pick one of the sample strings to see the format.
  • 2.Read off the parsed browser, engine, OS, and device type in the results grid.
  • 3.Check the device type badge (desktop, mobile, tablet, or bot) to quickly see how a request identified itself.

Frequently asked questions

Does this cover every browser and bot?
It covers the major desktop and mobile browsers (Chrome, Firefox, Safari, Edge, Opera, Samsung Internet) and common search-engine and social crawlers (Googlebot, Bingbot, Twitterbot, and others), but it is not an exhaustive UA database. Obscure or heavily customized UA strings may return "Unknown" for some fields.
How does it tell Chrome and Edge apart, since Edge's UA also contains a Chrome token?
It checks for browser-specific tokens in a fixed priority order: Edge's Edg/ token and Opera's OPR/ token are checked before the generic Chrome/ token, since both Chromium-based browsers include a Chrome/ token for compatibility with sites that sniff for it.
What counts as a bot?
A UA string is flagged as a bot if it matches a known crawler signature (Googlebot, Bingbot, Baiduspider, and similar) or generic patterns like "crawler" or "spider". This is pattern matching on the string itself, not a live behavioral check, so a UA can claim to be a bot (or spoof being a real browser) and this tool has no way to verify the claim.
Is my data sent anywhere?
No, the browser tool parses the string entirely client-side. The REST API and SDKs process whatever UA string you send them, same as any other API call.

Use via API, SDK, or MCP

cURL# Free: 1,000 req/day · Pro: 10,000 req/day
curl -X POST https://api.utilix.tech/v1/tools/user-agent-parser \
  -H "Authorization: Bearer utx_live_..." \
  -H "Content-Type: application/json" \
  -d '{"ua":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"}'

Get an API key from your dashboard · Full API docs →

Related tools

CORS Header BuilderGenerate CORS headers with nginx, Express, and Apache config snippetsNetworkcURL BuilderBuild cURL commands from URL, method, headers, and bodyNetworkGitHub URL ParserParse a GitHub URL (repo, pull request, issue, commit, or file with line range) into structured componentsCode