Tutorials 5 min read

How to Set Up a Proxy in Chrome on Windows and macOS (2026)

Chrome doesn't have its own proxy settings page. Here's how it actually picks up a proxy, how to set one on Windows and macOS, and how to deal with the password prompt.

If you're trying to set up a proxy in Chrome, the first surprise is that Chrome has no proxy fields of its own. On Windows and macOS it uses the operating system's proxy settings. Go to Settings, then System, and you'll find "Open your computer's proxy settings", which simply opens the OS dialog. This guide covers both operating systems, explains why Chrome keeps asking for a username and password, and shows two ways to run Chrome through a proxy without changing your whole system.

Before You Start: Which Port to Use

Use the HTTP endpoint for Chrome: global.nodeproxies.xyz on port 8080. Chrome can use SOCKS5 proxies, but it does not support SOCKS5 username and password authentication, so an authenticated SOCKS5 proxy won't work in Chrome directly. The HTTP endpoint lets Chrome prompt you for credentials. If you're unsure of the difference, see SOCKS5 vs HTTP proxies.

Keep your username and password handy. If you want a specific country or a sticky IP, add the options to the username, for example USERNAME-country-us or USERNAME-country-us-session-chrome1-time-30. The proxy username builder generates these for you.

Set Up a Proxy in Chrome on Windows 10 and 11

  1. In Chrome, open Settings, then System, and click "Open your computer's proxy settings". Or open Windows Settings, then Network & internet, then Proxy.
  2. Under Manual proxy setup, click Set up (Windows 11) or turn on "Use a proxy server" (Windows 10).
  3. Enter global.nodeproxies.xyz as the address and 8080 as the port.
  4. Optionally add addresses that should bypass the proxy, such as localhost and your local network, then save.
  5. Restart Chrome and load any page. Chrome shows a sign-in dialog for the proxy. Enter your proxy username (with options) and password.

Note that this is a system-wide setting. Edge and other apps that follow Windows proxy settings will also route through the proxy, and each may ask for credentials.

Set Up a Proxy in Chrome on macOS

  1. In Chrome, open Settings, then System, and click "Open your computer's proxy settings". Or open System Settings, then Network, select your active connection (Wi-Fi or Ethernet) and click Details.
  2. Open the Proxies tab.
  3. Turn on Web proxy (HTTP) and Secure web proxy (HTTPS). For each, enter global.nodeproxies.xyz as the server and 8080 as the port.
  4. You can turn on "Proxy server requires password" and enter your credentials. macOS stores them in the Keychain, but Chrome may still show its own sign-in prompt.
  5. Click OK, restart Chrome and enter the proxy credentials when prompted.

On Linux, Chrome follows the desktop environment's proxy settings on GNOME and KDE; otherwise use the command-line flag described below.

Why Chrome Can't Save the Proxy Username and Password

Neither the Windows proxy dialog nor Chrome's own settings have a place for proxy credentials that Chrome reads automatically. When the proxy answers with 407 Proxy Authentication Required, Chrome shows a sign-in dialog. Chrome may remember what you enter for the rest of the browsing session, but you'll often see the prompt again after restarting the browser. You also can't put credentials in the address, because Chrome ignores user:pass in proxy server settings.

That's fine for occasional manual use. For anything you do repeatedly, there are two better options.

Option 1: A Proxy Extension

Chrome extensions can set a proxy for the browser only, using the chrome.proxy API, and answer the authentication challenge automatically. Proxy manager extensions use this to store a username and password and switch proxies without touching system settings. Choose a well-reviewed extension with a clear privacy policy, since it can see your proxy credentials and all the hosts you visit. Configure it with HTTP, global.nodeproxies.xyz, port 8080, and your username and password.

Option 2: The --proxy-server Launch Flag

You can start a separate Chrome instance that uses a proxy, leaving your normal browser and system settings untouched. Use a separate profile directory, because if Chrome is already running with the same profile, the new window joins the existing process and the flag is ignored.

# macOS
open -na "Google Chrome" --args --proxy-server="http://global.nodeproxies.xyz:8080" --user-data-dir="$HOME/chrome-proxy-profile"

# Windows (Command Prompt)
"C:\Program Files\Google\Chrome\Application\chrome.exe" --proxy-server="http://global.nodeproxies.xyz:8080" --user-data-dir="%USERPROFILE%\chrome-proxy-profile"

# Linux
google-chrome --proxy-server="http://global.nodeproxies.xyz:8080" --user-data-dir="$HOME/chrome-proxy-profile"

The flag doesn't accept credentials, so Chrome still prompts for them on the first page. For automated browsers, tools like Puppeteer and Playwright pass credentials programmatically; see our Node.js and Puppeteer guide and the Playwright guide.

Verify the Proxy Is Working

Once Chrome is connected, open our what is my IP tool in that browser. You should see the proxy's IP and country, not your own. If you used a country option, check that it matches. If you see your real IP, Chrome isn't using the proxy: confirm the settings were saved, restart Chrome fully, and make sure no extension is overriding the system proxy.

Without a session option, the IP can change between requests, which some sites don't like mid-visit. For normal browsing, add a sticky session to the username, such as USERNAME-session-chrome1-time-30, so the IP stays the same for 30 minutes. For a deeper check, see how to test if a proxy is working.

Troubleshooting

  • The sign-in prompt keeps reappearing: the credentials are being rejected. Check for typos, and make sure options like -country-us are in the username, not the password.
  • ERR_PROXY_CONNECTION_FAILED: Chrome can't reach the proxy. Check the host and port, and whether a firewall or VPN is blocking outbound connections.
  • ERR_TUNNEL_CONNECTION_FAILED: the proxy refused the tunnel. On NodeProxies this usually means the plan is inactive or out of bandwidth.
  • Pages load but the IP is yours: another proxy setting (an extension or a PAC script) is taking priority.

Getting a Proxy for Chrome From NodeProxies

Register, buy a small plan (from 100 MB, minimum deposit $3) and copy your credentials from the dashboard's proxy generator. For browsing, residential proxies with a sticky session look like a normal home connection; for social apps, mobile proxies are an option. No ID verification is required, and you can pay by card or crypto.

FAQ

Does Chrome have its own proxy settings?

No. On Windows and macOS, Chrome uses the system proxy settings. To use a proxy only in Chrome, use a proxy extension or launch Chrome with the --proxy-server flag.

How do I enter a proxy username and password in Chrome?

Chrome asks for them in a sign-in dialog when the proxy requests authentication. To avoid the prompt, use an extension that handles proxy authentication.

Can I use a SOCKS5 proxy with a password in Chrome?

Not directly. Chrome doesn't support SOCKS5 authentication, so use the HTTP endpoint on port 8080 instead.

How do I turn the proxy off in Chrome?

Disable the manual proxy in your OS network settings, or close the Chrome instance you started with --proxy-server. Your normal profile is unaffected by the flag.

NodeProxies

Ready to get started?

90M+ residential, mobile & datacenter proxies. Datacenter from $0.30/GB, residential from $0.42/GB. No contracts.

Create free account