How to Change Your User Agent (and Why Websites Still Know It's You)

Changing your user agent takes about ten seconds, and your browser already has the tools built in. The catch: flipping that one header rarely makes you anonymous, because modern sites cross-check it against a dozen other signals. Here is exactly how to change it on every major browser — and the honest picture of what it does and doesn't do.

Quick answer

To change your user agent in Chrome or Edge: open DevTools (F12) → ⋮ menu → More tools → Network conditions → uncheck Use browser default → choose or paste a custom user agent. In Firefox, type about:config, accept the warning, and set general.useragent.override to your chosen string. For a persistent, cross-tab change, install a user-agent switcher extension. None of this hides your IP, screen size, or User-Agent Client Hints — so sites that check those still see your real device class.

Want to confirm what a site actually receives? Run the User Agent tool — it shows your live string, the parsed browser/OS/device, and the Client Hints most spoofers forget about.

What "changing your user agent" actually changes

Your browser sends a User-Agent request header on every HTTP request — a text string naming your browser, engine, and operating system. Overriding it changes only that string. It does not change:

That is why the header is a weak privacy control on its own. It was designed for compatibility, not concealment.

Change your user agent in Chrome

1. Press F12 (or right-click → Inspect) to open DevTools.
2. Open the Network conditions tab. If you don't see it, click the ⋮ (kebab) menu → More tools → Network conditions.
3. Under User agent, uncheck Use browser default.
4. Pick a preset (Googlebot, an iPhone, an older Chrome) or paste a Custom string.

The override applies only to that tab, and only while DevTools stays open. Close DevTools and your real string returns. This is the safest mode for testing because it can't follow you around and silently break other sites.

Change your user agent in Edge

Edge is Chromium-based, so the steps mirror Chrome: F12 → Network conditions → uncheck Use browser default → choose or paste a string. Because Edge sends Client Hints by default, remember that emulating an iPhone in the UA string while your Client Hints still say "Windows / x86" is exactly the kind of mismatch that flags you.

Change your user agent in Firefox

Firefox does not ship Client Hints, so the legacy string carries more weight here.

1. Type about:config in the address bar and accept the risk warning.
2. Right-click anywhere → New → String.
3. Name it general.useragent.override.
4. Set the value to your desired user agent string.

This change is global and persistent until you reset that preference (right-click → Reset). Forgetting it is the classic way to spend an afternoon chasing a layout bug that only exists because you're still pretending to be Googlebot.

Change your user agent in Safari

1. Enable the Develop menu: Safari → Settings → Advanced → Show features for web developers.
2. In the menu bar, open Develop → User Agent.
3. Choose a preset or Other… to enter a custom string.

Safari, like Firefox, does not implement User-Agent Client Hints as of 2026, so the string is the primary identifier — but your IP and fingerprint are untouched.

Extensions: persistent switching across tabs

DevTools overrides are temporary by design. If you need a string to persist across every tab and reload, a user-agent switcher extension is the practical tool. Good ones let you:

• Set per-site rules (real string here, spoofed there).
• Quickly toggle between desktop and mobile.
• Whitelist sites that break under a fake string.

The trade-off is trust: an extension that rewrites your headers can see your browsing. Prefer open-source, well-reviewed options, and disable spoofing when you're done.

Why websites still know it's you

Here is the part most "fake user agent" guides skip. Bot-detection and anti-fraud systems were built precisely because the UA string is trivial to forge. They score consistency, not just the string:

• Client Hints vs UA string — Chromium browsers expose navigator.userAgentData. If your string says "iPhone" but the high-entropy hints say "Windows," that contradiction is a red flag.
• JavaScript reality checks — navigator.platform, maxTouchPoints, screen size, and WebGL renderer describe the actual machine. A mobile UA on a 2560-pixel touchless display is implausible.
• TLS and HTTP/2 fingerprints — the way your browser negotiates the connection is hard to fake and often betrays the real engine.
• IP reputation — a "Googlebot" string from a residential IP that fails reverse DNS is an obvious impostor.

Our User Agent tool runs a live consistency check and automation/bot check on your own session, so you can see how these contradictions look from a server's side. For the deeper mechanics, see what your user agent reveals about you and what your browser reveals about you.

Legitimate reasons to change it

Spoofing has a bad reputation it doesn't fully deserve. Common, fully legitimate uses:

The line you don't want to cross is using a forged string to evade access controls, scrape against a site's rules, or commit fraud — that can breach terms of service or worse.

If anonymity is the real goal

Changing your user agent is the wrong tool for hiding. If privacy is what you're after:

1. Hide your IP with a reputable VPN, and confirm it isn't leaking with a VPN leak test.
2. Reduce fingerprint entropy — privacy-focused browsers normalize many of the signals listed above so you blend into a crowd instead of standing out with a contradictory UA.
3. Block trackers at the network and browser level.

A consistent, ordinary-looking browser beats a heavily spoofed one every time. Standing out is the opposite of staying private.

Verify your change worked

After any override, reload the User Agent tool and check three things:

1. The raw string matches what you set.
2. The parsed device type reflects your intended target.
3. The Client Hints panel — if it still shows your real platform, the site is reading hints, not the string, and your spoof is leaking.

Treat your user agent as operational metadata you can edit for testing, not a cloak. For real privacy, layer IP and fingerprint controls underneath it.