Free Online User-Agent Parser
Paste any user-agent string to extract the browser, operating system, rendering engine, and device type — or inspect your own browser's user-agent with one click. It helps support teams and developers identify the browser, operating system, engine, and device represented by a user-agent string.
What is a user-agent string?
A user-agent string is a line of text every browser sends with each HTTP request, identifying itself — nominally the browser name and version, rendering engine, operating system, and device type. It exists mostly for historical and compatibility reasons: servers used to (and sometimes still do) serve different content based on it, which is also why many browsers include tokens from other browsers in their own string for compatibility.
How to use this parser
Paste a user-agent string (from a server log, an analytics report, or a bug reproduction) and click Parse to see it broken down into browser, OS, engine, and device information. Click Use My Browser's User-Agent to instantly parse the string your own browser is currently sending.
Common use cases
- Debugging a bug report by understanding exactly which browser and OS combination a user was on
- Investigating server log entries to understand traffic patterns by browser or device type
- Checking what a custom or unusual user-agent string (from a bot, script, or embedded webview) actually identifies as
A word of caution
User-agent strings are trivially spoofable — any browser extension, developer tools override, or HTTP client can set an arbitrary value. Useful for analytics and debugging, but never rely on a user-agent string as a security or identity check.
How to use User-Agent Parser for related tasks
Paste the UA string, inspect the detected fields, and treat unusual or spoofed strings cautiously because user agents are not reliable identity proof.
Related tools: REST API Tester, JSON Parser.
Frequently asked questions
Is my user-agent string uploaded anywhere?
No — parsing happens entirely in your browser. Nothing is sent to a server, including when you inspect your own current user-agent.
Why do some browsers show up with confusing names, like "Mobile Safari" or a Chromium-based browser showing as Chrome?
Many browsers (Edge, Opera, Brave, Vivaldi) are built on the Chromium engine and include "Chrome" in their user-agent string for compatibility with sites that check for it — parsers can only report what the string itself says, and some browsers deliberately make themselves hard to distinguish from Chrome this way.
Can a user-agent string be faked?
Yes, trivially — browser extensions and developer tools can override the user-agent your browser sends, and any HTTP client can set an arbitrary one. Never treat user-agent parsing as a reliable security check; it's useful for analytics and feature-detection hints, not for verifying a client's true identity.
Why is the device type empty for a desktop browser?
Desktop is effectively the default/unset case in most user-agent parsing — device type is really only populated for mobile, tablet, TV, or other non-desktop form factors that include explicit identifying tokens in their user-agent string.
Can a user-agent parser identify a user reliably?
No. User-agent strings can be changed or reduced by privacy settings; use them for compatibility hints, not authentication or precise analytics.