Parse a User-Agent string into browser, OS, and device details.
About this tool
Paste a browser User-Agent string to break it down into browser name and version, rendering engine, operating system, and device type. Useful for debugging analytics data or browser-detection logic. All parsing happens in your browser — the string never leaves your device.
Paste any browser User-Agent string and Tabreon instantly breaks it down into browser, operating system, device, and engine details — entirely in your browser.
Why use Tabreon for this?
Parsing runs client-side — the User-Agent string you paste, which may come from private server logs, never leaves your browser.
Handles desktop and mobile User-Agent strings from all major browsers.
Never throws on malformed input — unrecognized fields are reported as "Unknown" instead of an error.
How to parse a User-Agent string
1Paste the User-Agent string. Copy a User-Agent string from server logs, analytics data, or your own browser, and paste it into the input panel.
2Review the breakdown. Browser, operating system, device, and rendering engine details appear in separate panels.
3Copy or download. Copy any individual panel, or download the full breakdown as a file.
What is a User-Agent string?
A User-Agent string is a line of text a browser sends with every request, identifying itself — browser name and version, rendering engine, operating system, and sometimes device model. Servers and analytics tools use it to tailor responses or understand traffic, but the raw string is dense and hard to read by eye; this tool parses it into labeled fields.
How Tabreon handles your data
Parsing runs entirely in your browser using the ua-parser-js library — the string you paste is never transmitted to a server.
Key features
Separate panels for Browser, Operating System, Device, and Engine/CPU
Handles both desktop and mobile User-Agent strings
Graceful "Unknown" fallback instead of an error for unrecognized strings
Copy-to-clipboard and file download
Common use cases
Debugging why a browser-detection script misclassifies a specific User-Agent string
Understanding a raw User-Agent value seen in server access logs
Checking which rendering engine a User-Agent string reports before writing engine-specific CSS
Common mistakes & limitations
User-Agent strings are self-reported by the browser and can be spoofed — parsing them is not a reliable way to enforce security decisions.
Very new or unusual browsers/devices not yet recognized by the underlying parser library may show as "Unknown" for some fields.
Frequently asked questions
No. Parsing happens locally in your browser using the ua-parser-js library — the string you paste is never transmitted to a server.
Some User-Agent strings omit certain details, or come from a browser/device the parser doesn't recognize yet. The tool reports "Unknown" for those fields rather than guessing or throwing an error.
No. A User-Agent string is fully controlled by the client and can be changed to anything — use it for analytics or debugging, never as a security or access-control mechanism.