User-Agent Parser

Parse any User-Agent string into browser, operating system, device type, and bot detection. Defaults to your own browser's string — edit it or paste a different one.

Your own User-Agent will parse automatically.

A User-Agent string is sent by every HTTP client — browsers, mobile apps, bots, and command-line tools — identifying itself on every request. Parsing it reliably means matching against dozens of overlapping, inconsistently formatted patterns: this tool runs the same parser behind /v1/ua.

What gets detected

Browser & version: Chrome, Firefox, Safari, Edge, Opera, Samsung Internet, and UC Browser, with version number where present.
OS & version: Windows, macOS, Linux, Chrome OS, Android, iOS, and iPadOS.
Device type: desktop, mobile, tablet, or bot.
Bot detection: Named detection for major search and social crawlers (Googlebot, Bingbot, AhrefsBot, and more) plus common HTTP libraries and headless browsers (curl, python-requests, HeadlessChrome, Selenium).

FAQ

Can User-Agent strings be spoofed?

Yes, trivially — any client can send any string. Treat parsed UA data as a hint for analytics and routing, not as a security control on its own.

Does this detect headless browsers?

It flags well-known headless signatures like HeadlessChrome and PhantomJS when they appear in the string, but a deliberately disguised headless browser can evade string-based detection entirely.

Can I parse a UA server-side without the page?

Yes — GET /v1/ua?ua=<string> returns the same JSON this page renders. See the API reference.

About this tool

A User-Agent string is the text a browser or application sends to identify itself. It is dense and inconsistent, so this tool breaks it into the browser and version, operating system, device type and whether the client looks like a bot or crawler.

How it works

Paste any User-Agent string, or leave the field alone to parse your own browser. Parsing runs on the server against a maintained set of patterns, and the same capability is available as a JSON endpoint in the API for use in your own code.

What to keep in mind

User-Agent strings are self-reported and trivially spoofed, and modern browsers deliberately reduce the detail they expose. Treat the result as a classification of what the client claims to be, and combine it with network signals before acting on it.

Common uses

Common uses are segmenting analytics by browser and device, filtering known crawlers out of reports, debugging a layout bug reported from a particular device, and flagging requests whose declared client does not match their network.