How to Set Up a Proxy in Chrome — 3 Methods (2026 Guide)

How Chrome Handles Proxies

Unlike Firefox, Chrome does not have its own proxy settings. Instead, Chrome relies on your operating system's proxy configuration. This means changing Chrome's proxy settings affects all apps on your system that use the default system proxy.

There are three ways to route Chrome traffic through a proxy:

1. System proxy settings — Built-in, affects all system traffic
2. Browser extensions — Proxy management within Chrome only
3. Command-line flags — Launch Chrome with a specific proxy

Each method has trade-offs. We'll walk through all three so you can pick the best fit.

Method 1: System Proxy Settings

This is the most straightforward method. You configure the proxy at the OS level, and Chrome automatically uses it.

Windows 11/10

1. Open Chrome and go to Settings > System > Open your computer's proxy settings (Or go directly: Settings > Network & Internet > Proxy)
2. Under Manual proxy setup, click Set up
3. Toggle Use a proxy server to On
4. Enter the details:

Proxy IP address:  198.51.100.42
Port:              8080

1. Optionally add addresses to bypass the proxy:

localhost;127.0.0.1;*.local

1. Click Save
2. Restart Chrome

macOS

1. Open System Preferences > Network
2. Select your active connection (Wi-Fi or Ethernet)
3. Click Advanced > Proxies
4. Check Web Proxy (HTTP) and/or Secure Web Proxy (HTTPS)
5. Enter the proxy server and port
6. Click OK, then Apply
7. Restart Chrome

Linux (GNOME)

1. Open Settings > Network > Network Proxy
2. Select Manual
3. Enter the HTTP and HTTPS proxy details:

HTTP Proxy:   198.51.100.42  Port: 8080
HTTPS Proxy:  198.51.100.42  Port: 8080
SOCKS Host:   198.51.100.42  Port: 1080

1. Close settings and restart Chrome

Verifying the System Proxy

After configuring, visit our homepage in Chrome to check your IP address. If it matches the proxy's IP, the configuration is working.

Use the Proxy Checker tool to verify your proxy is online before configuring it.

Drawbacks of System Proxy

• Affects all applications, not just Chrome
• No quick toggle — you must go back to settings to enable/disable
• One proxy at a time — cannot use different proxies for different tabs or sites
• No SOCKS5 on Windows — Windows system proxy settings only support HTTP/HTTPS

Method 2: Browser Extensions (Recommended)

Extensions let you manage proxies directly within Chrome without affecting other applications. They also offer features like quick switching, per-site rules, and proxy lists.

FoxyProxy Standard

FoxyProxy is one of the most popular proxy extensions, available for both Chrome and Firefox.

Installation:

1. Go to the Chrome Web Store and search for FoxyProxy Standard
2. Click Add to Chrome
3. Click the FoxyProxy icon in the toolbar
4. Go to Options

Adding a Proxy:

1. Click Add New Proxy
2. Fill in the proxy details:

Title:    My SOCKS5 Proxy
Type:     SOCKS5
IP:       203.0.113.50
Port:     1080
Username: (optional)
Password: (optional)

1. Click Save

Using the Proxy:

• Click the FoxyProxy icon in the toolbar
• Select your proxy from the dropdown
• To disable, select Disable FoxyProxy

Pattern-Based Routing:

FoxyProxy lets you route specific URLs through different proxies:

