What's in a User-Agent String? Decode Yours in One Click

Every time your browser makes a request, it sends along a line of text identifying itself - something like Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36. That’s the User-Agent string, and it’s been part of the web since the earliest browsers, for reasons that are mostly historical accidents rather than good design.

Why it looks so messy

Notice that string claims to be “Mozilla,” mentions “like Gecko,” and lists “Safari” even in Chrome. None of that is a mistake - it’s the result of decades of browsers impersonating each other to avoid being blocked by sites that checked User-Agent strings too strictly. Each new browser added its own real name onto the string while keeping the old browsers’ names in place, since removing them would break sites that specifically looked for “Mozilla” or “Safari” to decide whether to serve modern content. The result is a string that’s technically self-contradictory but universally parseable if you know the pattern.

What sites actually use it for

A User-Agent string tells a server your browser engine, browser version, operating system, and often whether you’re on mobile or desktop. Sites use this to decide what layout or content to serve, to block outdated or unsupported browsers, and as one input (among several) in browser fingerprinting for analytics or fraud detection. If a site is behaving strangely - showing a broken layout, or refusing to load at all - checking exactly what it’s seeing from your browser is a reasonable first debugging step.

Decoding yours

Our User-Agent & Device Lookup tool parses your current browser’s User-Agent string into readable fields - browser name and version, operating system, and device type - entirely client-side, so nothing is sent anywhere. It’s the same string every site you visit already receives; the tool just makes it legible.

Where this fits with fingerprinting

User-Agent is only one signal among many that sites can use to build a fingerprint of your browser - canvas rendering, installed fonts, and WebRTC-exposed IPs are others. If you’re specifically interested in the privacy side rather than just the browser/OS breakdown, our Privacy & Browser Leak Checker covers WebRTC IP leaks and other fingerprinting signals in more depth, and we’ve written separately about checking for WebRTC and DNS leaks specifically.