User-Agent Parser

Parse a User-Agent to identify browser, engine, OS, and device

User-Agent

Usage

Identify browser, engine, OS and versions, device type, vendor and model

Read your current browser UA in one click, or paste any UA string

Related tools

What the User-Agent parser is for

The User-Agent parser takes a UA string and identifies the browser name and version, layout engine, operating system and version, device type (desktop, mobile, tablet, or bot), device vendor, and device model. It uses a well-maintained parser library to handle the full range of current and historical UA string formats.

Common uses include identifying the browser and device of a visitor from a server access log entry, testing whether a specific UA string is correctly classified by analytics or targeting logic, debugging UA-dependent behavior in web applications, and understanding the device and OS mix in a traffic sample.

Frequently asked questions

Where do I find a User-Agent string to parse?

Click 'Use current browser UA' to parse your own browser's UA string. You can also copy a UA string from server logs (e.g. the HTTP_USER_AGENT field in Nginx/Apache access logs), from developer tools, or from test device emulation.

Why does a mobile device show up as 'Desktop'?

Some browsers on mobile devices send a desktop UA string when 'Request Desktop Site' mode is active. The parser reports what the UA string says, not the physical device.

What is a 'Bot / Crawler' device type?

The UA string matches a known web crawler, search engine bot, monitoring agent, or headless browser. Common examples include Googlebot, Bingbot, and curl.

Can UA strings be spoofed?

Yes. Any client can send any UA string. UA strings are useful for analytics and adaptive content, but should not be trusted for security decisions. Always combine UA analysis with other signals.