How to Set Up a Proxy in Google Chrome: Windows, Mac, Linux, Mobile (2026)

Chrome has no built-in proxy configuration panel of its own — it delegates entirely to your operating system's network settings, or to an extension/command-line flag if you want a proxy scoped to Chrome only. This guide covers every method across every platform: system-level setup on Windows, macOS, and Linux; per-instance command-line flags; extensions; mobile Wi-Fi proxy configuration; the SOCKS5 authentication caveat that trips up many users; and a complete troubleshooting reference.

⚡ Key Takeaways

  • Chrome's "proxy settings" menu item simply opens your OS network settings — Chrome has no independent configuration of its own.[1]
  • Setting a proxy through system settings applies it to all apps, not just Chrome. For Chrome-only routing, use the --proxy-server launch flag or an extension.[1]
  • Chrome does not support SOCKS5 authentication prompts — HTTP/HTTPS proxies prompt for credentials automatically; SOCKS5 proxies with auth require a workaround.[2]
  • On Linux, Chrome reads your desktop environment's network settings (GNOME, KDE) rather than a separate config — or respects http_proxy/https_proxy environment variables when launched from a terminal.[1]
  • Chrome for mobile (Android/iOS) has no in-browser proxy settings at all — configuration happens entirely through the phone's Wi-Fi network settings.[3]
  • Always verify with an IP-checker site after setup — a misconfigured proxy fails silently rather than throwing an error.

The Key Fact: Chrome Has No Proxy Settings of Its Own

This is the single most important thing to understand before attempting any Chrome proxy setup: Chrome does not have an independent proxy configuration panel. When you navigate to Chrome's settings and click anything related to "proxy," it simply opens your operating system's network proxy settings — Windows Settings, macOS Network Preferences, or your Linux desktop environment's network panel.[4]

This has a direct practical consequence: any proxy you configure this way applies to your entire system — every app, not just Chrome. If you only want Chrome's traffic routed through a proxy while leaving other apps on your regular connection, you need one of the two Chrome-specific methods covered later: the --proxy-server command-line flag, or a browser extension.

3 Methods to Set a Proxy in Chrome

⚙️ System Settings

~3 minutes

Opens your OS's network proxy panel. Applies to all apps on your device, not just Chrome. The default, most universal method — works identically regardless of which browser you ultimately use.

🧩 Browser Extension

~2 minutes

Extensions like Proxy SwitchyOmega let you save multiple proxy profiles and switch between them with one click, scoped to Chrome only. The most convenient method if you switch proxies frequently.[5]

💻 Command-Line Flag

~1 minute

Launch Chrome with --proxy-server=host:port to apply a proxy to that single Chrome instance only — without touching system settings or installing anything. Best for scripted/automated launches.

Setting Up a Proxy in Chrome on Windows 10/11

🪟
Windows 10/11 — System Settings Method
Applies to all apps, not just Chrome
  1. Open Chrome and click the three-dot menu (⋮) in the top-right corner.
  2. Select Settings.
  3. In the left sidebar, click System.
  4. Click Open your computer's proxy settings — this opens Windows' native proxy panel.[4]
  5. Under Manual proxy setup, toggle Use a proxy server to On.
  6. Enter the proxy's IP address/hostname and Port provided by your proxy service.
  7. Click Save.
💡 The first time you visit a webpage after enabling an HTTP/HTTPS proxy with authentication, Windows will prompt you for your proxy username and password directly in the browser.

Setting Up a Proxy in Chrome on macOS

🍎
macOS — System Settings Method
Per-protocol configuration (HTTP, HTTPS, SOCKS)
  1. Open Chrome and click the three-dot menu (⋮) in the top-right corner.
  2. Select SettingsSystemOpen your computer's proxy settings.
  3. macOS opens the Network preferences for your active connection (Wi-Fi or Ethernet).
  4. Click Details…, then the Proxies tab.
  5. Select the protocol you want to configure — Web Proxy (HTTP), Secure Web Proxy (HTTPS), or SOCKS Proxy — and check its box.
  6. Enter the server address and port.
  7. If your proxy requires authentication, check Proxy server requires password and enter your credentials.
  8. Click OK, then Apply.
💡 Unlike Windows, macOS lets you configure HTTP, HTTPS, and SOCKS proxies independently and simultaneously — useful if different traffic types need to route through different proxy endpoints.

Setting Up a Proxy in Chrome on Linux

