The short answer
ProxyFox and SwitchyOmega / ZeroOmega all manage proxy profiles, but their priorities differ. ProxyFox focuses on manual switching, strict authentication matching, connection tests, rollback, and local transparency. ZeroOmega carries forward SwitchyOmega-style profiles, automatic rules, and migration workflows.
| Capability | ProxyFox | SwitchyOmega / ZeroOmega direction |
|---|---|---|
| Manifest V3 | Yes | ZeroOmega supports it; classic SwitchyOmega was built around the older platform |
| Manual profile switching | Yes | Yes |
| HTTP / HTTPS / SOCKS | Yes | Yes |
| Automatic proxy by website | No | Typically supports auto-switch or PAC-style rules |
| Direct bypass rules | Global and per-profile | Supported with a different model and syntax |
| Direct SwitchyOmega import | No | ZeroOmega is a better fit for carrying profiles forward |
| Pre-save connection test | Yes, with restoration | Depends on the specific version and feature set |
| Transactional rollback | Switch, save, delete, and import | Implementation differs |
| Account or developer backend | None | Depends on the project |
Choose ProxyFox when
- You manually switch among a small number of trusted profiles.
- Strict authentication host and port matching matters.
- You want a candidate test that restores the current setting.
- You need commented global and per-profile direct-bypass rules.
- You value a relatively small, auditable workflow.
Choose ZeroOmega or another rule-based tool when
- Domains must automatically select different proxies.
- You have many SwitchyOmega profiles to migrate directly.
- You need complex PAC, subscription, or conditional rules.
- You want a workflow close to classic SwitchyOmega.
Before migrating
Do not import a SwitchyOmega or ZeroOmega export directly into ProxyFox; the formats are not compatible. List the hosts, ports, authentication requirements, and bypass rules you still need, rebuild a small number of profiles manually, and test them one at a time.
What local-first means
ProxyFox has no developer backend and does not upload profiles, but credentials still live in Chrome local storage. Local does not mean encrypted. With any proxy extension, review permissions, update provenance, and the proxy service itself.