How to Find and Read Your User Agent

Every time your browser requests a page, it sends a short line of text called the user-agent string. It identifies the browser and version, the rendering engine, and the operating system, so the website can respond appropriately — serving a mobile layout to a phone, for example.

You can see your own user-agent instantly with the User Agent Finder, which also parses the raw string into a readable breakdown. That saves you from decoding the string yourself, which is harder than it looks.

A modern user-agent is full of names that seem wrong. Chrome on Windows reports 'Mozilla/5.0', 'AppleWebKit', 'KHTML, like Gecko', and 'Safari' all in one line, even though none of those are Chrome. This is historical baggage: browsers copied each other's tokens over the years so that older sites would treat them as compatible.

Because of that clutter, reading the string by eye is error-prone. The finder checks the tokens in the right order — Edge and Opera both contain 'Chrome', so it looks for the specific ones first — and reports the browser you are actually using.

Getting your user-agent takes only a moment and needs no technical setup.

The most common reason to grab your user-agent is a bug report. Developers ask for it because a problem often depends on the exact browser and version, and the string pins that down precisely.

It is also useful for testing — confirming a site detects your browser correctly — and for curiosity about what every page can read about your setup. Keep in mind that user-agents are easily changed and are being simplified for privacy, so treat them as a helpful signal rather than proof of identity.