A user agent is a short technical string your browser sends automatically when it requests a web page. It identifies the browser, version, operating system, and sometimes device type so the website can decide how to respond.
Does this affect you?
Use this explanation for any desktop or mobile browser. You usually do not see the user agent unless you inspect network requests or search for your current browser string.
What a user agent is actually used for
Websites read this in the background with each request.
- Serving the right layout: A site can use the user agent to decide whether to send a mobile or desktop layout, or whether to adjust behavior for touch screens.
- Checking compatibility: A site may warn you when the browser version is too old for a feature it needs.
- Analytics: Site owners use aggregated user agent data to understand which browsers, devices, and operating systems visitors use.
- Fingerprinting signal: A detailed user agent can contribute to browser fingerprinting when combined with screen size, fonts, language, time zone, and other details.
More control
Browsers are reducing how much detail is shared
Because detailed user agent strings can help fingerprinting, Chrome and other browsers have moved toward User-Agent Client Hints. Instead of giving every site the full detail automatically, the browser shares a smaller default set and lets sites request more detail when needed.
You can view your own user agent
Search the web for what is my user agent, or open developer tools, check the Network tab, select a request, and look at its request headers. This shows what a website sees from your browser.
Developers can override it for testing
Some browsers let developers spoof a different user agent to test mobile layouts or browser compatibility. That only changes what the site thinks you are using; it does not add missing browser features or change the real device.
It rarely identifies you by itself
Many people share the same browser version and operating system, so the user agent alone usually is not unique. Its privacy impact comes from being combined with other browser and device details.
Sources
- MDN Web Docs – User-Agent header (2025)
- Google Chrome Developers – Reduce your User-Agent string entropy with User-Agent Client Hints (2024)
- Mozilla Developer Network – Browser detection using the user agent (2025)