How do I read my own browser's current User-Agent?

Click "Use my browser's" above the input box, it fills the field with navigator.userAgent from your current browser session and parses it immediately, no need to look it up or copy it from developer tools.

Why does the Device field say Desktop / unknown?

Most desktop browser User-Agent strings don't encode a device vendor or model the way mobile ones do, so the parser falls back to the detected device type, or this generic label if even that isn't present in the string.

Does pasting a User-Agent string send it to a server?

No, the ua-parser-js library runs entirely as JavaScript in your browser tab, so a User-Agent string copied from an internal log or bug report is never transmitted anywhere to be parsed.

Can this tool detect a spoofed User-Agent?

No, it only reads whatever text is in the string and matches it against known patterns; it has no way to check that string against the browser actually making the request, so a deliberately altered value parses at face value.

User-Agent Parser

Break a User-Agent string into browser, engine, OS and device, locally.

Local, Runs entirely in your browser, your data never leaves your device.

Loading tool…

Break a User-Agent header into browser, OS and device

A User-Agent string packs a browser name and version, rendering engine, operating system, device vendor and model, and CPU architecture into one dense line that's genuinely hard to read by eye. This tool runs it through the ua-parser-js library and lays the result out as labeled fields, which is useful when you're reading server logs, debugging a device-specific bug report, or checking what a spoofed or custom User-Agent actually claims to be. Parsing runs on the string you paste, in your browser tab.

How to use the User-Agent Parser

Paste a User-Agent string into the text box, or click "Use my browser's" to fill in the one your own browser is sending right now.
Read the Browser and Engine rows for the name and version of the browser and its rendering engine.
Check Operating system, Device and Device type for the platform and hardware the string claims to run on.
Hover a row and click its copy button to copy just that field's value.

Fields the parser can't determine from the string, such as device vendor and model on a plain desktop browser, are reported as "Unknown" or a generic "Desktop / unknown" rather than left blank, so an empty-looking result usually means the User-Agent genuinely doesn't encode that detail.

Detection is pattern-based against known browser and device signatures, so a very new browser release or an intentionally spoofed string can be misread or only partially recognized; treat the output as a best-effort read, not a guaranteed fingerprint.

Frequently asked questions

How do I read my own browser's current User-Agent?: Click "Use my browser's" above the input box, it fills the field with navigator.userAgent from your current browser session and parses it immediately, no need to look it up or copy it from developer tools.
Why does the Device field say Desktop / unknown?: Most desktop browser User-Agent strings don't encode a device vendor or model the way mobile ones do, so the parser falls back to the detected device type, or this generic label if even that isn't present in the string.
Does pasting a User-Agent string send it to a server?: No, the ua-parser-js library runs entirely as JavaScript in your browser tab, so a User-Agent string copied from an internal log or bug report is never transmitted anywhere to be parsed.
Can this tool detect a spoofed User-Agent?: No, it only reads whatever text is in the string and matches it against known patterns; it has no way to check that string against the browser actually making the request, so a deliberately altered value parses at face value.