Chrome 140 and Manifest V2 Extensions
Quick Answer
Chrome 140 does not bring back Manifest V2 support for ordinary users. Manifest V2 extensions were disabled earlier in the MV2 phase-out, so old extensions that depend on MV2 usually do not work in modern Chrome. Users should check for maintained Manifest V3 updates, use trusted alternatives, or consider another browser only when they specifically need classic extension behavior. Avoid installing old CRX files or disabling browser protections, because unsupported extensions can request broad access to pages you visit.
Key Takeaways
- Chrome 140 does not restore ordinary-user Manifest V2 support.
- Many old Chrome extensions stopped working because of the MV2 phase-out.
- Reinstalling the same extension usually does not solve the compatibility issue.
- Maintained MV3 alternatives are the long-term path for Chrome users.
- Old CRX files from mirror sites are not recommended and can be unsafe.
Current Status
- Chrome status
- MV2 support no longer available for ordinary users
- User control
- No simple toggle restores old MV2 support
- Recommended path
- Use MV3 updates or maintained alternatives
- Last reviewed
- May 23, 2026
Why This Happens
- Chrome 140 is part of the ongoing Manifest V2 deprecation and does not restore MV2 support for regular users.
- Chrome 138 fully disabled MV2 extensions by default for all non-enterprise users.
- Chrome 140 follows the same MV2 deprecation schedule with no special exception for regular users.
- The MV2-to-MV3 migration is a platform-level change, not a per-extension setting.
- Chrome enterprise administrators can still use enterprise extension policies to manage MV2 on managed devices.
Common Failed Fixes
Trying to: Install old CRX files from mirror sites
Why it does not work: Old CRX packages may be outdated, modified, or incompatible with Chrome 140. Chrome does not support MV2 extensions regardless.
Safer alternative: Use MV3-compatible alternatives from the Chrome Web Store.
Trying to: Keep using an outdated Chrome build
Why it does not work: Outdated Chrome builds do not receive security patches. The security risk outweighs any benefit from preserving MV2 extension access.
Safer alternative: Use a modern Chrome build and migrate to MV3-compatible extensions.
Trying to: Enable developer mode and expect old APIs to work
Why it does not work: Developer Mode does not re-enable MV2 APIs. It only allows loading unpacked extensions that still use the supported platform.
Safer alternative: Look for MV3-compatible versions of the extensions you need.
Trying to: Change Chrome flags to re-enable MV2
Why it does not work: MV2 removal flags are temporary, version-dependent, and removed in later Chrome versions. They do not make unsupported APIs functional.
Safer alternative: Use this only as a short-term data export path, not a permanent workaround.
Trying to: Disable browser protections to run old extensions
Why it does not work: Disabling browser protections exposes your pages, cookies, and credentials to any extension loaded, including old or unverified ones.
Safer alternative: Use only verified extensions from the Chrome Web Store.
What You Can Do
Identify which extensions stopped working and check whether MV3 updates are available.
Search the Chrome Web Store for maintained MV3-compatible versions from the same developer.
Use Extension Fixes to find verified alternatives for affected extensions.
Export settings from old extensions if possible before removing them.
Consider Firefox as a secondary browser for specific extensions that only work with MV2.
Report extension migration issues to the developer's official support channels.
What Not to Do
- Do not install old CRX files from mirror sites.
- Do not keep using an outdated Chrome build to preserve MV2 support.
- Do not enable developer flags to try to force MV2 support — flags are temporary and version-dependent.
- Do not disable browser protections to run old extensions, because this exposes your browsing data.
Frequently Asked Questions
Sources
- Chrome Manifest V2 Deprecation TimelineGoogle Chrome DevelopersChrome DevelopersPrimary source
Supports: Chrome MV2 deprecation schedule, which versions disabled MV2, and enterprise policy options
- Manifest V3 Migration GuideGoogle Chrome DevelopersChrome DevelopersPrimary source
Supports: What MV3 is, why it replaced MV2, and how extensions must migrate
- Chrome Extension InstallationGoogle Chrome DevelopersChrome DevelopersPrimary source
Supports: Chrome extension installation requirements and manifest version policies