Skip to main content
chain
UA
User Agent Parser
Browser
Engine
OS
Device
CPU
Paste a User-Agent string to break it into parts
// about this tool

User Agent Parser Online

Updated 2026-08-19

Parse a User-Agent string online for free. Paste any UA string and SnapTools identifies the browser, rendering engine, operating system, device, and CPU architecture — laid out for easy reading. Everything runs in your browser, so the string you paste is never uploaded.

Every HTTP request carries a User-Agent header, but the raw string is a dense, historical mess that is hard to read at a glance. This tool breaks it into the parts that matter, so you can quickly see what a client claims to be when you are debugging content negotiation, reading analytics logs, or testing device-detection logic.

// how to use

  1. 1 Paste a User-Agent string into the input panel — for example your own from any request header.
  2. 2 SnapTools parses it and lists the browser, engine, OS, device, and CPU.
  3. 3 Copy the parsed result, or paste a different UA string to compare.

// examples

Desktop Chrome
Input
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36
Output
Browser:  Chrome 120.0.0.0
Engine:   Blink 120.0.0.0
OS:       Windows 10
Device:   Desktop / unknown
CPU:      amd64
iPhone Safari
Input
Mozilla/5.0 (iPhone; CPU iPhone OS 17_0 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.0 Mobile/15E148 Safari/604.1
Output
Browser:  Mobile Safari 17.0
Engine:   WebKit 605.1.15
OS:       iOS 17.0
Device:   Apple iPhone mobile
CPU:      —

// common uses

Debugging why a browser or device is served the wrong content Reading User-Agent strings from server or analytics logs Checking how a device identifies itself Building or testing device-detection logic

// faq

Is the User-Agent string uploaded to a server?
No. Parsing runs entirely in your browser, so the string you paste never leaves your machine.
What does it detect?
It breaks a User-Agent down into the browser and version, the rendering engine, the operating system and version, the device (vendor, model, type), and the CPU architecture when present.
Where do I find my own User-Agent?
It is sent with every request as the User-Agent header. You can read it in your browser's developer tools under the Network tab, or from any request log on your server.
Why is the device shown as "Desktop / unknown"?
Desktop browsers usually do not advertise a device model, so there is nothing to report. Mobile and tablet User-Agents typically include a vendor and model, which are shown when available.
How reliable is User-Agent parsing?
It is a best-effort read of a self-reported string, which clients can spoof or freeze. It is great for analytics and debugging, but should not be your only signal for security decisions.

Use this via API

Get a free API key →
curl -X POST https://thesnaptools.com/api/v1/tools/user-agent-parser \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gec..."}'