Free tools
User Agent Parser
Parse a User-Agent string into browser, OS, device, CPU, and engine details. Supports bulk parsing and exports JSON or TSV — runs locally in your browser.
User-agent input
Tip: Paste multiple user-agents (one per line) to parse in bulk.
Parsed output
User agent parser
Parse a User-Agent string into structured fields like browser name/version, operating system, device model/type, CPU architecture, and rendering engine. Works entirely in your browser.
How to use
- Paste a User-Agent string (or multiple, one per line).
- Choose an output format.
- Click Parse user-agents and copy the result.
Output formats
- Pretty JSON — best for humans (indented)
- Compact JSON — best for logs or small payloads
- Summary (TSV) — paste into spreadsheets (one UA per row)
Common uses
- Debug analytics/device reports
- Normalize logs into structured data
- Identify bots vs real browsers (best-effort)
Limitations & notes
- User-Agent strings are not a secure signal and can be spoofed.
- Some modern browsers reduce or freeze UA details; results may be less specific than expected.
- This tool parses the string only; it doesn’t “detect” the real device behind the request.
Privacy
Your input is processed locally in your browser. Nothing is uploaded to a server.
Frequently Asked Questions
What is a User-Agent string?
A User-Agent string is text that browsers and apps send to identify themselves to web servers. It typically includes the browser name and version, operating system, device type, and rendering engine. For example: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36'
How do I use the User Agent parser?
Paste a User-Agent string into the input field. The tool extracts and displays: browser (name, version), operating system, device type (desktop/mobile/tablet), CPU architecture, and rendering engine. You can also batch-process multiple User-Agents at once.
Can I export the parsed data?
Yes. The tool supports exporting parsed results in JSON or TSV format. This is useful for analyzing server logs, building device compatibility reports, or importing into spreadsheets and databases for further analysis.
Why do websites need to parse User-Agents?
Common use cases: analytics (understanding what devices/browsers visit your site), content adaptation (serving mobile-optimized layouts), feature detection (enabling features only supported by certain browsers), security (detecting bots or suspicious clients), and debugging (reproducing issues reported by specific browser versions).
Is User-Agent sniffing reliable?
User-Agent strings can be spoofed, modified by browsers, or frozen to reduce fingerprinting. Modern best practice is to use feature detection instead of User-Agent sniffing when possible. However, User-Agent parsing remains useful for analytics and server-side content negotiation.