Two kinds of browser proxy setup
Browsers either use the operating system's proxy settings or their own settings. Chrome, Edge and Safari use system settings by default. Firefox has its own, independent proxy configuration. Extensions can override both for browsers that support them.
Chrome and Edge
Chrome and Edge use the OS proxy settings. Opening their proxy settings page sends you to the system settings:
- Chrome: Settings → System → Open your computer's proxy settings.
- Edge: Settings → System and performance → Open your computer's proxy settings.
Then follow Windows proxy setup or Mac proxy setup.
Chrome with a command-line flag
To run Chrome with a specific proxy without changing system settings, launch it with a flag (using a separate profile is wise):
# macOS
open -na "Google Chrome" --args --proxy-server="http://gate.example.com:7777" --user-data-dir="/tmp/chrome-proxy"
# Windows (PowerShell)
& "C:\Program Files\Google\Chrome\Application\chrome.exe" --proxy-server="http://gate.example.com:7777" --user-data-dir="$env:TEMP\chrome-proxy"Chrome will prompt for credentials if the proxy requires them. For SOCKS5, use socks5://host:port (no authentication support).
Firefox
Firefox has its own settings:
- Open Settings and search for "proxy", then click Settings… under Network Settings.
- Choose Manual proxy configuration.
- Enter the HTTP Proxy and port, and tick Also use this proxy for HTTPS. Or enter a SOCKS Host, select SOCKS v5, and tick Proxy DNS when using SOCKS v5 to avoid DNS leaks.
- Add exceptions in No proxy for.
- Click OK.
Firefox prompts for proxy credentials and can save them. You can also choose Use system proxy settings or Automatic proxy configuration URL (PAC). See proxy PAC files.
Safari
Safari uses macOS system settings. See Mac proxy setup.
Proxy extensions
Extensions let you switch proxies quickly and route specific sites through specific proxies:
- FoxyProxy (Firefox and Chrome) is a long-standing option with pattern-based rules.
- SwitchyOmega-style extensions offer profiles and rule lists for Chromium browsers; check for maintained versions compatible with current Chrome extension standards.
Extensions are convenient but run inside the browser, so check their permissions and source.
Multiple identities
To run several proxies at once with separate cookies, use separate browser profiles or an antidetect browser.
Proxy tip: When troubleshooting, it helps to have a second, known-good proxy to compare against. A small pay-as-you-go balance from Geonode works well for that, and its dashboard shows usage and active sticky sessions. More in using Geonode in your browser.
Check for leaks
After configuring, verify:
- Your IP shows the proxy's IP.
- WebRTC doesn't reveal your real IP. See WebRTC leaks.
- DNS requests aren't leaking. See DNS leaks.
See how to check if a proxy works.
Choosing the right browser setup for your goal
| Goal | Best setup |
|---|---|
| Quick one-off check from another country | Firefox with manual proxy, or Chrome with flag and temporary profile |
| Regular switching between proxies | Proxy extension with profiles |
| Many accounts with separate identities | Antidetect browser or separate profiles per account |
| Company-wide routing rules | PAC file. See proxy PAC files |
| Automation | Puppeteer/Playwright/Selenium proxy configuration |
Firefox advanced settings worth knowing
In about:config:
| Preference | Purpose |
|---|---|
network.proxy.socks_remote_dns | Resolve DNS through SOCKS proxy |
network.proxy.allow_hijacking_localhost | Whether localhost goes through the proxy |
media.peerconnection.ice.proxy_only | Restrict WebRTC to the proxy |
network.dns.disablePrefetch | Disable DNS prefetching |
Clearing state when switching proxies
When you switch a browser from one proxy to another, cookies and site data from the previous location remain. Sites may notice the same cookie appearing from a different country. For clean checks:
- Use a private window or a fresh profile per proxy.
- Clear site data for the target domain before switching.
Edge and enterprise policies
In managed environments, administrators can set proxy configuration via group policy for Chrome and Edge, including PAC URLs and bypass lists. If your browser's proxy settings are greyed out, they're managed by policy.
For OS-level setup, see proxy setup on Windows and proxy setup on Mac.
Seeing which proxy the browser is really using
When a browser ignores your settings, or uses a proxy you didn't expect, its internal pages tell you what's actually in effect:
| Browser | Where to look | What it shows |
|---|---|---|
| Chrome | chrome://net-internals/#proxy | The effective proxy settings, with a button to re-apply them |
| Edge | edge://net-internals/#proxy | The same, for Edge |
| Chrome and Edge | chrome://policy or edge://policy | Enterprise policies, including any that set or lock proxies |
| Firefox | Settings → Network Settings | The active configuration, including "Use system proxy settings" |
| Firefox | about:policies | Enterprise policies |
| Firefox | about:networking | Open connections and DNS cache, useful for spotting direct connections |
Typical findings:
- An extension is in control. Chrome and Edge show "controlled by an extension" next to the setting; disable the extension to regain control.
- A policy is set, which explains why changes don't stick. On a managed machine, talk to IT.
- The system proxy applies, not the one you thought you'd set in the browser. Chrome and Edge use system settings unless launched with flags or an extension.
- A PAC file is in play. The effective settings show the PAC URL; test its logic with the tools in proxy PAC files.
After any change, confirm the exit IP and run a leak test, as described above. For system-level settings, see proxy setup on Windows and proxy setup on macOS.
Key takeaways
- Chrome, Edge and Safari use operating system proxy settings; Firefox has its own independent configuration.
- Chrome can run with a specific proxy via the
--proxy-serverflag and a separate profile, but can't do SOCKS5 authentication. - Firefox stores proxy credentials and supports remote DNS for SOCKS5.
- Extensions such as FoxyProxy enable rule-based switching between proxies.
- Use separate profiles or a fresh private window when switching proxies to avoid carrying cookies across locations.
- Verify with IP, WebRTC and DNS leak tests after any change. See dns leaks and proxies.
FAQ
Can I use a proxy in just one browser?
Yes: use Firefox's own settings, a Chrome command-line flag with a separate profile, or an extension.
Why does Chrome keep asking for my proxy password?
Chrome doesn't store proxy credentials as conveniently as Firefox. Use IP whitelisting or an extension that supplies credentials.
Editorial note: Proxy providers change their pools, features and prices often, so treat any figures here as typical ranges at the time of writing and confirm current terms with the provider before you buy.