Before you start
You'll need your proxy's host (IP or hostname), port, and, if it uses authentication, username and password. If your provider supports IP whitelisting, add your public IP in their dashboard first; Windows' built-in proxy settings don't store proxy credentials, so whitelisting avoids repeated login prompts. See proxy authentication methods.
Windows 11: manual proxy
- Open Settings → Network & internet → Proxy.
- Under Manual proxy setup, next to "Use a proxy server", click Set up.
- Toggle Use a proxy server on.
- Enter the Proxy IP address and Port.
- Optionally, list addresses to bypass (separated by semicolons), for example
localhost;127.0.0.1;*.internal.example.com. - Tick Don't use the proxy server for local (intranet) addresses if appropriate.
- Click Save.
Windows 10: manual proxy
Microsoft ended support for Windows 10 on 14 October 2025. If you still run it, for example on a device enrolled in Extended Security Updates, the steps below still apply, but plan your move to Windows 11.
- Open Settings → Network & Internet → Proxy.
- Under Manual proxy setup, turn on Use a proxy server.
- Enter the address and port, add exceptions if needed, and click Save.
Automatic configuration (PAC)
If your organisation or provider gives you a PAC file URL:
- In the same Proxy settings page, under Automatic proxy setup, turn on Use setup script (Windows 11: click Set up next to it).
- Enter the script address and save.
See proxy PAC files.
Which apps use the Windows proxy?
- Chrome and Edge use the Windows system proxy by default.
- Firefox has its own settings but can be set to use system settings. See browser proxy settings.
- Many desktop apps use the system proxy, but some ignore it or have their own settings.
- Command-line tools often use environment variables instead.
Authentication prompts
If your proxy requires a username and password, browsers will prompt you when they first connect. Windows doesn't store proxy credentials in the system proxy dialog. For a smoother setup, use IP whitelisting, or configure proxies per app where credentials can be saved.
SOCKS proxies on Windows
The Windows system proxy settings are designed for HTTP proxies; there's no dedicated SOCKS field. Use per-app SOCKS settings (Firefox, many desktop apps) or a local tool that exposes an HTTP proxy forwarding to SOCKS. See SOCKS5 proxies.
Proxy tip: If you need a working proxy to test these steps with, Geonode generates endpoints in host:port:username:password format, supports IP whitelisting, and has a Chrome extension for quick switching. See using Geonode in your browser.
WinHTTP (services and system components)
Some Windows services use WinHTTP, which has separate settings:
netsh winhttp show proxy
netsh winhttp set proxy proxy-server="http=203.0.113.10:8080;https=203.0.113.10:8080" bypass-list="*.local;<local>"
netsh winhttp import proxy source=ie
netsh winhttp reset proxyRun these in an elevated terminal.
Command-line tools and environment variables
$env:HTTPS_PROXY = "http://USER:PASS@gate.example.com:7777"
$env:HTTP_PROXY = $env:HTTPS_PROXY
curl.exe https://api.ipify.orgWindows includes curl.exe. Note curl reads the lowercase http_proxy for HTTP targets; for HTTPS, either case works. See curl proxy. To set variables permanently, use System Properties → Environment Variables, or setx.
Verify it works
Visit an IP-check site in your browser, or run curl.exe https://api.ipify.org with the proxy configured. The IP should be the proxy's. See how to check if a proxy works.
Troubleshooting
| Problem | Fix |
|---|---|
| No internet after enabling proxy | Check host/port; disable to restore access |
| Repeated password prompts | Use IP whitelisting or per-app settings |
| Some apps ignore the proxy | Configure them individually |
| Intranet sites fail | Add them to the bypass list |
| Works in browser, not in a service | Configure WinHTTP |
See common proxy errors.
Per-app proxy configuration on Windows
| App | Where to configure |
|---|---|
| Firefox | Settings → Network Settings |
| Chrome | Launch flag or extension |
| Git | git config --global http.proxy |
| npm | npm config set proxy / https-proxy |
| pip | --proxy flag or pip.ini |
| PowerShell web cmdlets | -Proxy and -ProxyCredential parameters |
PowerShell example:
$cred = Get-Credential # proxy username and password
Invoke-WebRequest -Uri "https://api.ipify.org" -Proxy "http://gate.example.com:7777" -ProxyCredential $credGroup Policy and enterprise environments
In managed environments, proxy settings may be enforced via Group Policy or Intune. If the settings page shows "Some settings are managed by your organisation", contact IT rather than overriding them.
Finding a stuck or hidden proxy setting
Sometimes Windows keeps using a proxy you thought you'd removed, or traffic goes through one you never set. The current user's settings live in the registry, and you can read them directly:
reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v ProxyEnable
reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v ProxyServer
reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v AutoConfigURLProxyEnable set to 0x1 means a manual proxy is on, ProxyServer shows the host and port, and AutoConfigURL shows a PAC file in use. A "value not found" error simply means that setting isn't configured.
Then check the places the Settings app doesn't show:
- Environment variables for command-line tools, in PowerShell:
Get-ChildItem Env: | Where-Object Name -like '*proxy*'. - WinHTTP, with the
netshcommands above. - Browser extensions that control proxy settings. Chrome and Edge say "controlled by an extension" next to the setting.
- VPN and security software, which may install their own proxy or filtering layer.
If settings keep coming back after you change them, the device is probably managed, and an organisation policy is setting them. Look for "Some settings are managed by your organization" in Settings, and ask IT rather than fighting the policy.
Microsoft's own guide, use a proxy server in Windows, covers the Settings app. For PAC files, see proxy PAC files; for browser-level settings, browser proxy settings.
Key takeaways
- Windows 11 and 10 configure a system-wide HTTP proxy under Settings → Network & internet → Proxy; Chrome and Edge follow it automatically.
- The system dialog doesn't store proxy passwords, so IP whitelisting or per-app settings give a smoother experience with authenticated proxies.
- There's no SOCKS field in the system dialog; use per-app SOCKS settings or a local forwarder.
- Services that use WinHTTP need
netsh winhttpconfiguration separately from the user proxy. - Command-line tools usually read environment variables, and curl only reads lowercase
http_proxyfor HTTP targets. - Always verify with an IP check and, in browsers, a WebRTC and DNS leak test. See how to check if a proxy works.
FAQ
How do I turn off the proxy on Windows?
Settings → Network & internet → Proxy → turn off "Use a proxy server".
Can I use different proxies for different apps?
Yes, by configuring apps individually rather than system-wide.
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.