Proxies for Proxifier
Proxifier pushes any application through a proxy, even the ones with no proxy setting at all. Add your Proxy Rotator gateway once, write a rule per app, and route exactly what you want through a residential, datacenter, mobile or IPv6 IP while everything else stays on your normal connection.
HTTPS & SOCKS5 Per-app rules DNS through the proxy
Built for the apps that ignore proxy settings
Proxifier solves the routing. We supply the IPs behind it, in every type, on one plan.
HTTPS and SOCKS5
Proxifier's protocol list includes HTTPS and SOCKS version 5, and our gateway serves both. SOCKS5 is the better default here, it carries any TCP traffic rather than just web requests.
All four IP types, one plan
Residential, datacenter, mobile and IPv6 come from the same account, so you can point one app at a residential IP and another at a fast datacenter IP without buying twice.
Sticky sessions for desktop apps
Desktop software holds long connections and stays logged in. A sticky port keeps one IP in place for the session so an app is not silently reassigned mid-task.
DNS handled properly
Turn on Resolve hostnames through proxy and lookups leave through the gateway instead of your ISP's resolver, which is the leak most Proxifier setups miss.
City & country targeting
Choose the country, and the city on residential, so an app that checks location sees a consistent, believable place.
Flexible authentication
Enter a username and password in the proxy dialog, or whitelist your machine's public IP in your dashboard and leave the credentials blank.
Add Proxy Rotator to Proxifier
Four steps from a fresh install to an application running on your own IP.
Copy your gateway details
Open Proxy Gateways in your Proxy Rotator dashboard. Copy the host, the port for the proxy type and location you want, and your username and password. Each type shows a rotating port and a range of sticky ports, pick a sticky port if the app needs to stay on one IP.
Open Proxy Servers and add the gateway
In Proxifier, go to Profile › Proxy Servers… and click Add. Fill in the address, port and protocol, then tick Authentication and enter your credentials.
The Proxifier proxy dialog with Proxy Rotator gateway details.
Check it before you rely on it
Click Check in the dialog to launch the Proxy Checker, also available from View › Proxy Checker. It tests the proxy and measures response time, then reports back with the problem if something is wrong. Fix any failure here rather than debugging it later inside an application.
Decide what gets proxied
Proxifier will ask whether the new proxy should handle traffic by default. Accept that to route everything, or say no and write targeted rules instead, which is the approach we recommend below.
Proxification Rules: route only what you mean to
Most Proxifier problems are rule problems, not proxy problems. Open Profile › Proxification Rules… and be specific.
| What you want | Applications field | Action |
|---|---|---|
| Route one browser only | chrome.exe | Proxy |
| Route several tools together | chrome.exe; scraper.exe | Proxy |
| Route a specific build, not any copy | C:\Apps\scraper\run.exe | Proxy |
| Keep updaters off your bandwidth | *update*.exe | Direct |
| Stop an app talking out at all | telemetry.exe | Block |
| Route one running process | pid=1234 | Proxy |
| Send everything else direct | Default rule, cannot be deleted | Direct |
A connection has to match the Applications, Target hosts and Target ports fields together. A blank field shows Any and matches everything.
Rule order decides everything
Proxifier reads rules from the top down and stops at the first match, so a broad rule sitting above a narrow one will swallow it. Put your most specific rules first and use the arrow buttons to reorder. The Default rule always sits at the bottom and catches whatever is left, and a predefined Localhost rule keeps loopback traffic out of the tunnel, leave that one alone.
Each rule also accepts a Target hosts and Target ports filter, which is how you proxy one destination rather than one program. That is useful when a single browser should reach one site through a residential IP and everything else directly.
# Applications (semicolons separate entries) chrome.exe; firefox.exe # match by executable name C:\Apps\scraper\run.exe # match one exact build by full path *update*.exe # wildcards: * is any substring, ? is one char pid=1234 # match a single running process # Target hosts *.example.com # wildcard domain 192.168.0.1-192.168.0.255 # address range 10.0.0.0/8 # CIDR notation, IPv4 # Target ports 443 # single port 8000-8100 # port range
Proxifier also supports Proxy Chains, where a connection passes through two or more proxies in sequence. Set the rule's action to Chain and build the chain in the Proxy Servers dialog. Most setups do not need it, and every extra hop costs latency, so reach for it only when a specific route demands it.
Field mapping
Every field in the Proxifier proxy dialog and what belongs in it.
| Proxifier field | What to enter | Example |
|---|---|---|
| Address | Your gateway hostname. An IPv4 or IPv6 address works too | gateway.proxyrotator.com |
| Port | The port for that proxy type and location | 8080 |
| Protocol | SOCKS version 5, or HTTPS | SOCKS version 5 |
| Authentication | Tick it, unless you authenticate by IP whitelist | Enabled |
| Username | Your gateway username | USER |
| Password | Your gateway password | PASS |
| Protocol: HTTP | Avoid. Carries HTTP connections only | — |
Host, port and credentials all come from Proxy Gateways in your Proxy Rotator dashboard.
Stop the DNS leak
This is the step most guides skip. By default your machine can still resolve hostnames through your own ISP's resolver even while the traffic itself goes through the proxy. The connection is proxied, the lookup is not, and anyone watching DNS sees exactly which sites the app is visiting, from your real network.
Open Profile › Name Resolution… and enable Resolve hostnames through proxy. Proxifier then sends lookups out through the gateway with the rest of the traffic. There is also an automatic mode that watches whether system DNS is reachable and switches as needed.
If some names must stay local, for example an internal hostname on your own network, the same dialog takes a list in either direction: Do NOT resolve the following keeps matching names local and sends the rest through the proxy, and Resolve ONLY the following does the opposite. Both accept wildcards.
Verify the connection
Proxifier's own Proxy Checker confirms the gateway answers. To confirm the credentials independently, run this from a terminal on the same machine. It should print an IP that is not yours.
curl -x http://USER:PASS@gateway.proxyrotator.com:8080 https://api.ipify.org
Then check the app itself. Proxify a browser, load an IP echo page, and confirm it shows the proxy address. Proxifier's main window logs every connection it handles in real time, so if an application's traffic is not listed there, the rule is not matching it and the app is still going out directly.
Run the cURL command twice against a rotating port and you should get two different IPs. Run it twice against a sticky port and the IP should stay the same.
Rotating or sticky for desktop apps?
Desktop software behaves differently from a scraper. It opens long-lived connections, stays signed in, and often assumes the address it started on is the address it keeps. For that, use a sticky proxy: point the app at a sticky port and the IP holds for the session, so a login does not get invalidated halfway through a task.
Use a rotating proxy when the app makes many independent requests and a fresh IP per connection is an advantage, such as a desktop crawler or a bulk checker. Both modes live on the same gateway and the same plan, so you switch by changing the port in the Proxifier dialog and nothing else.
Running several apps that each need their own IP? Add a separate proxy entry per app, each on its own sticky port, then write one rule per application pointing at its own entry. Proxifier keeps them cleanly separated.
Proxifier not connecting through the proxy?
The failures we see most, and what actually fixes them.
| Symptom | Likely cause | Fix |
|---|---|---|
| Proxy Checker fails on every test | Wrong port for the protocol, or a typo in the host | Re-copy host and port from Proxy Gateways, confirm HTTPS vs SOCKS5 |
| Authentication rejected | Credentials missing, or IP-whitelist auth from an unlisted IP | Tick Authentication and enter user:pass, or whitelist this machine's IP |
| App traffic never appears in the log | No rule matches it, so it is going out directly | Check the executable name in the rule and move the rule higher |
| A broad rule catches the wrong apps | Rule order. Proxifier stops at the first match | Move specific rules above general ones with the arrow buttons |
| Site loads but shows your real location | Hostnames still resolving locally | Enable Resolve hostnames through proxy in Name Resolution |
| Works for web, breaks everything else | Protocol set to plain HTTP | Switch to SOCKS version 5, or HTTPS |
| Nothing connects after install | Antivirus or firewall blocking the driver | Add Proxifier to the exceptions list, then retest |
| The IP changes mid-session | Pointed at a rotating port | Switch to a sticky port from the range in your dashboard |
Still stuck? Our support team answers real questions from real people.
Pair Proxifier with the rest of your stack
One plan, one set of credentials. Use it everywhere at once.
Incogniton
Sticky IP per antidetect profile, with bulk proxy import.
View setup guideAdsPower
Per-profile proxies for multi-account work.
View setup guideSelenium
Drive a real browser through rotating or sticky IPs.
View setup guideScrapy
One gateway, a new IP per request, no proxy lists.
View setup guideRotating proxy API
Endpoint details, protocols and code samples.
Read the docsAll integrations
Every supported tool, with copy-paste setup guides.
Browse all guidesProxy Rotator with Proxifier FAQ
How do I add a proxy to Proxifier?
Should I use SOCKS5 or HTTPS in Proxifier?
Does Proxifier include proxies?
Why is Proxifier not connecting through the proxy?
How do I proxy only one application in Proxifier?
chrome.exe, and set the Action to Proxy. Leave the Default rule set to Direct so everything else stays on your normal connection. Rules are read top to bottom, so keep specific rules above general ones.How do I stop DNS leaks in Proxifier?
Can I run different apps on different IPs at the same time?
Which proxy type should I use with Proxifier?
Should I use a rotating or sticky proxy in Proxifier?
Does Proxifier work on Mac as well as Windows?
Can I use IP whitelisting instead of a username and password?
Route any app through a clean IP
Residential, datacenter, mobile and IPv6 proxies on one gateway, with HTTPS and SOCKS5 for Proxifier. From $24.95/mo.