1. Add a URL pattern (e.g., *.netflix.com/*)
2. Assign it to a specific proxy
3. All matching URLs use that proxy; everything else goes direct

Proxy SwitchyOmega

SwitchyOmega is a powerful proxy manager with profile-based switching.

Installation:

1. Install from the Chrome Web Store: Proxy SwitchyOmega
2. Click the extension icon > Options

Creating a Proxy Profile:

1. Click New Profile on the left sidebar
2. Name it (e.g., "US SOCKS5") and select Proxy Profile
3. Set the protocol and server:

Protocol:  SOCKS5
Server:    203.0.113.50
Port:      1080

1. Click Apply Changes

Auto Switch Mode:

SwitchyOmega's killer feature is Auto Switch, which lets you create rules:

Rule List:
  *.netflix.com     →  US Proxy Profile
  *.bbc.co.uk       →  UK Proxy Profile
  (Default)         →  Direct Connection

This is particularly useful when you need different proxies for different sites.

Quick Switching:

Click the SwitchyOmega icon in Chrome's toolbar to instantly switch between profiles or toggle auto-switch mode.

Extension Comparison

Feature	FoxyProxy	SwitchyOmega
SOCKS5 support	Yes	Yes
SOCKS4 support	Yes	Yes
HTTP/HTTPS	Yes	Yes
URL pattern routing	Yes	Yes
Auto-switch profiles	Basic	Advanced
PAC script support	No	Yes
Import/Export	Yes	Yes
Ease of use	Simpler	More powerful

Method 3: Command-Line Flags

You can launch Chrome with a proxy by passing command-line arguments. This is useful for automation, testing, or running a separate Chrome instance with a proxy.

Windows

Open Command Prompt or PowerShell and run:

"C:\Program Files\Google\Chrome\Application\chrome.exe" --proxy-server="socks5://203.0.113.50:1080"

macOS

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --proxy-server="socks5://203.0.113.50:1080"

Linux

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

Supported Proxy Formats

# HTTP proxy
--proxy-server="http://198.51.100.42:8080"

# HTTPS proxy
--proxy-server="https://198.51.100.42:8080"

# SOCKS5 proxy
--proxy-server="socks5://203.0.113.50:1080"

# SOCKS4 proxy
--proxy-server="socks4://203.0.113.50:1080"

Proxy Bypass List

To exclude certain addresses from the proxy:

google-chrome --proxy-server="socks5://203.0.113.50:1080" --proxy-bypass-list="localhost;127.0.0.1;*.local"

Running Multiple Chrome Instances

To run a proxied Chrome alongside your regular Chrome, use a separate user data directory:

google-chrome --proxy-server="socks5://203.0.113.50:1080" --user-data-dir="/tmp/chrome-proxy-profile"

This creates an isolated Chrome instance with its own cookies, history, and extensions — and its own proxy.

Preventing DNS Leaks with SOCKS5

When using SOCKS5 via command line, add the --host-resolver-rules flag to prevent DNS leaks:

google-chrome --proxy-server="socks5://203.0.113.50:1080" --host-resolver-rules="MAP * ~NOTFOUND, EXCLUDE 203.0.113.50"

This forces Chrome to resolve DNS through the SOCKS5 proxy instead of your local DNS server.

Which Method Should You Choose?

Use Case	Recommended Method
Quick one-time use	Command-line flag
Daily browsing with proxy	Browser extension
Corporate/work proxy	System settings
Multiple proxies for different sites	SwitchyOmega
Automation and testing	Command-line flag
Sharing proxy config across apps	System settings

Troubleshooting Chrome Proxy Issues

ERR_PROXY_CONNECTION_FAILED

The proxy server is unreachable. Verify the proxy is online using our Proxy Checker and double-check the IP and port.

ERR_TUNNEL_CONNECTION_FAILED

This occurs when the proxy rejects the CONNECT request (used for HTTPS). Try a different proxy or check if the proxy supports HTTPS tunneling.

Websites Load Slowly

• The proxy may be overloaded or far away
• Try a proxy with lower latency
• Check if the proxy is throttling bandwidth

Chrome Ignores Extension Proxy

If Chrome seems to bypass the extension's proxy: - Check that no system-level proxy is configured (it takes priority) - Verify the extension has the necessary permissions - Restart Chrome after changing extension settings

For setting up proxies in Firefox (which has its own native proxy settings), see our companion guide: How to Set Up a Proxy in Firefox.

Conclusion

Chrome offers three practical methods for proxy configuration. Browser extensions like SwitchyOmega give you the most flexibility and control without affecting other applications. System settings work best for organization-wide proxies. Command-line flags are perfect for developers and automation.

Start by testing your proxy with our Proxy Checker, then pick the method that fits your workflow. For most users, SwitchyOmega or FoxyProxy provides the best balance of power and convenience.