What a User Agent String Looks Like
A typical user agent string looks dense and technical at first glance, 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. Despite the appearance, each part identifies something specific: the rendering engine, the operating system, and the browser name and version.
Why Websites Read Your User Agent
Websites use your user agent string for a handful of practical reasons: serving a mobile-optimized layout to phones, applying browser-specific fixes for known rendering quirks, gathering aggregate analytics on which browsers visitors use, and occasionally restricting features on outdated or unsupported browser versions.
See your exact user agent string and what it reveals about your current browser and device.
Check Your Browser Info →Can Your User Agent Be Changed?
Yes. Most desktop browsers let you override the user agent string through developer tools, typically used by developers testing how a site behaves on other browsers or devices without needing separate hardware. Browser extensions can do the same thing for everyday browsing, though this is far less common outside of testing and development.
Is Your User Agent a Privacy Concern?
A user agent string alone reveals general, non-identifying details shared by millions of other users on the same browser and OS combination. The bigger privacy consideration is browser fingerprinting — combining the user agent with other signals like screen resolution, installed fonts, and timezone to build a more unique profile of a specific device across visits.
How User Agent Strings Have Changed
Modern browsers have started reducing how much detail the user agent string reveals by default, a shift often called "user agent reduction." Instead of exposing a precise operating system build number, newer browser versions report a more generic version string and let sites request additional details only when genuinely needed, reducing how much passive fingerprinting data is exposed to every site by default.
User Agent vs. Client Hints
Some modern browsers are moving toward a newer system called Client Hints, which lets a site explicitly request only the specific details it needs — such as whether the device is mobile — rather than receiving the full string automatically on every request. This is intended to reduce unnecessary data exposure while still letting sites adapt their layout correctly.
Curious what your browser reveals beyond the user agent string, like screen size, plugins, and connection details?
See Full Browser Details →For more background, see MDN Web Docs (developer.mozilla.org).
Frequently Asked Questions
What is my user agent?
Your user agent is a text string your browser automatically sends to every website you visit. It identifies your browser name and version, operating system, and device type, letting sites adjust what they show you.
Why do websites need my user agent string?
Sites use it to decide which version of a page to serve, a mobile layout versus a desktop one for example, and to troubleshoot browser-specific bugs by knowing exactly which browser and version a visitor is using.
Can a user agent string be changed or faked?
Yes. Browser developer tools and certain extensions let users override their user agent string to appear as a different browser or device, often used for testing how a site looks on other platforms.
Is my user agent string a privacy risk?
On its own, it's a small piece of data. Combined with other details like screen size, installed fonts, and timezone, it can contribute to browser fingerprinting, a technique used to identify a device across visits.