I configure proxies regularly — for testing geo-specific behaviour, routing scrapers, and one memorable week when a client's office network required one for everything — and the single most common misconception is that the proxy setting lives "inside Chrome." It doesn't, and hasn't for years: Chrome uses your operating system's proxy settings. This 2026 guide covers every working method, including the per-launch flag and extension routes when you genuinely need Chrome-only proxying.
Quick answer: In Chrome, go to Settings → System → Open your computer's proxy settings — Chrome hands you to Windows' or macOS' proxy configuration, and the change applies system-wide. For Chrome-only proxying, launch Chrome with the `–proxy-server` flag or install a switcher extension like SwitchyOmega. Verify any setup at browserleaks.com/ip before trusting it.
Proxy vs VPN: thirty seconds of theory
A proxy server sits between your browser and the internet: Chrome sends requests to the proxy, the proxy fetches the page and returns it, and the destination site sees the proxy's IP address instead of yours. A VPN does the same at system level but encrypts everything leaving your device.
Practical differences that matter:
- Chrome/system proxy: no encryption by itself (HTTP proxies), affects whichever apps use system settings, cheap or free, per-app control possible.
- VPN: strong encryption, whole device, usually paid, one on/off switch.
Use a proxy for IP rotation, testing location-specific behaviour, or accessing resources that whitelist certain IPs. Use a VPN when privacy from your network operator is the goal. And skip free public proxies entirely — you'd be routing your traffic through a stranger's computer that can read and modify everything that isn't HTTPS (more on that below).
Method 1: Chrome's system proxy settings (Windows)
Chrome's own settings page is the entry point:
1. Open Chrome → click the three-dot menu → Settings.
2. Click System in the left sidebar.
3. Click Open your computer's proxy settings — Chrome launches Windows' proxy panel directly.
4. In Windows Settings → Network & internet → Proxy, you have two paths:
- Automatic setup: use a setup script (PAC file) if your organisation gave you one — toggle "Use setup script," paste the script address, Save.
- Manual proxy: toggle "Use a proxy server," enter the proxy address and port (e.g. `proxy.example.com` and `8080`), optionally add exceptions for local addresses, then Save.
5. Reload a page in Chrome — traffic now flows through the proxy.
This applies to every Windows app that honours system proxy settings, not just Chrome — the same panels serve every major browser on Windows, which is exactly why Chrome stopped carrying its own. To undo it, return here and toggle the proxy off.
Google's own help page for Chrome's proxy behaviour documents the same flow on both platforms.
Method 2: The same on macOS
1. Open System Settings → Network.
2. Select your active network (Wi-Fi or Ethernet) → Details… → Proxies.
3. Enable the proxy types your server uses — Web Proxy (HTTP), Secure Web Proxy (HTTPS), or SOCKS — and enter address and port for each.
4. Click OK, then Apply. Chrome (and other Mac apps) pick it up immediately.
Since Chrome 2019-era versions dropped in-browser proxy screens, this OS-level step is mandatory on the Mac too — there is no Chrome-only checkbox.
Method 3: Launch Chrome with a proxy flag (Chrome-only)
When you want the proxy for Chrome but not for everything else on the PC, launch Chrome with a command-line switch:
1. Close every Chrome window (check the system tray — background Chrome must be gone).
2. Open Command Prompt or create a desktop shortcut with this target:
“`
"C:\Program Files\Google\Chrome\Application\chrome.exe" –proxy-server="http=proxy.example.com:8080;https=proxy.example.com:8080"
“`
For SOCKS5 proxies the value looks like `–proxy-server="socks5://proxy.example.com:1080"`.
3. Chrome launched this way routes through the proxy for that session only; normal Chrome launches are unaffected.
Caveats from experience: the flag is ignored if Chrome was already running, and some corporate policies lock Chrome flags out entirely. For frequent switching, Method 4 is more livable.
Method 4: SwitchyOmega (the power-user way)
The SwitchyOmega extension manages multiple proxy profiles inside Chrome and switches between them in two clicks — including per-website rules ("site X uses proxy A, everything else direct"), auto-switch patterns, and quick toggling from the toolbar. Install it from the Chrome Web Store, create a profile with your proxy's address and port, and assign it to whichever sites need it.
This is the right tool for web-scraping QA, managing several proxy endpoints, or anything where system-wide routing is overkill. One warning: an extension can proxy your traffic anywhere, so only use extensions from publishers you trust — SwitchyOmega's long track record is why it's the default recommendation.
Verify the proxy actually works
Before trusting any setup, confirm two things at browserleaks.com/ip: the IP address shown is the proxy's, and (for privacy purposes) the WebRTC section isn't leaking your real IP. If your real IP appears anywhere, the proxy isn't covering you the way you assume — that's exactly the kind of surprise better discovered by a test page than by whatever you were trying to avoid.
Choosing a proxy, and staying safe
- Datacentre vs residential: datacentre proxies are cheap and fast but easily flagged; residential proxies route through consumer IPs and are harder to block — and pricier. Oxylabs' guide to Chrome proxy setup covers the service-side options well if you're buying.
- Avoid free public proxies. Free means someone is paying — usually by inspecting your traffic, injecting ads, or harvesting logins. Never enter passwords while on a free proxy.
- HTTPS still protects passwords on modern sites even through a hostile proxy, but plain-HTTP sites get zero protection.
- At work? If your machine is managed by an organisation, its proxy policy is deliberate — overriding it can violate your employment terms, and MDM will revert your changes anyway.
For the privacy-adjacent reading, our guides on preventing common cyber attacks and using the Tor browser safely cover the heavier-duty options.
Frequently asked questions
How do I set a proxy in Google Chrome?
Chrome doesn't have its own proxy screen — it uses your operating system's. Open Chrome → Settings → System → "Open your computer's proxy settings," then configure the proxy in the Windows or macOS panel that opens (address and port for manual, or a PAC script URL for automatic). Changes apply to Chrome and other apps that use system settings. For Chrome-only proxying, use the `–proxy-server` launch flag or the SwitchyOmega extension instead.
Why does Chrome say "Open your computer's proxy settings" instead of a proxy option?
Because since 2019-era Chrome versions, the browser deliberately delegates proxy management to the OS — one setting governs Chrome, Edge, and other browsers consistently, and it prevents websites from quietly redirecting users through proxies via in-browser settings. The Chrome settings page just links you to the right OS panel. Command-line flags and extensions are the supported exceptions.
How do I use a SOCKS5 proxy in Chrome?
Set it system-wide via Windows or macOS proxy settings choosing the SOCKS option, launch Chrome with `–proxy-server="socks5://address:port"`, or configure the SOCKS profile in SwitchyOmega. SOCKS5 is protocol-agnostic (it proxies any traffic type) and is the common choice for SSH-tunnel proxies — if you tunnel over SSH with `ssh -D 1080 user@server`, point Chrome's SOCKS5 setting at `127.0.0.1:1080`.
Is using a proxy server safe?
A reputable paid proxy is reasonably safe for hiding your IP and routing traffic, but standard HTTP proxies don't encrypt anything — the proxy operator can see (and alter) your unencrypted traffic, which is why free public proxies are genuinely dangerous for logins. HTTPS sites stay encrypted end-to-end regardless of proxy. For safety-critical privacy, a VPN or Tor beats a proxy; for IP rotation and access control, a paid proxy is the right tool.
What's the difference between a proxy and a VPN in Chrome?
A proxy reroutes your browser (or system) traffic through another server, changing your visible IP, typically without encryption. A VPN encrypts all device traffic and routes it through the VPN's servers. Proxies are cheaper and per-app flexible; VPNs are the privacy tool. Many people use both: a VPN for always-on privacy, and Chrome proxy profiles (via SwitchyOmega) for specific sites that need a different location.
Related reading
I keep three SwitchyOmega profiles for testing site behaviour from different countries — tell me what you're trying to route around in the comments, and I'll tell you which method fits.
