Proxifier for Mac: Route One App Through SOCKS and Keep the Rest Direct
Use a specific application rule above a Direct default, retaining the localhost exception and checking which process owns the connection.
For an existing Proxifier for Mac profile, configure the SOCKS endpoint under Proxy Servers, using a matching candidate from the SOCKS proxy list when the application’s public-target route permits a public intermediary, then add a Proxification Rule selecting the intended application.
Keep that application's target-host and port criteria at Any if all of its supported connections should use the proxy. Choose the saved proxy as its action, and leave the Default rule's action as Direct.
| Rule order | Match | Action |
|---|---|---|
| Localhost | Existing loopback exception | Direct |
| Selected app | Chosen application, other criteria Any | Saved SOCKS proxy |
| Default | Remaining connections | Direct |
Rules are evaluated from top to bottom. All criteria within one rule must match. A broader earlier rule can therefore prevent the application-specific rule from taking effect.
Inspect the connection log's application and selected action. A helper process may own a connection instead of the visible application; add it deliberately if it belongs in the same policy.
The Mac documentation describes TCP connection routing. Treat DNS resolution policy and UDP support as separate capabilities. Application selection alone does not prove that every networking operation associated with that application follows this proxy.