User-Agent Parser
Paste any User-Agent string—or use your own—to break it down into the browser, rendering engine, operating system, and device type. Parsing happens entirely in your browser; nothing is sent to a server.
Secure & Private Client-Side
This tool runs entirely in your browser. No data is sent to any server, ensuring your information remains private and secure.
About User-Agent Parser
Paste any User-Agent string—or use your own—to break it down into the browser, rendering engine, operating system, and device type. Parsing happens entirely in your browser; nothing is sent to a server.
Frequently Asked Questions
What is a User-Agent string? expand_more
The User-Agent is an HTTP request header that identifies the client software making the request, including the browser, its version, the rendering engine, and the operating system.
Why are User-Agent strings so messy? expand_more
For historical compatibility reasons, most browsers still include legacy tokens like "Mozilla/5.0" and reference other engines. This "user-agent string history" means parsing relies on pattern matching rather than a single clean format.
Is User-Agent detection reliable? expand_more
It is a useful hint but can be spoofed or frozen. For feature support, prefer feature detection; modern browsers also reduce UA detail and offer the structured User-Agent Client Hints API.
Does this tool send my User-Agent anywhere? expand_more
No. The string is parsed locally in your browser using pattern matching. Nothing is uploaded or stored.
Common Use Cases
- Log Analysis: Decode raw User-Agent strings from server logs into readable browser and OS names.
- Bug Reproduction: Identify exactly which browser and version a user was on when a bug was reported.
- Checking Your Own: Quickly see how your current browser identifies itself with one click.
- Testing & QA: Confirm how a spoofed or device-emulated User-Agent is interpreted.