VKT Toolkit · September 12, 2026 · 8 min readHow to Change User Agent in Chrome (2026): DevTools vs Extension
The server shows you the mobile page, the broken IE layout, the geo-restricted banner — and behind all of it sits one line that decided your fate: the User-Agent header. Changing it is the oldest dev trick on the web: check what a site serves phones without owning a phone, reproduce a bug that only happens in an old browser, see roughly what the crawler sees. In 2026 Chrome offers three realistic ways to do it — two inside DevTools and one extension — and what separates them is scope and staying power, not capability.
What User-Agent Actually Tells Servers
The header is a single plain line in every request:
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
Anatomy: the Mozilla/5.0 prefix is a compatibility handshake left over from the browser wars that nobody dares remove. The parenthesized part names your operating system. AppleWebKit and KHTML declare the rendering engine, Chrome/… the browser version, and the trailing Safari/… is one more legacy courtesy token. Servers parse this string before a single byte of HTML moves: it picks the mobile or desktop layout, gates features, chooses app-store banners, sometimes decides which file you download. That decision happens on the wire — which is exactly the part you can rewrite.
Method 1: DevTools Device Mode
The fastest one-off check. Open DevTools with F12, toggle the device toolbar (Ctrl+Shift+M), and pick a preset device — or open the UA dropdown and choose "Other…" to paste any string you like. Chrome then sends the chosen User-Agent for requests from that tab, and header-gated servers answer with the mobile page immediately.
The catch is by design: the override belongs to that tab and that DevTools session. Reload, close the tab, or shut the browser and your real User-Agent is back. Perfect for a quick "what does this look like on an iPhone"; useless as a standing configuration you rely on daily.
Method 2: DevTools Command Menu Override / Flags
The DevTools command menu (Ctrl+Shift+P) exposes the same device overrides, Settings → Devices lets you edit the UA list, and you can even launch Chrome with a --user-agent switch. Honest limits: the DevTools variants reset just as stubbornly and are awkward to keep configured, while the launch flag stamps every tab in that browser window with the same fake identity — the opposite of containment. Neither is a daily-driver workflow.
Method 3: A Header Extension (Recommended for Repeat Work)
If you change User-Agent more than once a week, VKT Header turns it into a saved, contained, self-cleaning operation. It's a Manifest V3 Chrome/Edge extension that rewrites request headers through declarativeNetRequest session rules:
- Templates: save "iPhone Safari", "Old Chrome", "Googlebot" as profiles — apply one in a click instead of pasting a string every time.
- Tab isolation: rules apply to the tab you target, so the fake UA never follows you everywhere.
- URL matching: bind a template to specific URLs so the right test tab automatically gets the right identity.
- Auto-cleanup: session rules die when the tab closes or the browser restarts — no forgotten UA masquerading as you next week.
The free tier covers 5 profiles with 5 headers each; Premium ($9.99 one-time, lifetime, or $2.99/month) removes the caps and adds priority support. Install from the Edge Add-ons store, or use the Chrome install link on the product page. One honest boundary: VKT Header changes request headers only — see the caveat below before relying on it for anything more.
The Three Methods Side by Side
| Method | Persistence | Scope | Setup speed | Cleanup |
|---|---|---|---|---|
| DevTools device mode | Until reload or tab close | That one tab | Seconds | Gone on its own — and gone when you need it |
| Command menu override / launch flag | Resets on restart; flag lasts the window | Tab (DevTools) or entire window (flag) | Fiddly to keep configured | Unpredictable |
| VKT Header | Profiles saved forever; rules live per tab | One tab, or URL-matched tabs | One click after setup | Automatic — closing the tab wipes every rule |
The Honest Caveat: Headers vs Fingerprints
Changing the User-Agent header changes what the server reads on the wire. It does not change what JavaScript reads: navigator.userAgent still reports your real browser, and modern fingerprinting — client hints, canvas, plugin truth — can expose the mismatch. That's fine for testing and compatibility checks, which is exactly what this is for. It also means you shouldn't use a UA swap to deceive: security-sensitive sites like banking and app stores flag on mismatch, and some services' terms of service outright prohibit misrepresenting your client. Test with it; don't masquerade with it.
Frequently Asked Questions
Does changing User-Agent in DevTools apply to all tabs?
No. The DevTools override is scoped to the tab whose DevTools you configured, and it is temporary — reload the page or close the tab and your real User-Agent is back. Launch flags are the opposite extreme: they stamp every window you start with that flag.
Will servers actually serve me mobile pages?
Split the question honestly. If the server gates on the User-Agent header — most mobile/desktop layout switches do — yes, you'll get the mobile page. If the decision is made client-side, in JavaScript or fingerprinting that reads navigator.userAgent and other signals, a header change alone won't convince it, and shouldn't try to.
Is changing User-Agent legal?
For testing, development and compatibility checks, it's an ordinary developer workflow. Misrepresenting your client to bypass restrictions can violate a site's terms of service — and in some jurisdictions more. When in doubt, test on systems you own or are authorized to test. Nothing here is legal advice.
What's the best free way to keep a custom User-Agent?
VKT Header's free tier stores 5 profiles with 5 headers each — including tab isolation, URL matching and import/export — so a saved "iPhone Safari" identity is one click away, and it self-clears when the tab closes. Premium lifts the caps for $9.99 one-time, lifetime.
Why does my bank or app complain after I change User-Agent?
Because the header now disagrees with your browser's real fingerprint — that mismatch is exactly the honest caveat above, and fraud detection treats it as a red flag. Clear the rule and everything behaves normally again. With VKT Header's auto-cleanup, closing the tab has already cleared it.
Our take: DevTools answers "what does this page serve an iPhone, right now". A tab-scoped extension answers "every day, for exactly one tab, and then never again" — saved profiles, URL matching and session rules that die with the tab make VKT Header the daily-driver choice for repeat UA work, free to start with 5 profiles.
More VKT tools live in the extensions catalog, or reach us at [email protected].