# SwitchyOmega and Manifest V3: What Still Works in Chrome | ProxyJam Proxy SwitchyOmega stopped when Chrome ended Manifest V2. What Manifest V3 kept for proxy extensions, which switchers run now, and how to move your rules. - Canonical: https://proxyjam.com/blog/switchyomega-manifest-v3/ - Updated: 2026-10-08 - Language: en 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. ## Moving profiles and rules to a Manifest V3 switcher 1. **Find your backup file** SwitchyOmega saves its settings as a backup file, usually ending in .bak. A disabled extension does not run, so if you never exported one, you have to enter the profiles again by hand. 2. **Install the new switcher** Install it from the browser's store. Chrome and Microsoft Edge both install [ProxyJam Connector](/browser-extension/) from its Chrome Web Store listing. 3. **Import the file and read the report** Connector detects the format and reports how many profiles and rules it imported, and which entries it skipped or rejected, with the reasons. 4. **Rebuild what the importer skipped** Set the fallback for sites that match no rule and enter your bypass list again. Recreate any rule that pointed at a PAC or rule-list profile. 5. **Test one site from each rule** Add proxyjam.com to a rule for a minute and open [What Is My IP](/what-is-my-ip/): it should show the proxy's address. Then take it off the rule. ## Switchers that run on current Chrome | | Relation to SwitchyOmega | Where it comes from | |---|---|---| | FoxyProxy (version 8 and later) | A separate proxy switcher, rebuilt for Manifest V3 in version 8 | Open-source project on GitHub | | ProxyJam Connector | A separate proxy switcher whose importer reads SwitchyOmega and FoxyProxy backup files | Free; published by ProxyJam, which sells ISP proxies | | ZeroOmega | A fork of SwitchyOmega, made compatible with Manifest V3 | Open-source project on GitHub, with Chrome, Edge and Firefox store listings | Each row states what the project publishes about itself, checked on its own repository or documentation on the last-updated date. The list is in alphabetical order and ranks nothing; we did not test the other projects. ## Quick answers ### Can I turn SwitchyOmega back on in Chrome? No. Chrome 138 disabled Manifest V2 extensions for all users, who can no longer re-enable them, and the policy that let organisations keep them running was removed in Chrome 139. ### Is ZeroOmega the same as SwitchyOmega? ZeroOmega is a fork of SwitchyOmega made compatible with Manifest V3 and maintained by a different developer. The original author has published no Manifest V3 version. ### What are the "SwitchyOmega 3" and "SwitchyOmega (V3)" listings in the Chrome Web Store? Listings that reuse the old name for Manifest V3 builds; ZeroOmega's is one of them. The original extension was removed from the Chrome Web Store, and its author has stopped maintaining the project, so none of these listings is the original. ### Do I need the old extension installed to import a SwitchyOmega backup? No. The backup file is enough. ProxyJam Connector reads it directly and detects the format from the file's contents. ## Sources - [Chrome for Developers: Manifest V2 support timeline](https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline), Manifest V2 disabled for all users with Chrome 138 and the enterprise policy removed in Chrome 139 - [Chrome for Developers: migrate to a service worker](https://developer.chrome.com/docs/extensions/develop/migrate/to-service-workers), Manifest V3 replacing background pages with a service worker - [Chrome for Developers: chrome.webRequest API](https://developer.chrome.com/docs/extensions/reference/api/webRequest), blocking interception limited to policy-installed extensions, and the webRequestAuthProvider permission that proxy sign-in requires - [Chrome for Developers: chrome.proxy API](https://developer.chrome.com/docs/extensions/reference/api/proxy), the API that sets Chrome's proxy, documented for Manifest V3 - [SwitchyOmega issue 2513](https://github.com/FelisCatus/SwitchyOmega/issues/2513), the author's notice of January 2025 that the project is no longer maintained - [SwitchyOmega releases](https://github.com/FelisCatus/SwitchyOmega/releases), the last release, 2.5.20 and 2.5.21, published in August 2018 - [ZeroOmega on GitHub](https://github.com/zero-peak/ZeroOmega), a fork of SwitchyOmega compatible with Manifest V3 - [FoxyProxy browser extension on GitHub](https://github.com/foxyproxy/browser-extension), version 8 rebuilt for Manifest V3 - [Microsoft Learn: Manifest V3 and Manifest V2 extension support timeline](https://learn.microsoft.com/en-us/microsoft-edge/extensions/developer-guide/manifest-v3), Edge's own dates - [Chromium: proxy support notes (proxy.md)](https://chromium.googlesource.com/chromium/src/+/HEAD/net/docs/proxy.md), PAC scripts receiving HTTPS addresses without a path since Chrome 52, and no SOCKS5 authentication in Chrome 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](https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-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](https://github.com/FelisCatus/SwitchyOmega/issues/2513), 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](https://github.com/FelisCatus/SwitchyOmega/releases), 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](https://developer.chrome.com/docs/extensions/reference/api/proxy), 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](https://developer.chrome.com/docs/extensions/develop/migrate/to-service-workers) 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](https://developer.chrome.com/docs/extensions/reference/api/webRequest) 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](https://learn.microsoft.com/en-us/microsoft-edge/extensions/developer-guide/manifest-v3) 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](https://github.com/zero-peak/ZeroOmega) is a fork of SwitchyOmega made compatible with Manifest V3. [FoxyProxy](https://github.com/foxyproxy/browser-extension) is a separate switcher that rebuilt its extension for Manifest V3 in version 8. Our free [ProxyJam Connector](/browser-extension/) 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](https://chromium.googlesource.com/chromium/src/+/HEAD/net/docs/proxy.md) 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](/browser-extension/), 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](/blog/chrome-proxy-for-specific-sites/). If a proxy keeps asking for its password, read [why Chrome keeps asking for a proxy password](/blog/chrome-proxy-password-prompt/). If you also need proxies to use with it, read [what an ISP proxy is](/blog/what-are-isp-proxies/) first: ProxyJam sells static residential (ISP) proxies on the [ISP proxies page](/isp-proxies/), with prices on the [pricing page](/pricing/).