Anatomy of a user agent
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36
- Mozilla/5.0: a historical token almost every browser sends for compatibility.
- (Windows NT 10.0; Win64; x64): the operating system and CPU architecture.
- AppleWebKit/537.36 (KHTML, like Gecko): the rendering engine family (Blink in Chrome still reports this).
- Chrome/130.0.0.0: the actual browser and version. "Safari/537.36" at the end is another compatibility token.
Tips for reading user agents
- Check browser tokens in the right order: Edge, Opera and Samsung Internet also include "Chrome" in their strings.
- On iPhone and iPad, every browser uses Apple's WebKit engine, so Chrome on iOS shows "CriOS" with WebKit.
- Chrome now freezes some details (like minor versions and Android model) in the user agent; client hints provide them instead.
See your own details with what is my browser.
Last reviewed October 2026.
Frequently asked questions
What does a user agent parser do?
It reads a user agent string, the text a browser or app sends to websites, and turns it into plain facts: browser name and version, rendering engine, operating system and version, and whether the device is a desktop, phone, tablet or bot.
Where do I find user agent strings?
In server access logs, analytics tools, support tickets and browser developer tools (Network tab, request headers). Your own appears in the box when the page loads.
Can a user agent be faked?
Yes. Any browser or script can send any user agent, and some privacy tools and bots deliberately imitate common browsers. Treat the result as what the client claims to be, not proof.
Why is the Windows version shown as "10 or 11"?
Windows 11 still identifies itself as "Windows NT 10.0" in the user agent, so the string alone can't separate the two versions.
Can I parse many user agents at once?
Yes. Paste one per line and switch to the table view to see all of them parsed side by side.