Why did Chrome turn off my extension?

The most common reason in 2026 is Manifest V2 deprecation — Chrome 138 and later disabled all MV2 extensions by default. Other reasons include Web Store removal (policy violations, developer request, or malware detection) and proactive security disablement by Google.

Can I re-enable the extension that was turned off?

Generally no. If the extension was disabled due to MV2 deprecation, Chrome 138+ does not support re-enabling MV2 extensions. If it was removed from the Web Store, Chrome will not allow reinstallation. Your best option is to find an MV3-compatible alternative.

What does this message mean for my browser security?

Chrome proactively disables extensions that pose risks. If the extension was disabled for security reasons, it is best to not attempt to reinstall it from unofficial sources. Use verified alternatives from the Chrome Web Store instead.

How do I find a replacement for my turned-off extension?

Check the Chrome Web Store for MV3 updates from the same developer. Search Extension Fixes for your extension name and category. Verify alternative developers and permissions before installing any new extension.

Will my extension settings be lost?

If the extension still opens partially, export your settings immediately. Many extensions allow exporting profiles or configuration files. After finding a replacement, check if it supports importing your exported settings.

What if there is no MV3 alternative for my extension?

Consider browser-native features, alternative browsers that still support MV2 (like Firefox), or workflow adjustments. Some extensions have community-maintained forks worth checking on GitHub.

Why does Chrome say "these extensions were turned off because they're no longer supported"?

Chrome may display the plural "these extensions" version of this message when multiple extensions are disabled at the same time, typically during a Chrome update or batch disable event. Each extension listed was disabled independently — some may be MV2 extensions caught in the same deprecation wave, others may have been removed from the Web Store or flagged for security reasons. Check each extension individually: remove unsupported ones, look for MV3 updates, and use maintained alternatives from the Chrome Web Store.

This Extension Was Turned Off Because It Is No Longer Supported

Key Takeaways

Chrome shows this message when an extension has been automatically disabled — usually due to MV2 deprecation or Web Store removal.
You generally cannot re-enable a turned-off extension in regular Chrome.
Check the Chrome Web Store for an official MV3 update from the same developer.
Extension Fixes provides verified alternatives for commonly affected extensions.
Do not download CRX files from unofficial sources — they may contain unwanted code.
Export any accessible settings before the extension stops working entirely.

Current Status

MV2 extensions: Disabled in Chrome 138+ for regular users
Firefox: Still supports MV2 extensions
Chrome Web Store: Check for official MV3 updates

Why This Happens

Chrome 138+ disabled all Manifest V2 extensions by default for regular users.
The extension was removed from the Chrome Web Store by the developer or due to policy violations.
Google proactively disabled the extension due to detected security concerns.
The extension became incompatible with your current Chrome version.

Common Failed Fixes

Trying to: Search for and install the old version as a CRX file

Why it does not work: Chrome may block loading MV2 extensions from unofficial sources. Even if it loads, the extension will not function in modern Chrome.

Trying to: Wait for Chrome to restore the extension automatically

Why it does not work: Chrome does not automatically restore disabled extensions. The deprecation is permanent for regular Chrome users.

Finding an identical extension with a different name — always verify the developer before installing.

What You Can Do

Check the Chrome Web Store for an official MV3-compatible version of the extension.

Search Extension Fixes for your extension name to find verified alternatives.

Export any remaining extension settings if the option is still accessible.

Look for official announcements from the extension developer.

Contact the extension developer to ask about MV3 updates.

Consider Firefox as an alternative browser if you need specific extension functionality.

Related Extensions

uBlock Origin

Content Blocker

Affected by MV2

Classic uBlock Origin stopped working in Chrome 138+ because Chrome disabled Manifest V2 extensions. For many Chrome users, uBlock Origin Lite is the closest MV3-compatible option from the same developer, but it does not replicate every feature of the original extension. Firefox remains a practical option for users who need full classic uBlock Origin functionality, since Firefox still supports MV2 extensions. Avoid installing random CRX copies of classic uBlock Origin from unofficial sources, because modified extensions can create privacy and security risks. The MV3-compatible ad blocker space is actively developed, and other options like AdGuard AdBlocker and Adblock Plus are available in the Chrome Web Store.

View alternatives

Great Suspender

Tab Management

Removed

The original Great Suspender was removed from the Chrome Web Store after a malicious version incident in 2021, and Chrome proactively disabled it for installed users. Users should avoid reinstalling old CRX copies from mirror sites because modified versions can contain unwanted code. For most Chrome users, Chrome Memory Saver is the simplest built-in replacement for tab suspension. Auto Tab Discard is a practical extension alternative for automatic tab unloading, while OneTab is better for manual tab consolidation and Workona is more focused on workspace management. The best option depends on whether you want automatic suspension, simple memory savings, or session organization.

View alternatives

Proxy SwitchyOmega

Proxy Manager

Affected by MV2

Proxy SwitchyOmega stopped working in Chrome because Chrome 138 fully disabled Manifest V2 extensions. The closest migration path is ZeroOmega, a community fork designed for Manifest V3. FoxyProxy is another established option with advanced proxy management features. Both are available on the Chrome Web Store.

View alternatives

What Not to Do

Do not search for and download CRX files of the old extension.
Do not install extensions with similar names assuming they are from the same developer.
Do not disable Chrome security features to force-install unsupported extensions.
Do not grant broad permissions to unknown replacement extensions.

Frequently Asked Questions

Sources

Chrome Manifest V2 Deprecation Timeline
Google Chrome DevelopersChrome DevelopersPrimary source
Supports: Chrome MV2 deprecation timeline, which Chrome versions disabled MV2, and what extensions are affected
Chrome Web Store Program Policies
Google Chrome DevelopersChrome DevelopersSecondary source
Supports: Why extensions are removed from the Chrome Web Store and what policies apply
Extension Fixes Search Tool
Extension FixesAlternative directoryDiscovery source
Supports: Finding MV3 alternatives for common affected extensions