Docs / Getting started / ZeroOmega

Guide Browser proxy switching

ZeroOmega, Zero Omega, and Proxy SwitchyOmega setup with Crusader

~8 min · Chrome / Edge / Firefox proxy extension · Free

The short version. ZeroOmega, also listed as Proxy SwitchyOmega 3, is the current proxy-switcher path for users who want the SwitchyOmega workflow on modern browsers. People often search for the same extension as zero omega, omega zero, or the misspelling zeromega. Use it to create a Crusader proxy profile at 127.0.0.1:8080, route a browser through Crusader, and optionally add auto-switch rules for target hosts. Use Crusader's built-in test browser first for WAF-sensitive and JA3/browser-fingerprint-sensitive flows; ZeroOmega is a convenient routing extension, not a fingerprint fix.

01ZeroOmega vs SwitchyOmega

SwitchyOmega is the older proxy configuration extension many testers already know. ZeroOmega is a maintained fork of Proxy SwitchyOmega that targets modern Manifest V3 browser extension requirements. In browser stores it commonly appears as Proxy SwitchyOmega 3 (ZeroOmega); in search, you may also see the spaced forms zero omega and omega zero.

For current Chrome, Edge, Brave, and Chromium-family browsers, use ZeroOmega unless you have a specific reason to use the old extension. The original SwitchyOmega GitHub repository says it is no longer maintained and warns that similar project-homepage domains are not official.

NameUse it when
ZeroOmega / Proxy SwitchyOmega 3You want the SwitchyOmega workflow on current Chrome, Edge, Firefox, or Chromium browsers. This is the recommended path for most users.
Proxy SwitchyOmegaYou intentionally need the legacy extension, your browser still supports it, or you are importing an old SwitchyOmega profile.
Crusader test browserYou need the cleanest Crusader baseline for WAF-sensitive flows, login journeys, checkout, or JA3/browser-fingerprint-sensitive testing.

ZeroOmega and SwitchyOmega route browser traffic. They do not make traffic more browser-like at the TLS or HTTP/2 layer. For fingerprint-sensitive tests, confirm behavior in Crusader's built-in browser.

02Download ZeroOmega safely

Install only from the official project or browser store listings. Avoid random "SwitchyOmega download" or "omega zero download" sites; the original project specifically warns that unofficial homepage-style domains are not affiliated with SwitchyOmega.

If you searched for the zero omega chrome extension, the Chrome Web Store listing below is the current Proxy SwitchyOmega 3 (ZeroOmega) listing. For Edge and Firefox, use the matching official store links instead of side-loaded packages.

Pin the ZeroOmega icon after install. You want the active profile visible while testing so you do not accidentally browse through Crusader after the engagement ends.

03Start Crusader and note the listener

Open Crusader and confirm the proxy is running. The default listener is 127.0.0.1:8080. If that port is already used, Crusader may move to a nearby free port such as 8081. Use the host and port Crusader actually reports.

ZeroOmega does not start Crusader. If the profile points at the wrong port or Crusader is closed, the browser will stop loading pages until you switch back to Direct.

04Create the Crusader proxy profile

  1. Open ZeroOmega and choose Options.
  2. Select New profile.
  3. Name the profile Crusader.
  4. Choose Proxy Profile, then create it.
  5. Set protocol to HTTP.
  6. Set server or host to 127.0.0.1.
  7. Set port to the Crusader listener, usually 8080.
  8. Leave username and password blank unless you intentionally put another authenticated proxy in front of Crusader.
  9. Click Apply changes.
Profile name: Crusader
Protocol:     HTTP
Server:       127.0.0.1
Port:         8080
Auth:         blank

For the first test, select the Crusader profile manually and route all browser traffic through it. Once capture works, narrow the routing with auto-switch rules.

05Add auto-switch rules

Auto-switch rules are optional, but they are useful when you only want authorized target traffic routed into Crusader while everything else goes direct. Create an auto switch profile, send matching hosts to Crusader, and leave the default profile as Direct.

TargetRule idea
Single hostexample.com routes only that host through Crusader.
Subdomains*.example.com routes target subdomains through Crusader.
Program scopeCreate one rule per authorized host pattern; keep third-party analytics, ads, and unrelated domains direct.

After rules work in ZeroOmega, still set Target scope inside Crusader. Browser routing controls what reaches the proxy; Crusader scope controls what the project stores, scans, and surfaces.

06Trust the Crusader CA

Proxy routing and HTTPS trust are separate. ZeroOmega can send browser traffic to Crusader, but the browser still has to trust the Crusader CA or HTTPS sites will show certificate errors.

Use Crusader's CA wizard or follow Trust the Crusader CA. Chromium browsers usually use OS trust. Firefox can use its own certificate store, so verify Firefox trust separately before testing HTTPS targets.

If you do not want to touch your daily browser or OS trust store, use Crusader's Open test browser. It launches an isolated profile with Crusader trust already handled.

07Verify capture

  1. Enable the Crusader profile in ZeroOmega.
  2. Open a target you are authorized to test.
  3. Open Crusader History.
  4. Confirm the request appears with the expected host, method, status, request headers, and response.
  5. Switch ZeroOmega back to Direct when you finish testing.

If you see a WAF block or bot challenge only when using ZeroOmega, retest with Crusader's built-in browser before treating it as target behavior. Extension-managed proxy routing can change the path enough to trigger defenses that a clean browser profile does not.

08Troubleshooting

SymptomCheck
No traffic in CrusaderConfirm Crusader is running, ZeroOmega is set to the Crusader profile, and the port matches the listener Crusader reports.
HTTPS certificate errorsTrust the Crusader CA for that browser. Firefox may need browser-store trust even when OS trust is correct.
Only some target URLs captureReview auto-switch rules. Start with manual Crusader profile routing, verify capture, then add host rules.
Everything breaks after closing CrusaderSwitch ZeroOmega back to Direct. The browser is still pointing at a local proxy that is not listening.
WAF or bot page appearsRetest in Crusader's built-in browser and compare. Do not base a finding only on extension-routed behavior.

09FAQ

What is ZeroOmega or zero omega?

ZeroOmega is an open-source browser extension for managing proxy profiles and switching browser traffic through them. It is forked from Proxy SwitchyOmega and is commonly listed as Proxy SwitchyOmega 3 (ZeroOmega). The spaced search term "zero omega" points to the same extension family.

Is ZeroOmega the same as SwitchyOmega?

ZeroOmega is a maintained fork of SwitchyOmega. If you are on current Chrome, Edge, Brave, or another Chromium browser, use ZeroOmega unless you have a reason to use the older extension.

What about "zero omega," "omega zero," "zeromega," "Switchy Omega," or "SwithyOmega"?

"Zero omega" and "omega zero" are spaced search variants people use for ZeroOmega. "Zeromega" is a common misspelling. "Switchy Omega" is just a spaced spelling of SwitchyOmega, and "SwithyOmega" is a common misspelling. The current extension most users want is ZeroOmega / Proxy SwitchyOmega 3.

Does ZeroOmega make Crusader traffic look like Chrome?

No. ZeroOmega is a proxy switcher. It routes traffic, but it does not solve TLS, JA3, JA4, HTTP/2, or header-order fingerprint differences. Use Crusader's built-in browser for WAF-sensitive and fingerprint-sensitive testing.

Is ZeroOmega free?

Yes. ZeroOmega is free and open source. The extension does not include proxy servers; it only routes browser traffic through a proxy you configure, such as Crusader on 127.0.0.1:8080.

Want a guide that isn't here yet? Email [email protected].