D

User Agent Parser

Parse user agent strings to detect browser, engine, OS, device type, and CPU architecture.

Runs 100% in your browser — nothing is uploaded

About this tool

The User Agent Parser analyses HTTP User-Agent strings and extracts structured information: browser name and version, rendering engine, operating system, device type (desktop, mobile, tablet), device vendor and model, and CPU architecture. Uses the ua-parser-js library in the browser — no server call.

User agent strings are sent by browsers and HTTP clients with every request. Parsing them helps you understand your web traffic breakdown, debug browser-specific issues, validate device detection logic, and analyse logs. The "Use my UA" button loads your own browser's user agent string for instant inspection.

Because ua-parser-js runs in the browser, you can paste user agent strings from server logs without uploading them anywhere. The parsed result is shown as a structured table with copy buttons for each field.

Frequently asked questions

Can I parse a UA string from my server logs?
Yes — paste any UA string into the input and the tool will parse it. There is no need to upload your logs anywhere; parsing happens locally.
Why does "Device type" show "desktop" for many browsers?
Desktop browsers do not typically include device type in their UA string. ua-parser-js infers "desktop" when no mobile or tablet markers are present. Mobile browsers include keywords like "Mobile" or "Android" that make detection reliable.
Is the UA string accurate for bot detection?
User agent strings are easily spoofed — a bot can send any UA string it likes. For serious bot detection, combine UA analysis with behavioral signals, IP reputation, and fingerprinting.
What is the "CPU architecture" field?
Some user agents include architecture information: amd64, arm, arm64. Most desktop browser UAs on modern systems omit this, in which case the field shows "?" (unknown).