This guide covers three reliable ways to use a proxy in Google Chrome: inherit your system proxy, launch Chrome with proxy flags, or use a proxy extension. We also explain PAC auto‑config and common troubleshooting tips.
Chrome on Windows/macOS typically inherits system proxy settings. If you’ve configured a proxy system‑wide, Chrome will route through it. For per‑browser control, use launch flags or a dedicated extension.
Configure your OS proxy:
Chrome respects PAC auto‑config if set at the OS level.
Start Chrome with explicit proxy settings:
# macOS
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
--proxy-server="http://HOST:PORT"
# Windows (PowerShell)
Start-Process "C:\Program Files\Google\Chrome\Application\chrome.exe" `
-ArgumentList '--proxy-server="http://HOST:PORT"'
# Linux
google-chrome --proxy-server="http://HOST:PORT"
# macOS
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
--proxy-server="socks5://HOST:PORT"
# Windows (PowerShell)
Start-Process "C:\Program Files\Google\Chrome\Application\chrome.exe" `
-ArgumentList '--proxy-server="socks5://HOST:PORT"'
# Linux
google-chrome --proxy-server="socks5://HOST:PORT"
# Use a PAC URL
google-chrome --proxy-pac-url="https://example.com/proxy.pac"
# Combine with direct fallback rules inside PAC as needed
You can create a separate shortcut/script to launch Chrome with proxy settings when needed.
Extensions offer per‑site rules, quick toggles, and profile‑based setups. Search the Chrome Web Store for trusted proxy managers. Configure your server host, port, protocol, and authentication if required.
Extensions operate only inside Chrome and do not affect other applications.
Ensure the flag syntax is exact and no quotes are mismatched. On macOS, launch the binary path directly; on Windows, use PowerShell Start‑Process.
Remove proxy flags from your shortcut/script, disable the extension, or revert OS proxy settings to Off.