Cannot Install Extension: Unsupported Manifest Version in Chrome
Quick Answer
Chrome shows an unsupported manifest version error when an extension package uses an older extension format that modern Chrome no longer accepts, most commonly Manifest V2. In current Chrome versions, ordinary users usually cannot fix this by changing a simple setting. Reinstalling the same extension, downloading random CRX files, or disabling security protections can create privacy and malware risks. The safer path is to check whether the developer provides a Manifest V3 version, install a maintained alternative from the Chrome Web Store, or use a browser that still supports the extension you need.
Key Takeaways
- This error usually appears before installation, not after an extension is already enabled.
- It often means the extension package uses Manifest V2 or another outdated manifest format.
- Reinstalling the same CRX usually does not solve the underlying compatibility problem.
- Random CRX downloads can expose your browser data and should be avoided.
- The best long-term fix is a maintained Manifest V3 version or a trusted alternative.
Current Status
- Chrome status
- Modern Chrome blocks unsupported manifest formats
- User control
- Ordinary users generally cannot permanently re-enable MV2 installation
- Safer path
- Use an official MV3 update or a maintained alternative
- Last reviewed
- May 19, 2026
Why This Happens
- Chrome extensions use manifest files to declare permissions, scripts, background behavior, and APIs.
- Older Manifest V2 packages may no longer be accepted by modern Chrome.
- The Chrome Web Store itself may block installation of packages using unsupported manifest formats.
- This error happens during installation, not after an extension has been working normally.
- It typically means the extension package has not been updated to the Manifest V3 format.
Common Failed Fixes
Trying to: Download the same extension from a random CRX mirror
Why it does not work: It may be outdated, modified, or malicious.
Safer alternative: Use the Chrome Web Store or the developer's official release page.
Trying to: Enable Developer Mode and load an old unpacked extension
Why it does not work: Developer Mode does not make unsupported APIs compatible with modern Chrome.
Safer alternative: Use an MV3-compatible build.
Trying to: Change Chrome flags to allow legacy MV2 extensions
Why it does not work: Flags are temporary, version-dependent, and may disappear after Chrome updates.
Safer alternative: Treat this only as a short-term data export path, not a fix.
Trying to: Reinstall the same old package repeatedly
Why it does not work: The manifest version remains unsupported regardless of how many times you reinstall.
Safer alternative: Install a maintained MV3 version.
Trying to: Disable browser security protections
Why it does not work: It increases the risk of malicious extensions reading pages, cookies, or credentials.
Safer alternative: Replace the extension with a maintained alternative.
What You Can Do
Check the Chrome Web Store listing for an updated Manifest V3 version of the extension.
Visit the developer's official website or GitHub release page for migration notes.
Search for a maintained alternative from the Chrome Web Store.
Export settings from any old extension package before removing it, if possible.
Consider Firefox as an alternative browser if you need specific MV2 extension functionality.
What Not to Do
- Do not download the same extension from a random CRX mirror.
- Do not enable Developer Mode and load an old unpacked extension as a fix.
- Do not change Chrome flags to allow legacy MV2 extensions as a permanent fix.
- Do not reinstall the same old package repeatedly.
- Do not disable browser security protections to install unsupported extensions.
Frequently Asked Questions
Sources
Sources
- Chrome Manifest V2 Deprecation TimelineGoogle Chrome DevelopersChrome DevelopersPrimary source
Supports: Chrome MV2 deprecation timeline, which Chrome versions disabled MV2, and what extensions are affected
- Manifest V3 Migration GuideGoogle Chrome DevelopersChrome DevelopersPrimary source
Supports: What Manifest V3 is, why it replaced MV2, and what changes extensions must make
- Chrome Web Store Program PoliciesGoogle Chrome DevelopersChrome DevelopersSecondary source
Supports: Why unsupported extension packages may be blocked from the Chrome Web Store