Manifest V3 (MV3) is the latest Chrome extension platform, replacing Manifest V2. Key changes include the declarativeNetRequest API replacing the webRequest API and modifications to background script handling. MV3 provides better security, privacy controls, and performance improvements.

When exactly did Chrome disable MV2?

Chrome began phasing out MV2 in 2023 with warnings in Chrome 127-137. Chrome 138 (released in early 2026) fully disabled MV2 extensions by default for all users.

Can I still use MV2 extensions in any Chrome version?

Chrome enterprise administrators can enable the ExtensionManifestV2Enabled policy for managed devices, extending MV2 support. However, this is only available for enterprise and educational organizations, not individual users.

Why did Google deprecate MV2?

Google states that MV3 provides better security by limiting extension capabilities, improves privacy with user-controlled permissions, and enhances performance by reducing resource usage.

Will all my extensions stop working?

Popular extensions have been updated to MV3 or have MV3-compatible alternatives. Some less-maintained extensions may stop working permanently. Check Extension Fixes for alternatives to affected extensions.

Does Chrome 140 support Manifest V2 extensions?

No. Chrome 140 does not bring back Manifest V2 support for ordinary users. Manifest V2 extensions were disabled earlier in the Chrome MV2 phase-out. Users should use maintained Manifest V3 extensions or suitable alternatives.

Manifest V2 Disabled in Chrome: What You Can Do

Key Takeaways

Chrome 138 disabled MV2 extensions by default for all regular users.
Chrome 139 and later remove MV2 support more completely.
Ordinary users generally cannot permanently restore MV2 support in modern Chrome.
Enterprise-managed devices are a special case with the ExtensionManifestV2Enabled policy.
The recommended path is to find MV3-compatible replacements or official updates.
Firefox remains an option if you need specific MV2 extension functionality.

Current Status

MV2 in Chrome 138+: Fully disabled for regular users
Enterprise policy: ExtensionManifestV2Enabled available for managed devices
Firefox: Still supports MV2 extensions

Why This Happens

Google announced Manifest V2 deprecation in 2020, beginning gradual phase-out.
Chrome 127-137 displayed warnings for MV2 extensions.
Chrome 138 fully disabled MV2 extensions by default for all users.
Manifest V3 offers improved security, privacy, and performance.
Enterprise policies may allow extended MV2 support on managed devices only.

Common Failed Fixes

Trying to: Use Chrome flags to re-enable MV2 extensions

Why it does not work: Chrome flags do not provide a working path to restore MV2 extensions in Chrome 138+. The flags related to MV2 were removed or disabled.

Trying to: Download MV2 extensions as CRX files and load them unpacked

Why it does not work: Chrome blocks loading MV2 extensions from unofficial sources. Even if loaded, they will not function in modern Chrome.

Waiting for Chrome to restore MV2 support — it will not happen in regular Chrome.

What You Can Do

Search for MV3-compatible replacements in the Chrome Web Store.

Check if your extension developer has released an official MV3 version.

Look for community-maintained forks designed as MV3 successors.

Consider Firefox if you need specific MV2 extension functionality.

Use browser-native features that may have replaced extension capabilities.

Check Extension Fixes for alternatives to commonly affected extensions.

Related Extensions

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

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

What Not to Do

Do not try to force-enable MV2 through Chrome flags.
Do not download bypass tools from untrusted sources.
Do not assume all MV2 extensions are unsafe; they simply need updating.
Do not disable Chrome security features to install old extensions.

Frequently Asked Questions

Sources

Chrome Manifest V2 Deprecation Timeline
Google Chrome DevelopersChrome DevelopersPrimary source
Supports: Chrome MV2 deprecation schedule, which Chrome versions disabled MV2, and what extensions are affected
Manifest V3 Migration Guide
Google Chrome DevelopersChrome DevelopersPrimary source
Supports: What Manifest V3 is, why it replaced MV2, and what changes extensions must make
Chrome Web Store Program Policies
Google Chrome DevelopersChrome DevelopersSecondary source
Supports: Why extensions are removed from the Chrome Web Store and what policies apply
Manage extensions on work or school Chromebooks
Google Chrome HelpDocumentationSecondary source
Supports: Why managed devices may have different extension policies than consumer Chrome