User-Agent Parser
Paste any User-Agent string to detect the browser, rendering engine, operating system, device type, CPU architecture and whether it looks like a bot. Everything runs in your browser — your data is never sent anywhere and nothing is stored.
How to use the User-Agent parser
- Your browser's own User-Agent is loaded automatically — or click Use my browser to refill it.
- Paste any other User-Agent string you want to inspect into the box.
- The results update as you type, or click Parse. Each field shows Unknown when it cannot be detected.
The parser recognises common browsers (Chrome, Edge, Firefox, Safari, Opera, Samsung Internet), operating systems (Windows, macOS, Linux, Android, iOS, Chrome OS) and well-known bots. A User-Agent is just text and can be spoofed, so treat the result as a hint, not proof.
More PAYATE tools
Frequently asked questions
What is a User-Agent string?
A User-Agent is a line of text your browser sends with every request to identify itself. It usually names the browser and its version, the rendering engine, and the operating system — for example Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0 Safari/537.36.
Is my User-Agent sent anywhere?
No. Parsing runs entirely in your browser — the string is read and analysed locally, nothing is uploaded to a server and nothing is stored.
Why does Chrome say it is also Safari and Mozilla?
For historical compatibility nearly every browser still begins with Mozilla/5.0 and Chromium-based browsers also include Safari/537.36 because they share the WebKit/Blink lineage. The parser looks for the most specific token (such as Chrome, Edg or OPR) to decide the real browser.
What is the rendering engine?
The rendering engine turns HTML and CSS into what you see. Blink powers Chrome, Edge, Opera and most Chromium browsers; WebKit powers Safari and all iOS browsers; Gecko powers Firefox; older Edge used EdgeHTML.
Can a User-Agent be faked?
Yes. A User-Agent is just text and can be changed or spoofed by the client, so it should never be trusted for security decisions. It is useful for analytics, troubleshooting and feature hints, not authentication.
How do you detect bots and crawlers?
The parser checks for well-known crawler tokens such as Googlebot, bingbot, DuckDuckBot and generic words like bot, crawler or spider. A match flags the agent as a bot, though some bots deliberately omit these tokens.