SwitchyOmega and Manifest V3: What Still Works in Chrome

In short: The original Proxy SwitchyOmega no longer runs in current Chrome. It is a Manifest V2 extension; Chrome disabled every Manifest V2 extension for all users with Chrome 138 in July 2025, and its author has stopped maintaining it. Manifest V3 kept the API that lets an extension set Chrome’s proxy, so proxy switchers still work, and your profiles and rules can move to one that reads SwitchyOmega backups.

Chrome’s switch to Manifest V3 ended Proxy SwitchyOmega, and the original extension will not come back. Manifest V3 kept the API a proxy switcher needs, so the job SwitchyOmega did is still possible with a Manifest V3 switcher, and a SwitchyOmega backup file can carry most of your setup across.

Does Proxy SwitchyOmega still work in Chrome?

No. SwitchyOmega is a Manifest V2 extension, and Chrome’s support timeline records that with Chrome 138 “all users on all channels of Chrome have now Manifest V2 extensions disabled” and that “Users can no longer turn them back on.” The policy that let organisations keep Manifest V2 extensions running was removed in Chrome 139.

The project has ended too. In an update to the pinned issue 2513 on its repository, the author wrote in January 2025 that “This project is no longer maintained” and that the extension “has been disabled on Chrome and removed by Chrome Web Store”. The last release, covering versions 2.5.20 and 2.5.21, came out in August 2018.

What did Manifest V3 change for proxy extensions?

The API that sets Chrome’s proxy survived. Chrome documents the chrome.proxy API, which applies anything from a fixed server to a PAC script, for Manifest V3 extensions, and three other changes shape how a switcher is built:

• Background code stops when idle. Manifest V3 replaced background pages with a service worker, which the migration guide says will “terminate on inactivity”. A switcher keeps its profiles and rules in storage and reads them when it wakes.
• Blocking interception is reserved for managed browsers. The webRequest reference makes the webRequestBlocking permission available only to extensions installed by an organisation’s policy.
• Proxy sign-in has a permission of its own. An extension that answers a proxy’s request for a username and password declares webRequestAuthProvider, and its asyncBlocking option lets it look the credentials up before replying.

A Manifest V3 switcher can therefore still change proxies, route sites by rules and sign in to an HTTP or HTTPS proxy.

Is Microsoft Edge on the same timeline?

Edge runs later than Chrome. Microsoft’s timeline shows deprecation warnings to some users on the Manage extensions page from mid-September 2026 and expects deprecation for enterprise customers to begin in early 2027. A Manifest V2 extension that still runs in Edge faces the same end, on Microsoft’s later schedule.

Which switchers run on current Chrome?

ZeroOmega, FoxyProxy from version 8, and ProxyJam Connector all publish Manifest V3 builds. ZeroOmega is a fork of SwitchyOmega made compatible with Manifest V3. FoxyProxy is a separate switcher that rebuilt its extension for Manifest V3 in version 8. Our free ProxyJam Connector is a third switcher, and its importer reads SwitchyOmega backup files directly. The comparison table lists all three with their sources, and each project’s repository is the place to confirm what it supports today.

What carries over from a SwitchyOmega backup?

ProxyJam Connector’s importer brings in fixed proxy profiles, with their usernames and passwords, and the rules from your auto-switch profiles, which it appends to any rules you already have. Wildcard, regex and keyword conditions become its own rule types; a host-regex condition arrives as a regex matched against the whole address.

It skips the rest and names each skipped entry in its report:

• PAC profiles and rule-list profiles, such as a subscribed list of hosts;
• conditions on IP ranges, host levels, weekdays or times of day, and bypass conditions;
• the default profile an auto-switch profile falls back to, and SwitchyOmega’s bypass lists, which you set again by hand.

Read the report before you delete the backup.

What can no proxy switcher do on Chrome?

Two limits apply to every switcher, SwitchyOmega included. Chromium’s proxy notes say a PAC script has received HTTPS addresses as scheme, host and port only since Chrome 52, so a rule that depends on a path matches no HTTPS page. The same notes say Chrome supports no authentication method for SOCKS5 proxies, so a SOCKS5 proxy that needs a password cannot be used in Chrome by any extension.

Where do you go from here?

To move your setup, install ProxyJam Connector, import your SwitchyOmega backup and read the report it gives you. To send only some sites through a proxy, read routing only some sites through a proxy in Chrome. If a proxy keeps asking for its password, read why Chrome keeps asking for a proxy password.

If you also need proxies to use with it, read what an ISP proxy is first: ProxyJam sells static residential (ISP) proxies on the ISP proxies page, with prices on the pricing page.