🐧
Linux — Desktop Environment or Environment Variables
No standalone Linux network panel — Chrome reads your DE's settings
  1. On GNOME: open Settings → Network → Network Proxy, set the mode to Manual, and enter the host and port for each protocol (HTTP, HTTPS, FTP, SOCKS).[1]
  2. On KDE or other DEs: the path varies, but Chrome always reads whatever the desktop environment's network settings module reports.
  3. Via terminal launch: Chrome respects the http_proxy, https_proxy, and no_proxy environment variables when launched from a terminal session that has them set.
# Set proxy environment variables before launching Chrome from terminal
export http_proxy="http://username:password@proxy.example.com:8080"
export https_proxy="http://username:password@proxy.example.com:8080"
export no_proxy="localhost,127.0.0.1"
google-chrome

Method 2: Using a Chrome Proxy Extension

If you switch between proxies frequently, an extension is far more convenient than re-opening system settings every time. Proxy SwitchyOmega is the most widely used option, with millions of installs, letting you save multiple named proxy profiles and switch between them with a single click.[5]

  1. Install Proxy SwitchyOmega (or your proxy provider's own extension, if they offer one) from the Chrome Web Store.
  2. Pin the extension icon to your toolbar for easy access.
  3. Open the extension and create a new proxy profile — enter the server address, port, protocol, and credentials.
  4. Save the profile, then click the extension icon and select it to activate.
  5. Repeat for additional proxies — switching between saved profiles takes one click.
💡 Provider-specific extensions: Many commercial proxy providers (Nstproxy, Webshare, NodeMaven) offer their own Chrome extension that pulls your proxy credentials directly from your dashboard — eliminating manual entry and showing a connection-status indicator (commonly a green/red dot) directly in the toolbar.[6]

Method 3: Command-Line Flag (Per-Instance Proxy)

The --proxy-server flag applies a proxy to a single Chrome launch only — it does not touch system settings and does not persist after you close that Chrome instance. This is the cleanest method for scripted automation, testing, or any case where you want a temporary, isolated proxy session.[1]

# Windows — Command Prompt (close all Chrome windows first)
"C:\Program Files\Google\Chrome\Application\chrome.exe" --proxy-server="http://proxy.example.com:8080"

# macOS — Terminal
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
  --proxy-server="http://proxy.example.com:8080"

# Linux — Terminal
google-chrome --proxy-server="http://proxy.example.com:8080"

# With SOCKS5 protocol
google-chrome --proxy-server="socks5://proxy.example.com:1080"

# Bypass the proxy for specific hosts
google-chrome --proxy-server="http://proxy.example.com:8080" \
  --proxy-bypass-list="*.internal.company.com;localhost"
⚠️ Close all existing Chrome windows first. If Chrome is already running, the flag has no effect — Chrome attaches new windows to the existing process rather than launching a fresh instance with the new flag applied. Fully quit Chrome before running the command.

Setting Up a Proxy for Chrome on Android & iOS

Chrome's mobile apps have no built-in proxy settings of their own at all. Configuration happens entirely at the device's Wi-Fi network level — and because it's a network-level setting, it affects every app on the device, not just Chrome.[3]

🤖
Android
Wi-Fi only — no cellular proxy support via user settings
  1. Open Settings → Wi-Fi.
  2. Tap and hold your connected network, then select Modify network.
  3. Tap Advanced options.
  4. Under Proxy, select Manual.
  5. Enter the proxy server's IP address and port.
  6. Tap Save.
📱
iOS
Wi-Fi only — same as the general iPhone proxy setup
  1. Open Settings → Wi-Fi.
  2. Tap the (i) icon next to your connected network.
  3. Scroll to HTTP Proxy and select Manual.
  4. Enter the Server address and Port.
  5. Tap Save.

The SOCKS5 Authentication Caveat

⚠️ Chrome does not support SOCKS authentication prompts. While HTTP/HTTPS proxy authorization prompts appear automatically as soon as Chrome tries to load a webpage, Chrome has no equivalent built-in prompt for SOCKS5 proxies that require a username and password.[2]

If your proxy provider only offers SOCKS5 with authentication, you have three options: (1) use the provider's HTTP/HTTPS endpoint instead, if one is offered, since those prompt for credentials natively; (2) use a Chrome extension that handles SOCKS5 authentication internally (most major proxy provider extensions do this); or (3) configure IP whitelisting with your provider instead of username/password authentication, removing the need for any credential prompt entirely.

How to Verify Your Chrome Proxy Is Working

A misconfigured proxy in Chrome typically fails silently or simply doesn't apply — it rarely throws a clear error. Always verify before relying on it:

  1. Open a new tab and visit an IP-checking site such as whatismyipaddress.com or ipinfo.io.
  2. Confirm the displayed IP address matches your proxy's IP — not your real ISP-assigned address.
  3. If using a proxy with geo-targeting, confirm the displayed location matches the country/city you configured.
  4. If the proxy requires credentials and Chrome doesn't prompt you, the proxy likely isn't applying — recheck your configuration.

Troubleshooting Common Chrome Proxy Errors

Error / SymptomLikely CauseFix
Unable to connect to the proxy Wrong IP/port, proxy server offline, or firewall blocking the port Double-check the address and port against your provider dashboard. Test the same proxy with curl -x http://host:port https://ipinfo.io/ip from a terminal to isolate whether it's a Chrome issue or a proxy issue.
No credential prompt appears Using SOCKS5 with auth (unsupported), or proxy not actually applied Switch to HTTP/HTTPS protocol if available, use a proxy extension, or verify the proxy settings were saved correctly in system settings.
IP not changing after setup --proxy-server flag ignored because Chrome was already running Fully quit all Chrome windows and processes, then relaunch with the flag. On Windows, check Task Manager for lingering chrome.exe processes.
Target site blocks/CAPTCHAs immediately Proxy IP is connecting fine but has poor reputation (datacenter/shared/flagged) Switch to a residential proxy with clean IP history — the connection working and the IP being trusted by the target are two separate problems.
Settings keep reverting Corporate policy or another app/extension overwriting system proxy settings Check Chrome's managed policies page (chrome://policy) for organisation-enforced proxy settings that override manual configuration.

How to Disable the Proxy in Chrome

Reversing the setup is symmetric to enabling it — go back to the same settings panel and turn it off:

  • Windows: Settings → System → Open your computer's proxy settings → toggle Use a proxy server to Off → Save.
  • macOS: System Settings → Network → Details → Proxies tab → uncheck every protocol you had enabled (Web Proxy, Secure Web Proxy, SOCKS) → OK → Apply.
  • Linux: Set the Network Proxy mode back to Off in your desktop environment's settings, or unset the http_proxy/https_proxy environment variables.
  • Extension: Open the extension and switch the active profile back to "Direct" or "No proxy."
  • Mobile: Wi-Fi settings → your network → change Proxy from Manual back to None (Android) or Off (iOS).

Get Clean Residential Proxy Credentials for Chrome

Nstproxy's 110M+ residential IPs work with all three Chrome setup methods — system settings, extensions, or the --proxy-server flag — with HTTP, HTTPS, and SOCKS5 support from one dashboard.

Try Nstproxy for Free →

FAQ

Q: Does Chrome have its own proxy settings?

No. Chrome has no independent proxy configuration panel — clicking any proxy-related option in Chrome's settings simply opens your operating system's network proxy settings (Windows, macOS, or your Linux desktop environment). Any proxy you configure this way applies to your entire system, not just Chrome. To scope a proxy to Chrome only, use the --proxy-server command-line flag or a browser extension instead.

Q: How do I set a proxy for only Chrome, not my whole computer?

Two methods: launch Chrome with --proxy-server="host:port" from the command line (after fully closing any existing Chrome windows), or install a Chrome extension like Proxy SwitchyOmega that manages proxy profiles entirely within the browser, without touching system-wide settings.

Q: Why doesn't Chrome ask for my SOCKS5 proxy password?

Chrome does not support authentication prompts for SOCKS5 proxies — only HTTP/HTTPS proxies trigger an automatic credential prompt when you load a webpage. If your proxy is SOCKS5 with required authentication, use the provider's HTTP/HTTPS endpoint instead if available, use a proxy extension that handles SOCKS5 auth internally, or switch to IP whitelisting with your provider so no credentials are needed at all.

Q: Can I set up a proxy in Chrome on my phone?

Chrome's mobile apps (Android and iOS) have no in-browser proxy settings. Configuration happens entirely through your phone's Wi-Fi network settings — Settings → Wi-Fi → modify your network → set Proxy to Manual and enter the server address and port. This applies to all apps using that Wi-Fi network, not just Chrome, and only works on Wi-Fi — cellular data proxy is controlled by your carrier, not user settings.

Q: How do I know if my Chrome proxy is actually working?

Open a new tab and visit an IP-checking site like whatismyipaddress.com or ipinfo.io. If the proxy is active and configured correctly, the displayed IP address and location should match your proxy server's details, not your real ISP-assigned IP. A misconfigured proxy typically fails silently rather than showing an error, so this verification step is essential after every setup or change.

Further Reading