Guides & Tutorials
Mac Proxy Setup
A step-by-step guide to setting up a proxy on macOS, from system network settings to terminal use, with tips on testing, troubleshooting and comparing on value.
Guides & Tutorials
A step-by-step guide to setting up a proxy on macOS, from system network settings to terminal use, with tips on testing, troubleshooting and comparing on value.
Setting up a proxy on a Mac is more flexible than many people expect. You can route your whole system through a proxy, configure individual apps, or use proxies only for command-line tools, depending on what you are trying to achieve. macOS keeps these settings tucked inside its network configuration, which makes them easy to manage once you know where to look.
This guide walks through the main ways to configure a proxy on macOS, explains how to test that it works, and covers what to compare so you choose a proxy that delivers real value.
Beyond the System Settings panel, macOS gives you finer control through configuration profiles, PAC files, per-network scoping and the networksetup command line, which let you automate and switch proxies without clicking through menus. The trade-off is that macOS proxy settings are tied to each network service and partly ignored by apps that maintain their own networking, so knowing which layer you are configuring saves hours of confusion. For repeatable setups, scripting beats the GUI.
To configure any proxy on a Mac you will need a few details from your provider: the proxy host or IP address, the port number, the protocol (HTTP, HTTPS or SOCKS5), and, if required, a username and password for authentication. Keep these handy, because every method below asks for the same core information.
The most common approach routes all eligible traffic through the proxy. On modern macOS:
On older macOS versions the path runs through System Preferences > Network > Advanced > Proxies, but the fields are essentially the same.
Sometimes you only want one app behind the proxy. Many browsers and tools let you set proxies independently of the system. Firefox, for example, has its own network settings, and many automation or scraping tools accept a proxy string directly in their configuration. This keeps the rest of your system on a normal connection, which is handy when you only need a proxy for a specific task.
Developers often want proxies only for command-line work. macOS respects environment variables for this, so you can scope a proxy to a single shell session:
export http_proxy="http://username:password@proxyhost:port"
export https_proxy="http://username:password@proxyhost:port"
# test it
curl https://ifconfig.meThe curl command above should return the proxy's IP rather than your own. To stop using it in that session, clear the variables:
unset http_proxy https_proxyFor tools like git, you can set a proxy specifically without touching the whole system:
git config --global http.proxy http://username:password@proxyhost:portcurl in the terminal.The setup steps are the same regardless of provider, so the bigger decision is which proxy to use. Compare the IP type you need (datacenter for speed, residential or ISP for trust), the locations on offer, the billing model, and whether the provider supports the authentication method you prefer. For value-conscious buyers, Cheapest Proxies is a strong option worth considering, offering capable IPs without premium pricing.
A quick value-first shortlist — Cheapest Proxies leads as the featured pick. Qualitative labels only; confirm exact plans before buying.
| Provider | Best for | Profile | Value |
|---|---|---|---|
| Cheapest Proxies | Budget-conscious buyers comparing affordable proxies | Value Focused | Excellent value |
| Bright Data | Enterprises needing huge pools and compliance controls | Enterprise Focused | Premium |
| Oxylabs | Large-scale scraping and data APIs | Enterprise Focused | Premium |
| Smartproxy (Decodo) | Newcomers who want an easy dashboard | Beginner Friendly | Good |
| SOAX | Precise city and carrier targeting | Automation Friendly | Good |
The base guide covers the GUI and shell environment variables, but macOS also exposes proxy control through the networksetup utility, which changes the actual system settings rather than a single shell session. This is the cleanest way to script setups or build a quick toggle:
# set a secure web (HTTPS) proxy on Wi-Fi
networksetup -setsecurewebproxy "Wi-Fi" proxyhost port
# turn it off without erasing the stored details
networksetup -setsecurewebproxystate "Wi-Fi" off
# read back what is configured
networksetup -getsecurewebproxy "Wi-Fi"Because these commands target a named network service ("Wi-Fi", "Ethernet"), you can keep separate proxy profiles per connection and flip them with a one-line script, which is far faster than walking through System Settings each time.
Routing every byte through a proxy is often overkill. macOS supports automatic proxy configuration via a PAC file, a small script that returns, per URL, whether to use the proxy and which one. This lets you send only your target domains through the proxy while everything else uses the direct connection, which reduces bandwidth costs on per-GB plans and keeps latency-sensitive traffic local.
The bypass list deserves attention even on a full-system proxy: without entries for localhost and local domains, development servers and internal tools can break the moment the proxy turns on.
A frequent source of frustration is configuring the system proxy correctly yet seeing some apps connect directly. macOS system proxy settings are honoured by apps built on the standard networking stack, but many command-line tools, container runtimes and Electron-based apps maintain their own proxy logic and read environment variables or app-specific config instead. VPN clients add another layer: an active VPN can capture routing and bypass your proxy entirely. The fix is to identify which layer each app obeys, then configure that layer directly rather than assuming the system setting is global.
All this configuration is wasted on a flagged or distant IP. Since the macOS steps are identical across providers, the differentiator is IP quality, supported authentication (username/password versus IP allowlisting, which matters because a changing home IP can break allowlists) and location. For value-conscious Mac users assembling a tidy setup, Cheapest Proxies is worth comparing for capable IPs without premium pricing, leaving more budget for the spare addresses that keep sessions reliable.
Start on the smallest sensible tier and scale only what proves itself on your real targets.
Pick the proxy type the task needs first — it drives both success rate and cost more than the logo.
Check traffic limits, rotation rules and what happens on overage before you commit.
Our featured value pick, Cheapest Proxies, is a sensible starting point for affordable comparison.
The way you configure a proxy on macOS barely changes between providers, so the real difference in your experience comes down to IP quality, location coverage and price. Comparing options on value, rather than grabbing the first plan you find, means your nicely configured Mac actually connects through clean, fast IPs instead of flagged, sluggish ones.
Compare Proxy Zone weighs providers on value, fit and reliability using qualitative judgement — never invented prices, speeds or uptime figures. See our review methodology, or email info@compareproxyzone.com with a correction.
Open System Settings, go to Network, select your active connection, choose Details, then open the Proxies tab to enter the host, port and credentials.
It covers most apps that respect system settings, but some, like Firefox or certain automation tools, have their own proxy configuration and may ignore the system one.
Set the http_proxy and https_proxy environment variables in your shell session, then run a command like curl to confirm traffic routes through the proxy.
HTTP and HTTPS proxies suit web traffic, while SOCKS5 handles a wider range of traffic types. Pick the one your provider supports and your task requires.
Common causes are wrong credentials, an IP that is not allowlisted, an app that ignores system settings, or a forgotten Apply step. Recheck each before assuming the proxy is faulty.
Return to the Proxies tab and untick the enabled protocols, or in the terminal run unset on the proxy environment variables for that session.
Yes. macOS stores proxy settings per network service, so a proxy set for Wi-Fi will not automatically apply when you switch to Ethernet or another connection.
For affordable proxies across the main types, our featured value pick is Cheapest Proxies — a strong budget-friendly option worth considering. Check the exact plan before ordering.