User-Agent Parser
Parse a User-Agent string into browser and version, rendering engine, operating system, device type and known bots and HTTP clients.
Free · No sign-up · Your inputs stay in your browser
Input
Parse a User-Agent string
Output
Chrome 141
| Browser | Chrome 141.0.0.0 |
|---|---|
| Engine | Blink |
| Operating system | macOS 10.15.7 |
| Device type | Desktop |
| Bot or tool | no |
Note
Reduced User-Agent
The version and OS fields here are frozen placeholders, not the real values.
User-Agent strings are self-reported and trivially faked, so never use one for access control. Chrome and Edge now freeze most of the string (UA reduction): the minor version reads 0.0.0 and macOS always reports 10_15_7. The full detail is in the Sec-CH-UA client hint headers.
Runs in this browser. Nothing you paste is sent to a server.
About this tool
Method, assumptions, practical next steps, and limits.
Why Chrome says Safari and Mozilla
Every browser's User-Agent carries tokens copied from older browsers so that sniffing scripts would serve it the modern page, which is why Chrome's string mentions Mozilla, AppleWebKit, KHTML, Gecko and Safari. Parse it in the right order or Chrome is reported as Safari.
User-Agent reduction
Chromium browsers now send a frozen string: the minor version is always 0.0.0, macOS is always 10_15_7 and Android hides the device model. The detail moved to User-Agent Client Hints headers that a server requests. Treat the User-Agent as a hint for analytics and support, never for security: any client can send any string.