People set a system-wide proxy on Windows or Mac expecting every app to route through it. Then a terminal command, a game launcher or a chat app shows their real IP. The operating system's proxy setting isn't enforced; it's published for apps to read, and each app decides whether to use it. Getting true system-wide coverage means understanding the three tiers of apps and handling each.
If you just need the click-by-click steps, see Windows proxy settings and macOS proxy settings. This post is about coverage: what each approach reaches and what it misses.
Tier 1: Apps That Follow the OS Proxy
These read the proxy you set in Windows Settings or macOS System Settings:
- Chromium-based browsers (Chrome, Edge and similar) and Safari.
- Most apps built on the platform's standard networking frameworks.
- Store apps on both platforms, in most cases.
- Firefox, only if its own setting is "Use system proxy settings".
On macOS, credentials saved in the Proxies panel are used automatically. On Windows there's no credential field, so these apps prompt on first use.
Tier 2: Apps That Read Environment Variables
Command-line tools and language runtimes generally ignore the OS setting and read HTTP_PROXY, HTTPS_PROXY and NO_PROXY instead: curl, wget, git, pip, npm, Python requests, Go programs, Docker CLI and many more. Set them for your user so every new terminal and script picks them up.
On Windows (PowerShell, applies to new processes):
[Environment]::SetEnvironmentVariable('HTTPS_PROXY', 'http://USERNAME:[email protected]:8080', 'User')
[Environment]::SetEnvironmentVariable('HTTP_PROXY', 'http://USERNAME:[email protected]:8080', 'User')
[Environment]::SetEnvironmentVariable('NO_PROXY', 'localhost,127.0.0.1', 'User')On macOS, add exports to ~/.zshrc for terminal sessions:
export HTTPS_PROXY='http://USERNAME:[email protected]:8080'
export HTTP_PROXY="$HTTPS_PROXY"
export https_proxy="$HTTPS_PROXY"
export http_proxy="$HTTPS_PROXY"
export NO_PROXY='localhost,127.0.0.1'macOS GUI apps launched from the Dock don't read ~/.zshrc. That rarely matters, since GUI apps are usually Tier 1, but it explains why an Electron app may behave differently when launched from Terminal. Some tools have their own config that overrides env vars; see git, npm and pip behind a proxy.
Tier 3: Apps That Ignore Both
Games, voice and video calling, some streaming apps, and anything using UDP generally connect directly. HTTP proxies can't carry UDP at all. For these, the only way to route traffic is at the network layer: a local client that creates a virtual network interface (often called TUN mode) and forwards all traffic to a SOCKS5 proxy. That's how you get genuinely system-wide coverage. Choose such a tool carefully, since it sees every packet, and expect UDP-heavy apps to still struggle, because many proxies only relay TCP.
PAC Files: Route Some Traffic, Not All
Often you don't want everything through the proxy, just certain sites. A PAC (proxy auto-config) file lets Tier 1 apps decide per URL:
function FindProxyForURL(url, host) {
if (dnsDomainIs(host, '.example-target.com') || host === 'example-target.com') {
return 'PROXY global.nodeproxies.xyz:8080';
}
return 'DIRECT';
}Host the file locally or on an internal server and point the OS at it: on Windows, "Use setup script" under Automatic proxy setup; on macOS, "Automatic proxy configuration" in the Proxies panel. This keeps updates, video calls and everything else off your metered proxy, which can cut your bandwidth bill dramatically.
Choose the Username for Shared Use
When many apps share one proxy, per-request rotation means your browser, email client and chat app all appear from different IPs minute to minute, which triggers security checks. Use a sticky session for system-wide setups, such as USERNAME-country-us-session-desk1-time-120, and change the id when you want a fresh IP. The trade-off is covered in static vs rotating proxies.
Verify App by App
- Browser: open our what is my IP tool in the browser you are checking.
- Terminal: run curl -s https://api.ipify.org.
- Each other app that matters: look for an "IP" or "location" readout in its settings, or check the login activity page of the service.
- Turn the proxy off and repeat to confirm the IPs change back.
Turning Everything Off Again
System-wide setups have several moving parts, and forgetting one leaves a confusing half-proxied machine. To undo fully: switch off the manual proxy or setup script in the OS settings, remove the HTTP_PROXY, HTTPS_PROXY and NO_PROXY user variables (or the exports in ~/.zshrc), clear tool-specific settings such as git's http.proxy, and stop any TUN-mode client. Then open a new terminal and confirm your real IP is back.
Using NodeProxies System-Wide
Use global.nodeproxies.xyz:8080 for the OS and env var settings, and port 1080 for SOCKS5 in a TUN-mode client. Whole-device traffic is bandwidth-hungry; if you're going all-in, the unlimited residential plan is billed by the hour instead of by the GB. Otherwise, pay-as-you-go pricing works well with a PAC file. Register to get credentials.
FAQ
Does setting a proxy in Windows route all traffic?
No. Browsers and many desktop apps follow it, but command-line tools use environment variables and some apps connect directly.
How do I make Terminal use the proxy on Mac?
Export http_proxy and https_proxy (and the uppercase versions) in ~/.zshrc. Terminal tools don't read System Settings.
Can a proxy route games and voice calls?
Not through OS proxy settings. You need a client that captures all traffic at the network layer, and UDP support on the proxy side.
