You open a site on your desktop and it hands you the stripped-down mobile version. Or you built a page and want to see what phone users see, without picking up your phone. The fix takes about two minutes. Your browser sends a short identity string, called a user agent, with every request it makes. Change that string and the site treats you like a different browser. Here is how to do it in Chrome and Firefox, and how to prove the switch actually worked.

First, see what sites see right now
Before you change anything, grab a baseline. Open ProxyNest's user agent checker. It shows the exact string your browser is sending right now, plus the browser, operating system and device it decodes to. Keep that tab open. It is your before photo.
On a Windows laptop, Chrome might report something like this: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36. That is a real current string, straight from MDN's reference. If you want the full anatomy of that line, our guide to what your user agent is breaks down every piece.
Now you know what "before" looks like. Time to change it.
Change your user agent in Chrome
Chrome hides this in Developer Tools. It takes five clicks and no extensions:
- Press F12 to open DevTools. On a Mac, use Cmd+Option+I.
- Click the three-dot menu inside DevTools, then More tools, then Network conditions.
- Under User agent, uncheck Use browser default.
- Pick a preset from the dropdown, or choose Custom and paste a full string. To pretend to be an iPhone, paste this one from MDN: Mozilla/5.0 (iPhone; CPU iPhone OS 18_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.0 Mobile/15E148 Safari/604.1
- Keep DevTools open and reload the page. The site now sees the new identity.
Here is the catch, and it trips up almost everyone the first time. The override only lives while DevTools stays open, and only in that one tab. Close the panel and Chrome quietly goes back to its real user agent. I did exactly this the first time I tested it: set the string, closed DevTools for a clean look at the page, and spent five confused minutes wondering why the site had flipped back to desktop. If your change seems to vanish, check whether DevTools is still open. That is usually the whole mystery.
Want something that survives closing DevTools? Launch Chrome from the command line with the --user-agent flag and your string in quotes. It applies to the whole session. One warning: close every Chrome window first. If Chrome is already running, the new window just joins the old process and ignores your flag.

Prefer watching? This short walkthrough shows the same Chrome and Firefox steps on screen.
Change your user agent in Firefox
Firefox does it differently. There is no built-in switcher, so you set a hidden preference. It takes a little longer to set up, but the change sticks across every tab until you remove it:
- Type about:config in the address bar and accept the warning.
- Search for general.useragent.override.
- If it is not there, type the name, choose String, click the + button, and paste your full user agent string as the value.
- Reload the page you are testing. Every tab now sends the new string.
To undo it, go back to about:config, find the same preference and click the trash icon to delete it. Delete it, don't just empty it. An empty value is not the same as no override, and it can leave you with a broken-looking identity.
One more trap. If privacy.resistFingerprinting is set to true in about:config, Firefox replaces your custom string with a generic one. Your override will look like it saved fine and do nothing at all. If your new user agent never shows up in the check, look at that setting first.
My take: Firefox's way is clunkier to set up and better for a longer test, because it sticks. Chrome's way is faster for a thirty-second check.
How to check it worked (don't skip this)
Reload the user agent checker in the same tab. The browser, operating system and device it reports should now match the string you set. Then open the HTTP headers tool, which shows the raw User-Agent header your browser actually sent, exactly as the server received it. The checker tells you what the string decodes to. The headers tool shows you the string itself. Check both.
Here is what a good result looks like. Before the switch, the checker said Chrome 143 on Windows. After pasting the iPhone string, it said Safari 26 on iPhone, running iOS 18.6. If your checker still says Chrome on Windows, the switch did not take. Walk through the next section before you blame the site.

It still shows your real browser? Three usual culprits
1. You closed DevTools. In Chrome, that ends the override instantly. Reopen DevTools, redo the Network conditions steps, and reload with the panel open.
2. Firefox is resisting fingerprinting. Check privacy.resistFingerprinting in about:config. If it is true, your override gets replaced with a generic string.
3. Client Hints are giving you away. Modern Chrome also sends Sec-CH-UA headers that can still name your real browser and platform. Changing the user agent string changes one header, and the hints can disagree with it. MDN's User-Agent reference explains the shift: Chrome now sends a reduced string, with the major version real and the minor version as zeros, and the detail moved to Client Hints. A strict site that compares the two will spot the mismatch. See our guide to what HTTP headers reveal for the rest of what a site can read.
And keep the honest limit in mind: a changed user agent does not change the rendering engine, and it does not hide your IP address. A site still sees where the request comes from. If the IP needs to match the story too, pair the switch with a proxy from the proxy list, and test that proxy first with the proxy checker so you know it is alive before you trust it.
What changing your user agent can't do
It won't turn Chrome into Firefox. The engine underneath stays the same, so a page that needs a real Firefox feature will still fail. It won't make you anonymous either. Your IP, your cookies and the rest of your fingerprint are untouched. And it won't beat a ban or a paywall. Sites that care check more than one header.
But for the job it is actually for, checking how a site treats a different browser, it is a two-minute tool that works. Open the user agent checker, flip the string, reload the checker, and watch the identity change. Then flip it back. Your real browser will be glad to have its name back.
Comments
Loading comments…
Leave a comment