How to Override the User-Agent in Chrome

Updated October 2026 · v1.2.0

Sites read the User-Agent header to guess the browser. Chrome can override it for a debugging session from DevTools. That override is easy to forget and is not a saved profile.

HeaderSwap can set the User-Agent on requests that match a site filter, including a mobile preset. The page may still behave like desktop Chrome, because the User-Agent is only one signal.

Get HeaderSwap for Chrome

Use DevTools for a quick check

Best when you need the override for a few minutes on one tab.

Open DevTools. On the page, open the device toolbar or the network conditions User-Agent list.
Pick a browser string. Choose a built-in User-Agent or paste one. Reload.
Turn it off. Clear the override before you file a bug that only existed while it was on.

Save a User-Agent on a profile

Use a profile when the same mobile or partner User-Agent has to survive the next reload and the next day.

Add a User-Agent header rule. Or apply the mobile User-Agent preset. Limit it to the host you are testing.
Reload and read the request. In the network panel, confirm the User-Agent on the document request.
Pause the profile. Your normal Chrome User-Agent returns as soon as the rule is off.

A header is not a phone

Screen size, touch events, and client hints can still say “desktop”.
Some sites ignore User-Agent and use other checks.
Do not use a spoofed User-Agent to bypass an access control you are not allowed to test.

Frequently Asked Questions

Will this make the site render a mobile layout?

Only if the site actually branches on that header. Many sites use viewport width instead.

Does the free plan include the mobile preset?

Yes. Presets are on the free plan, inside the free rule cap.

Can I set a different User-Agent per environment?

Yes. Put each string on its own profile and duplicate Local as Staging when the rest of the rules should match.