User-Agent Parser
Parse a User-Agent string for browser, operating system, rendering engine and device hints. Compare two entries or download the local results as JSON.
How to Read a Reduced User-Agent String
Paste one User-Agent header value per field, up to 4,096 characters.
User-Agent Parser: how to use it
- Paste one User-Agent header value or choose Use this browser’s User-Agent. Choose Load comparison example to see Chrome on Android beside Safari on iPhone.
- Turn on Compare two User-Agents to add a second value. Check the matched client token and read the notes for reduced or missing fields.
- Use Download JSON report to save the entered values with their parsed fields. The tool processes the values in your browser.
Limits and notes
Accepts one header value of up to 4,096 characters per input. Field detection uses common product and platform signatures. Client claims can be spoofed. Missing and reduced details may show Unknown. The tool reads the legacy browser value only when you choose it and does not request Client Hints.
How your privacy works →User-Agent Parser: common questions
Why does my Chrome User-Agent show Android 10 and K?
The combination matches Chromium’s reduced Android platform and model values. The browser can report these fixed strings on other Android releases and models.
Why does the parser show Chrome when the string also says Safari?
Chrome includes Safari as a compatibility token. The parser checks specific browser product tokens such as Chrome and Edg to identify the most likely client.
Does a Googlebot result verify the source of a request?
The result only shows that the source string claims to be Googlebot. The actual request sender requires separate verification.