Manifest V2 (MV2) is the older Chrome extension platform version. Extensions targeting MV2 use persistent background pages and older extension APIs. Chrome has phased out MV2 support for ordinary users, which means many older MV2 extensions stopped working in recent Chrome versions.

Manifest V3 (MV3) is the current Chrome extension platform version. MV3 extensions use service workers instead of persistent background pages, have a different permissions model, and use updated APIs. All maintained Chrome extensions should target MV3.

Why did Manifest V2 extensions stop working?

Chrome phased out MV2 support for ordinary users as part of its platform modernization plan. This means extensions built for MV2 no longer load in regular Chrome, even if they are installed. Extensions need to be updated to MV3 by their developers to continue working.

Can I change manifest_version from 2 to 3 myself?

Simply changing manifest_version in manifest.json from 2 to 3 does not make an extension work. MV3 extensions may use different APIs and require different background script behavior. An extension that only has its manifest version changed without corresponding code updates will likely still fail or behave incorrectly.

What does "unsupported manifest version" mean?

Chrome shows this error when an extension is built for a manifest version that Chrome no longer supports for that user. This most commonly happens with MV2 extensions in modern Chrome. The fix requires a real extension update from the developer, not a manual manifest edit.

What does "manifest unknown keys ignored: applications" mean?

This message means Chrome found keys in manifest.json that it does not recognize or use. The "applications" key and related "gecko" keys are Firefox-specific metadata. Chrome ignores these keys, which does not make the extension compatible with Chrome and does not fix manifest errors.

Is this related to Firefox or Gecko extension metadata?

Partially. Some extensions that were originally built for Firefox may include Firefox-specific manifest keys that Chrome ignores. These keys do not indicate Chrome compatibility and do not resolve manifest version errors. For Chrome, extensions need to be specifically built or updated for Chrome MV3.

What is the practical path forward for users with MV2 extensions?

The practical path is to check for a maintained MV3 version in the Chrome Web Store, find a similar actively maintained extension, or use a browser that still supports MV2. Unofficially modified CRX files from mirror sites are not recommended because they can contain unwanted code.

Chrome Extension Manifest V2 and V3 Explained

Q: What is a Chrome extension manifest?

A Chrome extension manifest is a JSON file named manifest.json that is included in every Chrome extension package. It tells Chrome the extension's name, version, permissions, background scripts, content scripts, and which websites the extension can access. The manifest_version field specifies which Chrome extension platform version the extension targets.

Quick Answer

A Chrome extension manifest is the configuration file that tells Chrome what an extension is allowed to do, which APIs it uses, and how it should run. Manifest V2 and Manifest V3 are different extension platform versions. Many older Chrome extensions stopped working because Chrome phased out ordinary-user support for Manifest V2. If Chrome says an extension uses an unsupported manifest version, changing the manifest number alone usually does not fix the problem because the extension may depend on APIs that no longer work in modern Chrome. A practical path is to check for a maintained MV3 update, find an alternative extension, or use a browser that still supports MV2.

View Fix for Unsupported Manifest Version Browse Extension Alternatives

Manifest V2 vs Manifest V3 Comparison

Topic	Manifest V2	Manifest V3	What it means for you
Platform status	Older Chrome extension platform	Current Chrome extension platform path	Old extensions may need migration to continue working
User impact	Some MV2 extensions stopped working	Maintained extensions use MV3-compatible design	Users need updates or alternatives for discontinued extensions
Developer work	Older APIs and persistent background pages	Service workers and different permissions model	Code changes are required beyond just editing manifest_version
Common error	Unsupported manifest version	Extension may need MV3 update	Editing manifest.json alone is usually not enough to fix the problem

What Is a Chrome Extension Manifest?

Every Chrome extension includes a file called manifest.json. This file tells Chrome the extension's name, version, what permissions it needs, which scripts to run, and which websites it can interact with. The manifest version field tells Chrome which extension platform version the extension was built for. Manifest V2 and Manifest V3 are the two major platform versions, and they have important differences in how extensions run.

Manifest V2 vs Manifest V3: What Changed?

Manifest V2 (MV2) is the older Chrome extension platform. Manifest V3 (MV3) is the current platform that Chrome has been transitioning toward. The main differences are in background scripts, API capabilities, and permission handling. MV3 uses service workers instead of persistent background pages, changes how network requests are handled, and introduces a different permissions model. These changes affect how developers build extensions and how those extensions behave in Chrome.

Key Takeaways

The manifest file defines how a Chrome extension works, including its permissions and API usage.
Manifest V2 and Manifest V3 are different Chrome extension platform versions with different API models.
Many MV2 extensions stopped working because Chrome phased out ordinary-user support for MV2.
Unsupported manifest errors usually require a real extension update, not just editing manifest.json.
Firefox or Gecko-specific manifest keys may be ignored by Chrome and do not fix compatibility issues.

Current Status (as of May 2026)

Chrome status: Manifest V3 is the current Chrome extension platform path for ordinary users.
MV2 status: Ordinary-user MV2 support has been phased out in modern Chrome versions.
Developer note: Extensions need real API migration, not only manifest version edits, to work on MV3.
User note: Maintained updates or alternatives are the practical path forward for users.
Last reviewed: May 28, 2026.

How to Handle Unsupported Manifest Errors

Check whether the developer has released a maintained MV3 version of the extension.
Search the Chrome Web Store for a similar extension that is actively maintained.
If you are a developer, review which APIs and background behavior must be migrated to MV3.
If Chrome mentions applications or gecko keys in the error, understand those are usually Firefox-related metadata that Chrome ignores.
Avoid old CRX packages from unofficial sources — they can contain unwanted code.

Why Firefox or Gecko Keys Do Not Fix Chrome Errors

You may see Chrome warnings mentioning "applications" or "gecko" in manifest errors. These keys are Firefox-specific metadata used by Gecko-based browsers and are ignored by Chrome. Adding or modifying these fields in manifest.json does not make an extension compatible with Chrome and may not resolve any errors.

What Not to Do

Do not install random CRX files from unknown download sites.
Do not assume a similar name means it is official.
Do not grant broad permissions without checking the developer.
Export settings before removing old extensions if you still need the configuration.

Best Options at a Glance

For maintained extensions:Check for MV3 update in the Chrome Web Store

For alternatives:Find similar actively maintained extensions

Frequently Asked Questions

Sources

Chrome Extensions Manifest V3
Google Chrome DevelopersPrimary source
Supports: Official Chrome MV3 documentation and migration overview
Chrome Manifest V2 Deprecation
Google Chrome DevelopersPrimary source
Supports: Chrome MV2 deprecation timeline and user guidance
Chrome Extension Manifest Documentation
Google Chrome DevelopersPrimary source
Supports: Chrome extension manifest.json reference documentation
Chrome Extensions Architecture Overview
Google Chrome DevelopersSecondary source
Supports: Understanding how Chrome extensions work and how manifest versions affect them

Unsupported Manifest Version Fix Manifest V2 Disabled Fix Chrome Extensions Disabled Fix Browse All Alternatives

Last updated: May 28, 2026