How to Configure a SOCKS5 Proxy on Windows
Windows has no complete built-in SOCKS5 client. Here are four reliable ways to use a SOCKS5 proxy: Firefox, curl, Python and a proxifier.
Windows’ own proxy settings are built for HTTP proxies and do not provide a full SOCKS5 client with authentication. Instead you configure SOCKS5 per application — or route applications through a proxifier. You will need the proxy’s host, port, username and password.
Option 1 — Firefox (native SOCKS5)
- Open Settings → General → Network Settings → Settings….
- Choose Manual proxy configuration.
- Enter the host and port in SOCKS Host, and select SOCKS v5.
- Tick “Proxy DNS when using SOCKS v5” so names are resolved at the proxy.
- Save, then browse. Firefox asks for the username and password on the first request.
Option 2 — curl (included with Windows 10 and 11)
Use the socks5h scheme so DNS is resolved by the proxy. Replace the placeholders with your own values.
curl --proxy socks5h://USER:PASS@HOST:PORT https://api.ipify.orgThe command prints the IP address that the website saw. If it shows the proxy’s exit IP rather than your own, the proxy works.
Option 3 — Python
pip install "requests[socks]"import requests
proxy = "socks5h://USER:PASS@HOST:PORT"
r = requests.get("https://api.ipify.org", proxies={"http": proxy, "https": proxy}, timeout=15)
print(r.text)Option 4 — a proxifier for any application
Programs such as Proxifier intercept an application’s connections and send them through your proxy. Add a proxy server with protocol SOCKS Version 5, enter the credentials, then create a rule that applies to the application’s executable. This is the usual way to use SOCKS5 with game clients and desktop software.
Chrome and Edge
Proxy toolsProxy CheckerPaste your proxies and find out which ones really work: the checker opens a tunnel through each one and reports the exit IP, protocol and response time.ExploreVerify and troubleshoot
- Run the SOCKS5 proxy checker to confirm the proxy answers and see its exit IP.
- Check for “connection refused” (wrong port) and “authentication failed” (wrong credentials or IP not whitelisted).
- Use the IP address checker in the browser you configured to confirm that traffic is going through the proxy.
- Read the guide on DNS and WebRTC leaks before relying on the setup.
What Windows’ own proxy settings can and cannot do
Windows keeps two separate proxy configurations. The per-user setting behind Settings → Network & internet → Proxy is read by Edge, Chrome and most desktop software built on the WinINET stack. System services use WinHTTP, which has its own setting. Neither offers a SOCKS5 client with a username and password. The older Internet Options → Connections → LAN settings → Advanced dialog does have a Socks field, but support for it differs from one application to the next and there is nowhere to enter credentials, so treat it as unreliable.
When a tool behaves oddly, first find out whether a system proxy is set at all, because a leftover value can silently route traffic you did not expect. These commands only display the configuration and change nothing.
netsh winhttp show proxy
reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v ProxyEnable
reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v ProxyServerProxyEnable shows 0x1 when the per-user proxy is switched on, and ProxyServer holds its host and port. A WinHTTP result of “Direct access (no proxy server)” is normal.
Special characters in usernames and passwords
Proxy details are usually written as a URL, so characters with a special meaning in URLs break the parsing. A password containing @ makes the client read the wrong host, and a colon or slash can cut the credentials short. The fix is percent-encoding:
- @ becomes %40
- : becomes %3A
- / becomes %2F
- # becomes %23
- ? becomes %3F
- % becomes %25
Python can do the conversion for you, which avoids typing mistakes in long passwords.
from urllib.parse import quote
print(quote("p@ss:w/rd#1", safe="")) # prints p%40ss%3Aw%2Frd%231Two shell details also bite on Windows. Inside a .bat file every percent sign must be doubled, and in PowerShell a URL containing a dollar sign should be wrapped in single quotes so the shell does not treat the text as a variable.
Environment variables for command-line tools
Many command-line tools read their proxy from environment variables, which lets you route a whole terminal session without touching each tool. curl honors ALL_PROXY, and Python’s requests library, with requests[socks] installed, picks up the same variable, so one line covers both. The value lasts only for that window. Avoid making it permanent with setx unless you want every future script on the machine to use the proxy.
$env:ALL_PROXY = "socks5h://user:pass@proxy.example.com:1080"
curl.exe https://api.ipify.org
Remove-Item Env:ALL_PROXYIn cmd.exe the equivalent is:
set "ALL_PROXY=socks5h://user:pass@proxy.example.com:1080"
curl.exe https://api.ipify.org
set ALL_PROXY=Chromium browsers with a whitelisted SOCKS5 proxy
Chrome and Edge cannot send SOCKS5 credentials, so the clean route is to authorize your own IP address instead, if your plan offers it (static mobile plans list whitelisting in the customer panel). Once your IP is whitelisted, pass the proxy on the browser’s command line. Use a dedicated profile folder: if a browser instance with the default profile is already running, a second launch hands its arguments to that instance and the proxy flag has no effect.
& "C:\Program Files\Google\Chrome\Application\chrome.exe" --proxy-server="socks5://proxy.example.com:1080" --user-data-dir="$env:TEMP\chrome-proxy-profile"Edge accepts the same flag. The setting applies only to windows opened from that launch and profile, which is a benefit: your normal browser keeps direct access, and the proxied profile is clearly separate. If you cannot whitelist, a small local relay that listens on 127.0.0.1 without a password and forwards upstream with your credentials is another option. Bind it to the loopback address only, because a relay listening on every interface becomes an open proxy for your whole network and exposes your credentials.
Making a proxifier behave
The basic proxifier setup in Option 4 is enough to start, but three details decide whether it stays reliable. Rule order comes first: rules are evaluated from top to bottom and the first match wins, so put specific rules first and keep the default rule on Direct, otherwise every program on the PC is proxied and Windows services start failing. Name resolution is next: enable remote name resolution if your tool offers it, so lookups are not made by your own resolver. Launchers are the third: many games and tools start through a launcher executable that spawns the real client under a different file name, and a rule for the launcher alone will not catch it. Watch the connection log while the program starts, note which executables open connections and add each one to the rule.
Diagnosing a failure from PowerShell, layer by layer
When nothing works, test one layer at a time so you know which one is broken. Use curl.exe with the .exe suffix: in Windows PowerShell 5.1, plain curl is an alias for Invoke-WebRequest and its options do not apply.
Test-NetConnection proxy.example.com -Port 1080
curl.exe -I -v --proxy socks5h://user:pass@proxy.example.com:1080 https://example.com
Get-NetTCPConnection -OwningProcess 1234 | Select-Object RemoteAddress, RemotePort, State- Reach the port. Test-NetConnection should report TcpTestSucceeded : True. If it fails, the cause is the host, the port, a firewall on your side or a network that blocks the port, not your credentials.
- Complete the SOCKS5 handshake. With -v, success prints SOCKS5 request granted followed by the response headers. A message such as “User was rejected by the SOCKS5 server” means the credentials are wrong or your IP is not whitelisted.
- Read curl’s exit code. Typically 7 means the connection to the proxy failed, 28 means a timeout, and 97 indicates a proxy handshake error, for example speaking SOCKS5 to a port that serves HTTP.
- Inspect the application’s connections. Replace 1234 with the process ID from Task Manager. For a program with built-in SOCKS5 support, the list should show established connections only to the proxy address. Connections to other addresses suggest that part of the traffic bypasses the proxy, for example through a helper process or UDP that the application sends directly.
Frequently asked questions
Why does curl in PowerShell ignore my proxy options?
In Windows PowerShell 5.1, curl is an alias for Invoke-WebRequest, a different command with different parameters. Type curl.exe to run the real curl that ships with Windows 10 and 11. Using the .exe name works in every PowerShell version.
Does the Windows 11 proxy settings page support SOCKS5?
Its manual setup is designed for HTTP-style proxies and has no field for SOCKS5 credentials. For SOCKS5, use per-application settings, environment variables for command-line tools, or a proxifier for programs without proxy support.
My game launcher is proxied but the game itself is not. What is wrong?
The launcher probably starts the real game as a separate executable, and your proxifier rule matches only the launcher. Watch the connection log while the game starts, add the executable that opens the game connections to the rule, and confirm the exit IP before logging in. Always check that the game’s rules allow proxy use.