Setup guide
SwitchyOmega setup in Chrome and Edge
The original Proxy SwitchyOmega is no longer maintained. Its author has said so on the project page, and Chrome has disabled it because it was never moved to Manifest V3. The project carries on as Proxy SwitchyOmega 3 (ZeroOmega), an open-source fork for Chrome, Edge and Firefox with the same profiles and switch rules. The labels below come from ZeroOmega 3.5.
Before you start
- Chrome or Edge on a current release.
- HOST, PORT, USERNAME and PASSWORD from the service page, or the public IP you browse from added to the service’s allowlist.
- A short list of the sites that should use the proxy, if not all of them should.
Your connection details
Sign in to the dashboard and open the service you bought. Its page shows the host, port, username and password for that service. There is no single ProxyPanda address to remember, so copy them from there each time. The code in these guides uses the placeholders below; replace each one with your own value.
- HOST
- The proxy address for this service, exactly as the service page shows it.
- PORT
- The port to connect to. Copy it with the host, since it can differ from one service to the next.
- USERNAME
- Your proxy login. It is separate from the email you use for the dashboard.
- PASSWORD
- Copy it in full. On residential, the options you choose in the dashboard are added to the end of the password, so a password typed from memory loses them.
You can skip the username and password by adding the IP address you connect from to the service’s allowlist. Then only HOST and PORT go into your code.
Need help? Letting the proxy recognise your IP address
The examples use HTTP, which reaches https sites through an encrypted tunnel. SOCKS5 works too: residential ports accept both, and ISP and datacenter proxies switch protocol in the dashboard.
Steps
Install the build the project points to
Open the ZeroOmega repository on GitHub and follow the Chrome Web Store or Edge Add-ons link in its README, so you land on the listing the project itself names: Proxy SwitchyOmega 3 (ZeroOmega). If the old SwitchyOmega is still installed, remove it. Only one extension at a time can control the browser’s proxy.
Create a proxy profile
On the options page, click New profile, choose Proxy Profile and name it, for example residential. In the Proxy servers table, on the (default) row, set Protocol to HTTP, Server to HOST and Port to PORT. One row for every kind of address is all most people need, so the per-scheme rows behind Show Advanced can stay hidden.
Proxy Profile › Proxy servers Scheme Protocol Server Port (default) HTTP HOST PORT [lock] Proxy Authentication Username: USERNAME Password: PASSWORDStore the login behind the lock button
The lock at the end of the row opens Proxy Authentication. Enter USERNAME and PASSWORD and save; the lock turns green once a login is stored. Then click Apply changes in the left menu. Until you apply, the browser keeps the old settings.
Or skip the login with the allowlist
In the dashboard, add the public IP of the network you browse from to the service’s allowlist, and leave Proxy Authentication empty. Then HOST and PORT connect on their own and Chrome has no login to ask about. This is also the only way to use SOCKS5 in Chrome or Edge. The allowlist trusts an address, not a person: anyone on that network can use it, and it stops working when your internet provider changes your IP. On residential, the Sticky IP choice travels in the password, so keep the login wherever a sticky session matters.
Keep local addresses direct
Under the servers table, Bypass List takes one address per line that never goes through the proxy. A new profile starts with 127.0.0.1, [::1] and localhost. Add your router’s range, internal names, or <local>, which covers every name without a dot.
Proxy Profile › Bypass List 127.0.0.1 [::1] localhost <local> 192.168.0.0/16Route chosen sites with a Switch Profile
Create a second profile and choose Switch Profile. Each row under Switch rules pairs a condition with a profile, and rows are read from the top, so the first one that matches decides. Host wildcard is the condition for sites: a pattern starting with *. covers the domain itself and every subdomain, and one starting with **. covers subdomains only. Point the Default row at [Direct], and anything you did not list stays off the proxy. Apply changes again.
Switch Profile › Switch rules Condition Type Condition Details Profile Host wildcard api.ipify.org residential Host wildcard *.example.com residential Host wildcard **.example.net residential Default [Direct]Turn it on and check the result
Click the toolbar icon and pick the Switch Profile. Visit https://api.ipify.org: the first rule sends it through the proxy, so the number you see is the proxy’s address. The icon shows which profile handled the tab, and hovering over it brings up the details.
Rotating and sticky IPs
The extension matches a stored login to a proxy by host and port, not by profile. Two profiles on the same residential port, one copied with Sticky IP and one with Randomize IP, both send whichever of the two passwords the extension tries first. Keep one profile per port and copy the password again when you change the session type.
A Switch Profile spends residential gigabytes only on the hosts you list. Pages often pull images and scripts from other hosts, though, and those go direct unless a rule covers them. A site that ties a sign-in to one address may then see two, so add its other hosts to the same profile.
An ISP or datacenter IP keeps its address for the whole rental term, so a profile pointed at one gives the browser the same exit on every visit without any session setting.
Common errors and fixes
Chrome asks for the proxy password although the login is stored
Check the stored password first; a wrong or shortened one brings the box back on every page. If it is correct, you have met a report that has stayed open on the project’s tracker for a long time: some requests, most often those sent while the browser restores tabs at start-up, never reach the extension’s login handler, so Chrome asks you itself. The maintainers suspect a Chromium bug. The extension does not keep what you type into that box. Allowlisting your IP removes the login, and the box with it.
“Your browser DOES NOT support socks5 proxy authentication!”
Chrome and Edge cannot send a username and password to a SOCKS5 proxy, whatever the extension does. Set Protocol to HTTP and match it in the dashboard on ISP and datacenter, or allowlist your IP and keep SOCKS5 without a login.
“The proxy settings are controlled by other app(s) or extension(s).”
Another extension holds the proxy setting: often an old SwitchyOmega, a VPN extension or a second proxy switcher. Disable it on the extensions page and pick your profile again from the popup.
Listed sites still load from your own IP
Three usual causes. The changes were never applied. The popup still has the proxy profile or [Direct] selected rather than the Switch Profile. Or the rule type does not fit the pattern: Host wildcard takes a bare host, while URL wildcard needs a whole address with its scheme and does not give *. the special meaning it has for hosts.
Need help? What a 407 or 403 message means
Which line to pick
For a browser that signs in to the same accounts every day, point the proxy profile at an ISP IP. Residential with Sticky IP suits shorter visits to sites that refuse server addresses, and a Switch Profile keeps those gigabytes to the sites that need them. Datacenter is the cheapest line for dashboards and tools that do not care where you connect from.
Other setup guides
Not sure what a word means? The glossary explains it in plain English.
Stuck on a step?
Paste the command and the error into Discord, with your password taken out. People there have met most of these errors before.