About this tool
Parse User-Agent strings to detect browser and OS. Turn opaque strings from network traces, devtools, or SEO audits into structured output you can act on.
Paste a User-Agent string from DevTools, logs, or an Access-Control dump. Read the detected browser family and operating system hints. Example — Desktop Chrome UA: try `Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36` and expect something like `browser: Chrome 120 os: macOS 10.15.7`.
Heuristic parsing — spoofed or highly reduced UAs can misidentify the client. See also: HTTP Header Parser. Runs in your browser — nothing you paste gets uploaded.
How to use
- Paste a User-Agent string from DevTools, logs, or an Access-Control dump.
- Read the detected browser family and operating system hints.
- Use the result when reproducing client-specific bugs or analytics buckets.
- Keep in mind modern browsers often reduce UA detail for privacy.
Example
Desktop Chrome UA
Input
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36
Output
browser: Chrome 120 os: macOS 10.15.7
Limitations
- Heuristic parsing — spoofed or highly reduced UAs can misidentify the client.
- Does not expose Client Hints (Sec-CH-UA) which many modern sites prefer.
- Bots and embedded WebViews may look like desktop browsers.
Related guides
1Related tools
1Frequently asked questions
What does the User-Agent Parser do?
Parse User-Agent strings to detect browser and OS. Runs in your browser — no install, no account.
How do I use the User-Agent Parser?
Paste a User-Agent string from DevTools, logs, or an Access-Control dump. Read the detected browser family and operating system hints. Use the result when reproducing client-specific bugs or analytics buckets. Keep in mind modern browsers often reduce UA detail for privacy.
Is the User-Agent Parser free?
Yes. No signup, no usage limits, no paywall.
Does the User-Agent Parser upload my data?
No. Processing happens locally in JavaScript. Your input is not uploaded, stored, or logged.
What are the limitations of the User-Agent Parser?
Heuristic parsing — spoofed or highly reduced UAs can misidentify the client. Does not expose Client Hints (Sec-CH-UA) which many modern sites prefer. Bots and embedded WebViews may look like desktop browsers.