Proxy any application
Desktop clients, scrapers, and CLI tools that lack proxy settings all inherit ProxyOmega's residential IPs once a Proxifier rule points them at your server.
Integration Proxy manager
Proxifier Integration
Proxifier pushes traffic from applications that have no proxy setting of their own through a proxy server, system-wide on Windows and macOS. This guide covers adding a ProxyOmega proxy server, choosing SOCKS5 or HTTPS with authentication, and writing proxification rules so only the apps you choose are routed. Menu paths match the current Proxifier release.
- 200+countries
- 1.5M+residential IPs
- SOCKS5on every port
Proxifier
What is Proxifier?
Proxifier is a desktop application for Windows and macOS that intercepts network connections from other programs and reroutes them through a proxy server, even when those programs offer no proxy setting themselves. It operates below the application layer, so command-line tools, desktop clients, games, and automation software can all be proxied without individual configuration.
The two pieces you configure are proxy servers and proxification rules. A proxy server entry holds the address, port, protocol, and credentials of an exit. A proxification rule decides which applications or destinations use that server, which connect directly, and which are blocked. Rules are evaluated top to bottom, so ordering matters.
This system-wide reach is what sets Proxifier apart from a browser extension. Where FoxyProxy or SwitchyOmega only affect one browser, Proxifier can route an entire machine or a hand-picked list of apps, which makes it a strong fit for tools that were never designed with proxy support in mind. Its live Connections view and Log tab also make it easy to confirm precisely how each connection was handled, which is invaluable when you are debugging a route.
Proxifier
Why pair Proxifier with residential proxies
Proxifier decides what gets proxied; ProxyOmega decides how that traffic looks on the way out. Feeding Proxifier a residential exit means apps that would otherwise reveal a datacenter IP present a genuine consumer address instead, with per-app control over which ones do.
Rule-level precision
Proxification rules let one app run through a US residential IP, another connect directly, and a third be blocked, so you route only what needs routing.
Real-IP output
ProxyOmega residential addresses come from real consumer connections, so proxied apps blend in rather than standing out as obvious hosting-range traffic.
Proxifier
How to add ProxyOmega to Proxifier
Have your ProxyOmega credentials ready: your username plus any targeting parameters, and the account API key that serves as the proxy password. Then add the server and, optionally, a rule.
- Open Proxifier and go to Profile, then Proxy Servers, and click Add.
- In Address enter your plan's endpoint, for example residential.proxyomega.com.
- In Port enter a port from your plan's range, for example 10000.
- Under Protocol select SOCKS Version 5 (or HTTPS if you prefer an HTTP-style proxy).
- Tick Enable under Authentication and enter your Username (with any targeting parameters, e.g. youruser-country-us) and Password (your dashboard API key).
- Click OK. If Proxifier asks whether to use this as the default, accept it to route all traffic, or decline if you plan to use rules.
- For selective routing, go to Profile, then Proxification Rules, and click Add.
- Name the rule, click Browse to select the application(s) it applies to, set Action to Proxy and pick your ProxyOmega server.
- Make sure the rule sits above the Default rule in the list, since rules are matched top to bottom.
- Launch the target app and confirm its outbound IP at ipinfo.io or in Proxifier's Connections log.
Proxifier
Choosing SOCKS5 vs HTTPS and a plan
Proxifier supports SOCKS5 and HTTPS proxies, and every ProxyOmega port serves both HTTP/HTTPS and SOCKS5 on the same port, so the port never changes when you change protocol. SOCKS5 is usually the better choice in Proxifier because it forwards all TCP traffic transparently and handles authentication cleanly, which suits arbitrary desktop apps and CLI tools. Choose HTTPS only if a specific application behaves better with an HTTP-style proxy. In both cases the username, password, host, and port are identical.
Select the plan according to the exits your apps need.
| Workload | Plan | Why |
|---|---|---|
| General desktop apps, rotating IPs | Budget Unlimited | Fresh residential IP per port; -country-xx targets a country |
| High-volume or bandwidth-heavy tools | Premium Unlimited | Higher-speed residential on premium.proxyomega.com:8000 |
| City, state, or ASN targeting, pay per GB | Platinum | Granular geo control on platinum.proxyomega.com:20228 |
| Apps that must see a mobile network | Mobile | Real 4G/5G IPs on mobile.proxyomega.com:20229 |
| A fixed IP for logins or allowlists | Static ISP | Stable US IP (Dallas) on isp.proxyomega.com, ports 30000-30099 |
Proxifier
Troubleshooting
When an app is not being proxied or a connection fails, the usual suspects in Proxifier are rule ordering, credentials, and the source IP you are connecting from. The Connections and Log tabs show exactly what Proxifier did with each connection.
Connection refused / 407
A 407 or refused proxy connection points to authentication. Confirm the password is your dashboard API key, not your login password, and that the username's targeting parameters are valid, since an unsupported parameter returns 407. If you authenticate by IP whitelist, remember that once any IP is whitelisted only those IPs may connect, so a request from a non-listed address is refused.
App isn't going through the proxy
Check Proxification Rules. Your rule must sit above the Default rule and correctly name the application's executable. Open the Connections tab to see whether Proxifier matched the app to your server or let it connect directly.
DNS resolves locally
In Profile, then Name Resolution, enable resolving hostnames through the proxy so lookups happen at the exit rather than on your local machine. This keeps DNS consistent with the proxied route.
FAQ
Frequently asked questions
Does Proxifier support SOCKS5 with authentication?
Yes. Choose SOCKS Version 5 as the protocol, tick Enable under Authentication, and enter your username and the API-key password. Every ProxyOmega port serves SOCKS5, so you use the same host and port as HTTP.
How do I proxy only one application?
Add a proxification rule under Profile then Proxification Rules, click Browse to select that app's executable, set the action to Proxy, and choose your ProxyOmega server. Keep the rule above the Default rule so it is matched first.
What is my proxy password in Proxifier?
It is the account API key shown in your ProxyOmega dashboard, not your website login password. The username is your account username plus any dash-separated targeting parameters.
SOCKS5 or HTTPS for desktop apps?
SOCKS5 is the better default in Proxifier because it forwards all TCP traffic and handles authentication cleanly. Use HTTPS only if a particular app works better with an HTTP-style proxy. Both use the same ProxyOmega port.
How do I target a specific country or keep a sticky IP?
Append -country- and a two-letter code to your username, such as youruser-country-ca. For a sticky IP, add -session- with an ID and -ttl- with minutes, for example youruser-session-x1-ttl-30.
Why does my app still show my real IP?
Either no rule matches the app, or a higher rule sent it Direct. Check the Connections tab in Proxifier to see how the connection was routed, and confirm the executable name in your rule is correct.
Proxy any desktop app through residential IPs Start routing today.
Point Proxifier at a ProxyOmega server and route what you choose.
ProxyOmega