EasyConvert / API & Network

User-Agent String Parser

Parse User-Agent headers to detect browser, OS, engine, CPU, and device specs. Free browser-based tool with no signup required.

About User-Agent String Parser

Parse User-Agent headers to detect browser, OS, engine, CPU, and device specs.

This network tool sends requests to the destination selected by the user. Do not submit secrets you do not intend to send.

How to use this tool

Enter or select the user agent string value you want to work with.
Review the available settings, then run the parse action.
Review the browser name, os version, device type output and use the copy or download action when the tool provides one.

What you can do with User-Agent String Parser

Parse user agent header
Detect browser and os

What this conversion does

Decode a User-Agent string into browser, operating system, and device type.

Example input

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 … Chrome/120.0 Safari/537.36

Example output

Browser: Chrome 120 · OS: Windows 10/11 · Device: Desktop

Practical workflow

Paste a User-Agent string from server logs, analytics, or a bug report.
Read the detected browser, engine, operating system, and device class.
Use your own browser's User-Agent (prefilled) to compare against the reported one.

Common use cases

Identify which browser and OS a bug reporter is actually using.
Classify traffic in server logs by browser family and device type.
Verify what User-Agent your own browser or HTTP client sends.

Important notes and limitations

Modern browsers freeze or reduce parts of the User-Agent, so minor version details can be approximate.
Parsing is heuristic and local; strings are never uploaded.

Continue your workflow

Live HTTP Headers & Redirect Chain Inspector — see the full request headers, not just the User-Agent.
HTTP Request Tester — send requests with a custom User-Agent.

Frequently asked questions

How do I find out what browser a User-Agent string belongs to?

Paste the string and the parser identifies the browser family and version, the operating system, and whether the client is desktop or mobile — the classic Mozilla/AppleWebKit prefixes are legacy compatibility tokens and are ignored.

Why do all User-Agents start with Mozilla/5.0?

Historical compatibility: early servers only served full pages to Netscape (Mozilla), so every later browser adopted the prefix. Real identification lives in later tokens like Chrome/, Firefox/, or Safari/.

Is parsing done locally?

Yes. Strings from your logs never leave the browser.