Proxies for SwitchyOmega
SwitchyOmega is still the best rule engine for browser proxies: define a profile per gateway, then let Auto Switch decide which sites use which one. Add your Proxy Rotator credentials once and every rule you write can reach residential, datacenter, mobile or IPv6 IPs in 195+ countries.
Auto Switch rules HTTPS & SOCKS5 One click per profile
First, make sure you have a version that still works
This trips up nearly everyone arriving at SwitchyOmega now. The original extension was built on Manifest V2. Google finished removing Manifest V2 extensions from Chrome during 2025, so the original SwitchyOmega was disabled and pulled from the Chrome Web Store. It was never updated. If your copy stopped working and the options page will not open, that is why.
The continuation is ZeroOmega, a community fork that rebuilt the internals for Manifest V3 while keeping the same interface and workflow. It is open source under the GPL, and it runs on Chrome, Edge, Firefox on desktop and Firefox on Android. Everything on this page applies to both, because the proxy settings are identical.
One account behind every profile
SwitchyOmega is only as useful as the proxies you can point it at. Ours cover every type on one set of credentials.
A profile per use case
Save one proxy profile per country or IP type, all on the same credentials with only the port differing, then let Auto Switch route each site to the right one automatically.
HTTPS and SOCKS5
SwitchyOmega's scheme list covers HTTP, HTTPS, SOCKS4 and SOCKS5. Our gateway serves HTTPS and SOCKS5, so you are covered whichever the browser handles better.
All four IP types, one plan
Residential, datacenter, mobile and IPv6 come from the same account. Match the IP type to the rule rather than buying a separate product for each.
City & country targeting
Pin a profile to a country, and a city on residential, so a rule for a localised site always exits where that site expects.
Sticky for real sessions
Browsing is stateful. A sticky port holds one IP so logins and carts survive, instead of breaking when the address moves.
Flexible authentication
Store a username and password in the profile, or whitelist your public IP in your dashboard and leave credentials out entirely, which sidesteps a Chrome limitation covered below.
Add Proxy Rotator to SwitchyOmega
Create a proxy profile, save it, and switch to it from the toolbar.
Copy your gateway details
Open Proxy Gateways in your Proxy Rotator dashboard. Copy the host, the port for the proxy type and location you want, and your username and password. Take a sticky port if you will be signed in to anything.
Create a new proxy profile
Open the extension's options, click New profile, give it a name and choose the Proxy Profile type. Name it after the location or IP type, because the toolbar menu shows these names and you will end up with several.
Enter the gateway
Set the scheme, server and port. Then open the credentials, usually a small lock or key icon on the same row, and enter your username and password.
A SwitchyOmega proxy profile holding Proxy Rotator gateway details.
Apply the changes
Click Apply changes in the options sidebar. This is the step people miss: edits are not live until they are applied, so a profile that looks correct can still be doing nothing. If a change does not seem to take effect, check here first.
Switch to it and test
Click the extension icon and pick your profile, then load an IP echo page to confirm the address changed. Select Direct from the same menu to go back to your normal connection.
Auto Switch: the right proxy per site, automatically
Create a Switch Profile, add conditions, and point each one at a proxy profile or at Direct.
| Condition type | Matches on | Example |
|---|---|---|
| Host wildcard | The hostname only, with * and ? wildcards | *.example.com |
| URL wildcard | The full URL including the path | https://example.com/eu/* |
| URL regex | A regular expression against the whole URL | ^https://.*\.example\.(com|de)/ |
| Default | Everything no other condition matched | Usually Direct |
Conditions are evaluated in order, so put specific rules above general ones.
A setup worth copying
The pattern that works for most people: leave the default result on Direct so ordinary browsing, your own dashboards and your bank never touch the proxy. Then add one condition per site you actually need to see from elsewhere, each pointing at the proxy profile for that country.
Because every profile uses the same credentials and differs only by port, adding a market is copying a profile and changing one number. A rule for a German price page points at your Germany profile, a rule for a US ad preview points at your US profile, and everything else stays direct and fast.
Field mapping
What belongs in each field of a SwitchyOmega proxy profile.
| SwitchyOmega field | What to enter | Example |
|---|---|---|
| Profile name | Any label. It appears in the toolbar menu | Proxy Rotator - US residential |
| Profile type | Proxy Profile for a gateway, Switch Profile for rules | Proxy Profile |
| Scheme | SOCKS5 or HTTPS, both on the same gateway | SOCKS5 |
| Server | Your gateway hostname | gateway.proxyrotator.com |
| Port | The port for that proxy type and location | 8080 |
| Username / Password | Behind the lock icon. Leave blank with IP whitelisting | USER / PASS |
| Apply changes | Not optional. Nothing takes effect until you click it | — |
Host, port and credentials all come from Proxy Gateways in your Proxy Rotator dashboard.
The Chrome SOCKS5 authentication problem
If you have ever saved a SOCKS5 profile with a username and password in Chrome and watched it fail while the identical profile works in Firefox, this is why: Chrome does not support username and password authentication on SOCKS5 proxies. No extension can work around it, because the limitation is in the browser's own proxy handling, not in SwitchyOmega.
Three ways through it, all on the same account:
- Use the HTTPS scheme on Chrome. Credential authentication works normally there. Take the HTTPS port from your dashboard and keep the same username and password.
- Authenticate by IP whitelist. Add your machine's public IP in your dashboard and leave the credentials blank. SOCKS5 then works fine on Chrome, because there is no authentication step to perform.
- Use Firefox for SOCKS5 with credentials. It supports SOCKS5 authentication properly, and it can also route DNS lookups through the proxy.
Verify it is working
Switch to the profile and load an IP echo page. It should show the proxy address. Switch to Direct, reload, and your own address should come back. If you are using Auto Switch, test a URL that matches a condition and one that does not, so you know the routing is doing what you wrote.
To confirm the credentials outside the browser entirely, run this.
curl -x http://USER:PASS@gateway.proxyrotator.com:8080 https://api.ipify.org
Rotating or sticky?
For browsing, sticky. A session assumes one stable address, and a rotating IP will log you out and trigger security checks mid-task. Point the profile at a sticky port and the address holds. Keep a separate profile on a rotating port for quick sampling where a fresh IP per request is the point, and switch between them from the toolbar.
SwitchyOmega not working?
In 2026 the first question is which version you are running.
| Symptom | Likely cause | Fix |
|---|---|---|
| Extension disabled or missing on Chrome | The original was Manifest V2 and has been removed | Move to ZeroOmega, the maintained Manifest V3 fork |
| Repeating authentication prompt | SOCKS5 with credentials, which Chrome does not support | Switch the profile to HTTPS, or use IP whitelisting |
| Changes have no effect | Edits were never applied | Click Apply changes in the options sidebar |
| Still on your real IP | Profile not selected, or Auto Switch fell through to Direct | Pick the profile manually, then check your conditions |
| Wrong proxy used for a site | Condition order. The first match wins | Move the specific condition above the general one |
| Connection refused | Scheme does not match the port | Confirm SOCKS5 vs HTTPS against your dashboard |
| Logged out mid-session | Profile points at a rotating port | Switch to a sticky port from the range in your dashboard |
| Some pages hang on an IPv6 profile | The target site has no IPv6 support | Use residential or datacenter IPv4 for that profile |
Beyond the browser
The same credentials work everywhere. Nothing extra to buy.
FoxyProxy
The other big proxy switcher, with URL-pattern routing.
View setup guideProxifier
Route desktop apps, not just browser tabs, through the gateway.
View setup guidePlaywright & Puppeteer
Script the same routing instead of clicking it.
View setup guideIncogniton
A full antidetect browser when one profile is not enough.
View setup guideFree proxy list
Try the extension with a free IP before you commit to a plan.
Browse the listAll integrations
Every supported tool, with copy-paste setup guides.
Browse all guidesProxy Rotator with SwitchyOmega FAQ
Is SwitchyOmega still working in 2026?
How do I add a proxy to SwitchyOmega?
Why do my SwitchyOmega changes not take effect?
Why does SOCKS5 authentication fail in Chrome?
What is the difference between a Proxy Profile and a Switch Profile?
How do I proxy only certain sites in SwitchyOmega?
*.example.com cover a domain and its subdomains. Conditions are evaluated in order, so specific rules go above general ones.Can I use different countries for different sites?
Should I use a rotating or sticky proxy with SwitchyOmega?
Does SwitchyOmega come with proxies?
Is ZeroOmega safe to install?
Which proxy type should I use for checking localised content?
Give every SwitchyOmega profile a clean IP
Residential, datacenter, mobile and IPv6 proxies on one gateway, with HTTPS and SOCKS5. One account behind every rule you write. From $24.95/mo.