Key takeaways:
Windows routes traffic for most apps, including Chrome and Edge, through one system proxy setting. Set it once and those apps follow it. This guide covers every method, from the Settings app to the command line, plus how to verify and fix a proxy when something goes wrong. The steps are the same on Windows 11 and Windows 10 unless noted.
Windows offers three setup methods; manual entry is the most common.
Manual setup is the most common method when you have a host and port from a provider.
On Windows 10 the path is identical: Settings > Network & Internet > Proxy. You can also open the classic panel by running inetcpl.cpl, then Connections > LAN settings.
The same four steps work on Windows 11 and Windows 10.
A proxy auto-config (PAC) file is a small script that tells Windows which proxy to use for each site. Organizations often distribute one so every machine uses the same rules.
A PAC file can live at a public or internal URL, or at a local path such as file:///C:/proxy/proxy.pac. Windows stores the configured script address in the registry under HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings as AutoConfigURL, which is where to look if you need to confirm or update the PAC file location.
Many paid proxies require authentication. When you first send traffic through the proxy, Windows or the app prompts for a username and password. Enter the credentials from your provider dashboard and choose to save them if you want Windows to remember them.
For command-line tools that read environment variables, you can include credentials in the proxy URL:
set HTTP_PROXY=http://username:password@host:port
set HTTPS_PROXY=http://username:password@host:port
Store credentials carefully and avoid committing them to scripts or version control.
The Windows Settings proxy field is built for HTTP and HTTPS proxies, so a SOCKS5 address does not belong there. To use SOCKS5, configure it in the application that supports it:
Decide between SOCKS5 and HTTP based on the traffic you route. Our guide on SOCKS5 and HTTP proxies explains when each one fits.
The system panel takes HTTP and HTTPS; set SOCKS5 in the app itself.
Command-line setup is handy for servers, scripts, and machines with no desktop.
Set the system WinHTTP proxy, used by Windows services and many background tools:
netsh winhttp set proxy proxy-server="host:port" bypass-list="*.example.com"
Set the per-user proxy that matches the Settings app, using PowerShell:
$reg = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings'
Set-ItemProperty -Path $reg -Name ProxyServer -Value 'host:port'
Set-ItemProperty -Path $reg -Name ProxyEnable -Value 1
For command-line tools only, set environment variables for the current session:
set HTTP_PROXY=http://host:port
set HTTPS_PROXY=http://host:port
Confirm the active system proxy with this read-only command:
netsh winhttp show proxy
When nothing is set, Windows returns "Direct access (no proxy server)." To change a proxy, edit the host and port in Settings > Network & internet > Proxy and save. To remove it, turn off Use a proxy server (or Use setup script) and select Save, or reset the WinHTTP proxy:
netsh winhttp reset proxy
If you only need to clear the proxy for browsing, see our walkthrough on how to remove a proxy in Chrome, which uses the same Windows panel.
The proxy you set is only as good as the network behind it. A free public proxy often drops connections and raises privacy concerns, so a paid service is the more stable choice for everyday use. Match the type to the task:
Proxy-Cheap offers these on pay-as-you-go and per-IP plans with no monthly commitment. For a full comparison, see our roundup of the best proxy providers.
