Gleb LepeshkinHead of Content Marketing
Windows 11 has no native GUI field for a SOCKS5 proxy with authentication, so you set it up either per-app or across the whole system with a client like Proxifier. The built-in Settings → Network & Internet → Proxy screen handles HTTP/HTTPS; for system-wide SOCKS5 you route traffic through a dedicated client.
Per-App vs System-Wide: Two Ways to Configure SOCKS5
The proxy panel built into Windows (Settings → Network & Internet → Proxy → Manual proxy setup) is designed for HTTP/HTTPS and does not expose a clean SOCKS5 field with username and password. Many apps will ignore a SOCKS entry placed there. The reliable approach depends on what you need to route.
For a single application, set SOCKS5 inside that app’s own network settings. Most browser extensions, scraping tools, and automation clients accept host, port, and SOCKS5 credentials directly. In Firefox, for example, go to Settings → General → Network Settings, select Manual proxy configuration, enter the host and port in the SOCKS Host field, and choose SOCKS v5. Enter credentials when the browser prompts for them on first connection.
For everything system-wide, use a connection manager such as Proxifier. Add your proxy with the following details:
- Address: your proxy host
- Port: your proxy port
- Protocol: SOCKS Version 5
- Authentication: enabled, with your username and password
Then define a rule for which programs or destinations should use it. Proxifier also handles DNS-through-proxy, which prevents DNS leaks that the Windows panel cannot address.
Where a tool expects a single proxy string rather than separate fields, use this format:
socks5://username:password@host:port
This works in curl, many scraping frameworks, and command-line tools that accept proxy URIs directly.
After setup, confirm the result with an IP check from inside the routed app, not from the system browser. If the IP check shows your real IP, the app is bypassing the proxy. If it shows the proxy IP, the SOCKS5 tunnel is active.