The essential points from this guide -- each one is explained in detail below.
macOS sets proxies per network service (WiFi, Ethernet), not device-wide, under System Settings > Network > [Service] > Details > Proxies.
The networksetup command lets you set or check mac proxy server settings from Terminal without opening any GUI panel.
Proxifier adds per-app proxy routing and proxy chaining that the built-in macOS proxy panel does not support.
A PAC file automates proxy selection by URL pattern instead of pointing every connection at one fixed proxy server.
Certificate and connection errors after enabling an HTTPS proxy are usually a trust or auto-discovery issue, not a broken proxy.
Every mac proxy settings change through the GUI starts in the same place: System Settings > Network, then the connection you want to configure. Pick WiFi or Ethernet, click Details next to the active network, then open the Proxies tab. This is where macOS separates proxy types into distinct fields instead of one shared setting.
Four tabs matter most. Web Proxy (HTTP) covers plain HTTP traffic and takes a server address and port. Secure Web Proxy (HTTPS) is a separate field for encrypted traffic, since macOS does not assume HTTPS should use the same proxy as HTTP unless you enter it twice. SOCKS Proxy accepts a SOCKS5 host and port and covers any TCP traffic, not just web browsing, which makes it the right tab for apps that do not speak HTTP directly. Auto Proxy Discovery, when checked, has macOS look for a WPAD (Web Proxy Auto-Discovery) configuration on the network automatically rather than using a fixed server.
After entering a hostname, port, and (if your provider requires it) a username and password, check the box next to that proxy type to turn it on, then click OK and Apply. The proxy applies only to the network service you configured it under; switching to a different WiFi network reverts to no proxy unless you repeat the steps there too.
One naming detail trips people up when following older guides: this panel lived inside System Preferences on macOS versions before Ventura (13), under Network > Advanced > Proxies. Ventura and later renamed the whole app to System Settings and moved proxy configuration one level shallower, into Network > [Service] > Details > Proxies, without a separate Advanced button. The fields themselves did not change, only where Apple put them.
The networksetup command configures the exact same proxy fields as the GUI panel, but from Terminal, which matters for anyone scripting a setup across multiple Macs or automating it in a provisioning script.
To set an HTTP proxy on the WiFi service:
networksetup -setwebproxy Wi-Fi gw.knoxproxy.com 7000 on USER PASSThe arguments after the port are optional authentication fields; leave them off entirely if your proxy does not require a username and password. For an HTTPS proxy, use the secure variant with the same argument order:
networksetup -setsecurewebproxy Wi-Fi gw.knoxproxy.com 7000 on USER PASSFor SOCKS5, the command name changes to setsocksfirewallproxy and typically points at a different port:
networksetup -setsocksfirewallproxy Wi-Fi gw.knoxproxy.com 7001 on USER PASSEach command targets a network service by name, Wi-Fi in these examples, which must match a service listed by networksetup -listallnetworkservices. Run that command first if you are unsure of the exact service name, since some Macs label the connection Wi-Fi and others (on Ethernet-connected desktops) use a different string entirely.
To turn a proxy off again without clearing the stored address, run the same command with off in place of on: networksetup -setwebproxy Wi-Fi "" "" off. This is the fastest way to disable proxy on mac from a script or a one-line Terminal command, and it is exactly what the System Settings toggle does under the hood.
System-level proxy settings apply to a whole network connection, but some workflows need one specific app routed through a proxy while everything else on the Mac connects normally. That is the gap mac proxifier fills: it intercepts traffic at the application layer and lets you build rules per program instead of per network.
After installing Proxifier, add your proxy server under Profile > Proxy Servers, entering the gateway address, port, and proxy type (HTTP or SOCKS5), plus a username and password if required. Proxifier's Proxification Rules panel is where the per-app control happens: create a rule, select which applications it covers by name or by browsing to the executable, and assign that rule to the proxy server you just added. Any application not covered by a rule falls back to a default action you set, either direct connection or a specified proxy.
Proxifier also supports proxy chaining, routing traffic through more than one proxy server in sequence, which the built-in macOS Proxies tab has no equivalent for. This matters for setups that need traffic to pass through a fixed entry proxy before reaching a rotating exit pool.
DNS handling is the detail that catches new Proxifier users off guard: by default, Proxifier resolves DNS queries through the proxy connection rather than your Mac's own network, which prevents DNS leaks but can break rules that rely on hostname matching if the proxy cannot resolve that specific address. Check the DNS section of a rule if a specific site fails to load under Proxifier but works fine with the system proxy set instead.
A PAC (Proxy Auto-Configuration) file is a script that tells macOS which proxy to use based on the destination URL, instead of routing every connection through one fixed server. This matters when different sites need different proxies, or when some destinations should bypass the proxy entirely and others should not.
To use one, go back to System Settings > Network > [Service] > Details > Proxies, check Automatic Proxy Configuration, and enter the PAC file's URL in the field below it. macOS fetches that file and re-evaluates it for every new connection, so update the hosted PAC file and Macs pointed at that URL pick up the change without any local reconfiguration.
A PAC file makes sense when you are managing proxy routing for multiple destinations with different rules, or maintaining consistent proxy behavior across many Macs from one hosted file. For a single proxy server used for everything, the manual Web Proxy, Secure Web Proxy, and SOCKS Proxy fields covered earlier are simpler and have one less moving part to break. See What Are Proxy Settings? for the full syntax and how to write one.
Certificate errors after turning on the Secure Web Proxy (HTTPS) field are the most common failure, and they usually mean the proxy is intercepting HTTPS traffic with its own certificate that macOS does not yet trust. If your provider issues a proxy certificate for this purpose, install and trust it in Keychain Access before assuming the proxy itself is broken; a plain forwarding HTTPS proxy that does not intercept traffic should not need this step at all.
A proxy that works in Safari but not in another app usually means that app manages its own network stack instead of reading the system-wide proxy settings. Not every application on macOS respects the Proxies tab; some, particularly command-line tools and certain Java or Electron-based apps, need a proxy set through their own preferences or environment variables instead.
To turn off proxy on mac quickly without hunting through menus, uncheck the relevant proxy type's checkbox in System Settings > Network > [Service] > Details > Proxies and click OK, or run the Terminal off command shown earlier for a one-line disable.
To confirm what is actually active without opening the GUI, check proxy status via Terminal with:
networksetup -getwebproxy Wi-FiThis prints the current HTTP proxy server, port, and enabled state for that network service, which is the fastest way to confirm a setting actually applied instead of guessing from app behavior alone. Run the same command with -getsecurewebproxy or -getsocksfirewallproxy to check the HTTPS or SOCKS5 fields.
networksetup -setwebproxy Wi-Fi "" "" off (and the secure or SOCKS variant) for the same result in one line.Ready to put this into practice? Browse Residential Proxies
KnoxProxy Research Team · Technical Content
Network engineers and proxy infrastructure specialists with 10+ years in anti-bot systems, web scraping, and IP routing.
90.4M+ ethically sourced residential IPs across 195 countries. Instant activation, 14-day money-back guarantee.