User agent parser
Paste one or more user agent strings, such as the ones in your server logs, and get the browser, rendering engine, operating system and device type for each. Crawlers are recognised too.
Runs in your browser: nothing you enter is sent anywhere.
How to use it
- Paste a user agent string. Several strings, one per line, are parsed one after another.
- Read the browser, engine, operating system and device type.
What each field means
| Field |
Meaning |
| Browser |
The product and version, such as Chrome 121.0.6167.101. |
| Engine |
The layout engine: Blink (Chrome, Edge, Opera, Samsung Internet), WebKit (Safari, every browser on iOS), Gecko (Firefox), Trident (Internet Explorer). |
| Operating system |
Name and version when the string contains one. |
| Device type |
Mobile, tablet, desktop, TV, game console or bot. |
Why strings look so strange
Almost every string starts with Mozilla/5.0 and mentions several other browsers (Chrome strings say Safari and like Gecko). This is historical: sites once served better pages to Netscape, so every browser kept claiming to be compatible. The parser therefore checks the more specific names first: Edge (Edg/) and Opera (OPR/) before Chrome, and Chrome before Safari.
Tips
For new work, prefer feature detection over reading the user agent; use the string for analytics and logs.
Frequently asked questions
Where do I find a user agent string?
In server access logs, in the request header named User-Agent, or in your browser: the navigator.userAgent value in the developer console. The "My browser" tool on this site shows your own.
Why does Windows 11 show as Windows 10/11?
Browsers report Windows 11 as "Windows NT 10.0", the same as Windows 10, so a user agent string cannot tell them apart.
Why is the Android device model sometimes missing?
Recent Chrome versions freeze the model to a single letter (like "K") to reduce fingerprinting. The tool leaves the model empty in that case.
Can I trust the result?
A user agent string is a claim, not proof: any client can send any text, and crawlers or privacy tools may pretend to be browsers. Treat the result as a hint, and verify important bots, such as Googlebot, by reverse DNS.
Which things does it recognise?
Chrome, Edge (current and legacy), Firefox, Safari, Opera, Samsung Internet and Internet Explorer; engines Blink, WebKit, Gecko, Trident, EdgeHTML and Presto; Windows, macOS, iOS, Android, ChromeOS and Linux; and desktop, mobile, tablet, TV, game console and bot devices.