The first real thing Chrome users learn about proxies is this: Chrome has no proxy setting of its own. The browser inherits the operating system's setting. In this article we show three different ways to route Chrome traffic through a proxy.
Method 1: Through the System Setting (Standard)
- In Chrome, go to the Settings > System section.
- "Open your computer's proxy settings" click that link — it takes you to the Windows/macOS network settings.
- On Windows, turn on the switch under "Manual proxy setup" and enter the IP and port you took from the list into the fields, then save.
From now on most applications on the system, Chrome included, exit through the proxy. For detailed system steps, see the Windows guide.
Method 2: Profile-Based Use with an Extension
If you want to route only Chrome — or even only certain sites — through a proxy rather than the whole system, proxy management extensions (e.g. Proxy SwitchyOmega derivatives) are the answer:
- You can define several proxy profiles and switch between them with a single click.
- You can set up domain-based rules: "this site through the proxy, the rest direct".
- SOCKS5 addresses can be defined directly through the extension — unlike with the system setting.
When choosing an extension, prefer open-source options with a large user base; a proxy extension can see all of your traffic.
Method 3: Command Line (Developers)
To launch Chrome with a specific proxy:
| Purpose | Parameter |
|---|---|
| HTTP proxy | chrome.exe --proxy-server="http://ip:port" |
| SOCKS5 proxy | chrome.exe --proxy-server="socks5://ip:port" |
| Bypass exception | --proxy-bypass-list="*.local" |
This method works with the same parameter in automation scenarios (Selenium/Puppeteer) too — details automation proxy page.
Proxies with Authentication
The username/password in paid packages is entered into the window Chrome opens on the first request. Extensions, on the other hand, can store the credentials permanently — which is more convenient in frequent use.
Verification and Troubleshooting
After setup, check it with My IP Address . If the page does not load: take the address and with the proxy checker tool test it, verify the protocol field and restart Chrome. For privacy, do not forget the WebRTC leak test either — WebRTC is enabled by default in Chrome.