What Is a User Agent? A Plain-English Guide (and Why It Matters for Multiple Accounts)

 A user agent is the “introduction” your browser sends with every request to a website.

A user agent is a line of information (the HTTP header called User-Agent) that your browser automatically sends to every website, telling it which browser you use, which version, and which operating system.

Every time you open a web page, your browser does not just ask for content — it also hands over a little “business card” describing itself. That card is the user agent. Websites read it to decide whether to serve the desktop or mobile layout, and whether to send a fallback for older browsers. This guide explains user agents in the simplest terms, breaks down each part of the user agent string, and shows why it matters especially to anyone running multiple accounts.

Table of contents

• What is a user agent?

• What does a user agent string look like?

• What do websites use a user agent for?

• How can you see your own user agent?

• Does a user agent reveal your identity?

• How does a user agent affect managing multiple accounts?

• Is the user agent slowly going away?

What Is a User Agent?

A user agent is any software that acts “on behalf of” a user to access the web — most often a web browser. In technical practice, the phrase usually points to the user agent string: a line of text your browser sends inside the “User-Agent” header of every HTTP request. Browsers are not the only things with a user agent; bots such as Googlebot, RSS readers, and email clients also carry their own strings to identify themselves to servers.

In short, the user agent answers the question, “which piece of software is knocking on this website’s door?” It is public information, sent automatically, and you rarely see it unless you go looking for it.

What Does a User Agent String Look Like?

A user agent string is a single line made of several “tokens,” each revealing one detail: a legacy compatibility token, the operating system, the rendering engine, then the browser name and version.

Here is an example user agent for Chrome on Windows:

 Each part of the user agent string reveals a different detail about your device.

Here is what each component tells a website:

Notice that almost every browser begins with “Mozilla/5.0.” This is a historical quirk: back when browsers had to imitate each other to be served the right content, everyone kept the token — and they still do, just to be safe.

What Do Websites Use a User Agent For?

Websites read the user agent to serve the right version (desktop or mobile), collect statistics, and identify bots — though they rely on it less and less for important decisions.

The most common uses include:

● Choosing a layout: returning a responsive mobile page or the full desktop version.

● Compatibility: sending a fallback to older browsers that lack newer features.

● Analytics: measuring the browser and operating-system share of visitors.

● Bot handling: recognizing crawlers by their user agent (for example, Googlebot) to allow or block them.

● Fraud and security signals: combining the user agent with other data to spot unusual behavior.

Because a user agent is so easy to edit, serious platforms never trust it alone — they cross-check it against many other signals, and that is where fingerprinting comes in.

How Can You See Your Own User Agent?

You can see your user agent by opening your browser’s Console and typing navigator.userAgent, or by visiting a website that displays it for you.

The two fastest methods:

● Open DevTools (press F12) → Console tab → type: navigator.userAgent and press Enter. The browser prints the exact string it sends.

● Visit a checker such as whatismybrowser.com — it shows your user agent alongside your browser details.

On a phone, the string contains tokens like “iPhone; CPU iPhone OS” or “Android 14; Mobile” in place of the Windows/macOS section.

Does a User Agent Reveal Your Identity?

A user agent contains no name or address on its own, but combined with other signals it becomes one building block of a browser fingerprint that lets websites recognize and track you.

A user agent describes software, not a person — it does not know who you are. Yet on its own it still carries some identifying power: a rare string (an old browser, an unusual OS) makes you stand out. When a website pairs the user agent with your screen resolution, time zone, font list, canvas/WebGL output, and language, they form a near-unique fingerprint — this is browser fingerprinting.

 Sharing one user agent across accounts makes them easy to link together.

A crucial point: consistency matters more than the specific value. If your user agent claims you are on an iPhone but the other signals say Windows, anti-fraud systems flag it immediately. Changing only the user agent, and nothing else, can therefore backfire.

How Does a User Agent Affect Managing Multiple Accounts?

When you run several accounts on one machine, if they all send an identical user agent (and fingerprint), platforms can conclude they belong to the same person and link — or even ban — many accounts at once.

This is why multi-store sellers, marketers running many ad accounts, and airdrop communities care so much about the user agent. In practice, when operating hundreds of profiles, letting every profile look identical is one of the most common causes of mass account suspensions.

The right fix is not to change the user agent tab by tab, but to give each account its own separate, consistent browser environment:

● One sensible user agent per profile, matching the corresponding operating system and engine.

● A synchronized fingerprint: canvas, WebGL, fonts, time zone, and language all match that user agent.

● Pairing each profile with its own proxy so the IP and user agent tell the same story.

This is exactly what an antidetect browser like GPM Login automates: it creates many profiles, each carrying its own stable fingerprint, instead of forcing you to tweak everything by hand. If you are just starting out, read more about how browser fingerprinting works [confirm URL] to see the full picture.

Is the User Agent Slowly Going Away?

Partly yes: Google has “reduced” Chrome’s user agent string and is shifting toward User-Agent Client Hints — a system that returns detailed information only when a website asks for it.

Since roughly early 2023 (Chrome 110 and later on desktop), Chrome began cutting the detail in its user agent string: freezing the minor version to “0.0.0” and trimming operating-system details, to limit passive fingerprinting. In its place come User-Agent Client Hints (UA-CH): if a website wants the details (for example, the full version), it has to request them explicitly.

For everyday users, this change is almost invisible. For anyone managing multiple accounts, the takeaway is this: the user agent has not disappeared, but it is increasingly just one signal among many — which only reinforces the need to manage the whole fingerprint, not a single line of text.

Frequently Asked Questions

Are a user agent and an IP address the same thing?

No. A user agent describes software (browser, operating system), while an IP address indicates your network location. They are two independent signals, and websites usually consider both together.

Will changing my user agent make me fully anonymous?

No. Changing the user agent alters only one line of information. Websites can still recognize you through canvas, WebGL, fonts, time zone, and many other signals. True anonymity requires managing your entire fingerprint consistently.

Is spoofing a user agent legal?

Changing the user agent of your own browser is normal and supported by many web-development tools. The legal and terms-of-service questions depend on how you use it, not on the act of changing the string. Always follow the terms of the platforms you visit.

Does Googlebot have its own user agent?

Yes. Crawlers such as Googlebot use their own user agent strings so websites can recognize them — for example, strings containing the word “Googlebot.” This lets site owners allow or tailor how content is served to bots.

Is changing the user agent enough to run multiple accounts safely?

Not by itself. If the user agents differ but every other signal is identical, the accounts can still be linked. The durable solution is one independent profile per account, each with its own matching fingerprint and proxy — which an antidetect browser handles automatically.

Conclusion

A user agent is the “introduction” your browser sends to every website: which browser you use, which version, and on which operating system. On its own it is harmless, but combined with other signals it becomes part of a fingerprint that can track you. For anyone managing multiple accounts, understanding the user agent is the first step to understanding why accounts get linked — and why each account needs its own browser environment.