My User Agent

Every time your browser makes a request to a website, it sends a User-Agent string along with it. This string identifies your browser, its version, the operating system you're running, and sometimes additional details about your device. The server receiving the request can use this information to decide how to respond — serving different layouts, features, or content based on what browser you're using.

What does a user agent string actually look like? They're notoriously messy. A Chrome user agent on Windows might look something like: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36. It says "Mozilla" even though it's Chrome, references WebKit even though Chrome uses Blink — this is years of historical baggage from browsers trying to get websites to serve them the right content.

Why would you need to know your user agent? Several reasons. Web developers frequently check it when debugging browser-specific issues — if a bug only happens in one browser, the user agent helps reproduce it. Some websites or APIs require you to send a specific user agent. Customer support teams sometimes ask for it to understand your setup. Security researchers analyze user agents to identify bots and automated traffic.

Beyond the raw string, this tool parses out the meaningful parts — browser name and version, OS, device type (desktop, mobile, tablet), and the rendering engine. It also shows your browser language, cookie support status, number of CPU threads (hardware concurrency), and whether you're currently online.

All detection happens locally in your browser. The data is read from the navigator object, which is available to any JavaScript running on the page. Nothing is logged or sent to our servers.