How to Set Up a Proxy in Chrome (Every Method That Actually Works)

The most common question we get about Chrome and proxies starts with a wrong assumption: "where is Chrome's proxy setting?" Chrome has not had its own proxy panel for years. The button in its settings simply hands you off to your operating system, which changes the proxy for everything on the machine, not just the browser.

That surprises people, and it matters, because "set a proxy in Chrome" almost always really means "route only this browser through a proxy." This guide covers the four methods that actually do that, from the quick-and-dirty to the way power users run whole fleets of separately-proxied Chrome windows.

How do you set up a proxy in Chrome?

Chrome has no proxy panel of its own, so you have four options: change your system proxy settings (this affects the whole computer), install a proxy extension like FoxyProxy (Chrome only, the usual pick), launch Chrome with a --proxy-server flag, or run an isolated profile with its own proxy. Pick by how often you switch and how many proxies you need at once.

First, understand what Chrome actually does

Chrome delegates proxying to the system by default. On Windows it opens the Windows proxy settings; on macOS it opens Network preferences. Set a proxy there and Chrome uses it, but so does every other app, from your email client to background updaters. That is the opposite of what most people want, and it is why the built-in path is the least useful of the four.

The useful methods isolate the proxy to Chrome (or to one Chrome profile). Pick based on how often you switch and whether you need more than one proxy at once.

Method 1: Chrome proxy via system settings

Use this only when you genuinely want the whole computer on one proxy.

1. Open Chrome settings, search "proxy," and click Open your computer's proxy settings.
2. Windows: under Manual proxy setup, turn on Use a proxy server, enter the IP and port, save. macOS: in Network > Details > Proxies, tick the proxy type (Web/HTTP, Secure/HTTPS, or SOCKS), enter the address and port, apply.
3. Load an IP-check page to confirm your visible IP changed.

The catch beyond "it affects everything": the built-in system dialogs are awkward with authenticated proxies and often will not prompt for SOCKS credentials at all. For anything you switch regularly, or any proxy with a username and password, skip straight to an extension.

Method 2: a Chrome proxy extension (best for most people)

A proxy-manager extension is the right answer for almost everyone. It routes only Chrome, switches proxies in two clicks, and handles credentials that the system dialog fumbles. The two standard choices are FoxyProxy (we have a full FoxyProxy setup guide) and Proxy SwitchyOmega.

1. Install the extension from the Chrome Web Store.
2. Open its options and add a proxy: type (HTTP or SOCKS5), host, port, and username/password if the proxy needs them.
3. Click the toolbar icon and select your proxy to turn it on; select Direct/Off to turn it back off.

The reason this beats the built-in path is control. You can save many proxies and switch between them instantly, and better extensions support pattern rules, meaning you can send only certain sites through the proxy and everything else direct. That is invaluable when you want, say, one region's storefront proxied while the rest of your browsing stays local.

A caution that applies to any extension: it can see your browsing. Install only well-known, well-reviewed proxy extensions, and be as careful about a random proxy extension as you would be about a random free proxy.

Method 3: the command-line flag (developers, automation)

Chrome accepts a --proxy-server flag at launch, which proxies that Chrome instance without touching your system settings. This is the cleanest method for testing and automation.

# macOS
open -a "Google Chrome" --args --proxy-server="http://203.0.113.7:8080"

# Windows (from Command Prompt / PowerShell)
"C:\Program Files\Google\Chrome\Application\chrome.exe" --proxy-server="http://203.0.113.7:8080"

# Linux
google-chrome --proxy-server="http://203.0.113.7:8080"

For a SOCKS5 proxy, change the scheme:

google-chrome --proxy-server="socks5://198.51.100.42:1080"

Two important limitations. First, if the running Chrome already has windows open, a new launch may just add a tab to the existing process and ignore the flag. Pair the flag with a fresh profile directory (Method 4) to guarantee it takes effect. Second, --proxy-server does not carry a username and password. For authenticated proxies, use an IP-allowlisted proxy, an extension, or a local forwarder that injects the credentials. Grab a no-auth proxy to test the flag from our free API:

curl "https://hproxy.com/api/proxy-list?format=txt&recent=true&limit=1"

Method 4: a separate, isolated Chrome profile

This is how people run several differently-proxied Chrome windows side by side, one per project, account or region, each fully isolated (separate cookies, cache and session).

google-chrome \
  --user-data-dir="/tmp/chrome-proxy-a" \
  --proxy-server="socks5://198.51.100.42:1080"

--user-data-dir points Chrome at a brand-new profile folder, so this window shares nothing with your normal browsing and its proxy flag is guaranteed to apply. Launch a second one with a different directory and a different proxy, and you have two isolated, independently-proxied browsers open at once. This is the poor-man's version of an antidetect browser, and for many tasks it is enough.

One real limitation: isolating cookies and IPs is not full anti-fingerprinting. The profiles still share fonts, screen size and other traits a determined site can read. For serious multi-account work people layer a dedicated antidetect browser on top of good residential proxies, but for testing and light separation, isolated profiles do the job for free.

Confirm the proxy is working in Chrome

Whatever method you choose, confirm it before trusting it. The 20-second check:

1. Load an IP-echo page (search "what is my IP") and note the address.
2. Enable the proxy.
3. Reload. The IP should now be the proxy's exit address, not yours.

If the IP did not change, the proxy is not engaged (or it is dead, which with free proxies is the usual explanation). For a fuller picture, our proxy checker reports a proxy's real exit IP, its anonymity grade and its speed, so you know not just that it works but whether it actually hides you. And if you want a live proxy to practice any of these methods with right now, the free proxy list has verified HTTP and SOCKS5 entries updated every few minutes.

Once Chrome is proxied the way you want, the same logic extends everywhere else: the cURL guide covers the command-line side, and the SOCKS5 explainer covers when to reach for SOCKS over HTTP in the first place.