Proxifier Proxy Setup: Route One App Through SOCKS5

• Edition and Windows version. Proxifier for Windows runs on Windows 7, 8, 10 and 11 (and Windows Server 2008 to 2022), 32- and 64-bit. The Standard Edition installs with administrator rights and can proxify every app, including services; the Portable Edition needs no install but proxifies only apps with a window. See Proxifier's editions page.
• Turn off the app's own proxy setting. If the app is already set to use a proxy, set it back to a direct connection. Otherwise, as Proxifier's own proxy documentation warns, the connection may be processed through the proxy twice, by the app and by Proxifier.

1. Open Profile → Proxy Servers and select Add.

2. Enter address gate.proxyfield.io and port 7000, and choose the protocol SOCKS Version 5.
3. Under Authentication, select Enable and enter your ProxyField username (for example <login>-country-us-city-new_york) and password. SOCKS5 is the SOCKS version that carries a username and password; SOCKS 4 has no password login.

4. Optional: under Advanced, give the proxy a label such as ProxyField US, so your rules and the connection list show a name instead of the address. Proxifier's proxy documentation lists custom label and interactive login among the advanced options.
5. Select Check. Proxifier opens its Proxy Checker, which connects through the proxy to a test site and reports whether it worked.
6. Select OK. When Proxifier asks whether to use this proxy by default, answer No, so only the apps you choose use it (step 2).

Proxification rules decide which connection goes where. Proxifier reads them from top to bottom and uses the first rule a connection matches; Default, at the bottom, catches everything else.

1. Open Profile → Proxification Rules and select Add.
2. Name the rule, for example My app via SOCKS5.
3. Under Applications, select Browse and pick the app's .exe, or type its name (app.exe). Separate several names with semicolons (chrome.exe; python.exe), put names with spaces in double quotes, and use * as a wildcard ("my tool*.exe"). Many apps run more than one process, such as a launcher and a helper: add each .exe.
4. Leave Target hosts and Target ports empty: they show Any, so every connection of the app matches.
5. Set Action to the ProxyField SOCKS5 proxy and select OK.

6. Move the rule above Default with the arrow buttons if it isn't there already.
7. Set the Default rule's action to Direct, so the rest of your computer keeps its own connection. Keep the built-in Localhost rule enabled, so connections to 127.0.0.1 stay local.
8. Close the app fully and open it again, so its connections start under the new rule.

For a one-off test without a rule, the Standard Edition can also start an app through a chosen proxy by hand (manual proxification); rules do not apply to apps started that way.

To send the whole computer through the proxy instead, set Default to the proxy and add Direct rules for what should stay local, such as your network drives.

Under Profile → Name Resolution, choose to resolve hostnames through the proxy. Lookups then happen at the proxy's location, so a site sees the country you chose rather than a DNS request from your own network, and names resolve to the servers nearest the proxy.

The Windows Remote Desktop client (mstsc.exe) has no proxy setting of its own: there is no SOCKS or HTTP proxy field, and the RD Gateway option is for Microsoft's own gateway servers, not for proxies. Proxifier fills the gap with any proxy that accepts connections to the remote computer's port. Ask our 24/7 live chat before you route RDP through ProxyField.

1. Add a rule for mstsc.exe with the ProxyField proxy as its action.
2. Connect to the remote computer as usual; Proxifier sends the TCP connection through the proxy.
3. RDP prefers UDP when it can. Proxifier works mainly with TCP connections, and RDP falls back to TCP when UDP is not available, which is slower on video but works for normal desktop use.

Remote Desktop uses port 3389 rather than a web port. Only connect to computers you are allowed to reach; scanning or guessing passwords is not allowed under our acceptable use policy.

Proxifier's main window has three panes that show whether the rule worked (user interface docs):

Then check the exit IP:

1. With a rule for your browser, open https://api.ipify.org: it should show the proxy's IP, not yours.
2. https://ipinfo.io/json shows the country and city, so you can see that -country-us-city-new_york in the username took effect.

Gateway error messages: 407 Proxy Authentication Required for a wrong login or password, an IP not on the allowlist or a malformed location, 402 Payment Required when no traffic is left and 502 Bad Gateway when no exit could be connected; a restricted site gets no separate response, and a 403 comes from the site itself. Status codes are explained in proxy errors. To test a proxy line on its own, use the proxy checker. Our 24/7 live chat helps with setup and integration.

Proxifier can chain several proxies under Profile → Proxy Chains, so a connection passes through each in turn. With ProxyField you don't need a chain to rotate: the gateway changes the IP itself, on every request or after the sticky time you choose. A chain adds a hop and its delay; it makes sense only when you have to pass one fixed proxy first, such as a company proxy. Proxy Chaining covers the trade-offs.

On Windows without Proxifier, the system proxy and app settings are covered on Windows proxy setup; on a Mac, see macOS; on Linux, proxychains does Proxifier's job (Linux).

ProxyField residential proxies cost $2.95/GB for 1 GB down to $1.95/GB from 1,000 GB, with a 99.6% success rate, according to our service data; mobile 5G/4G proxies cost $3.45/GB down to $2.45/GB, on the same gateway and balance. Start with the Easy Trial: 1 GB for $2.95, with no minimum purchase and no subscription. The traffic never expires and all purchases are final. See pricing per GB.