Manifest V2 Removal: What Edge Users Face Now

Manifest V2 extension removal means that Microsoft Edge will stop loading extensions built on the older Manifest V2 (MV2) framework, forcing users to switch to Manifest V3 (MV3) versions or lose functionality. If you use Edge extensions like ad blockers, password managers, or productivity tools, this change affects which extensions work, how they behave, and what you need to do to keep your browser secure. Below is a detailed look at what this transition means, why it’s happening, and how to adapt.

Background: Why Manifest V2 Is Being Removed

Manifest V2 is the extension architecture that Chrome, Edge, and other Chromium-based browsers have used since 2012. It allowed extensions to request broad permissions, including the ability to read and modify any webpage, execute arbitrary code, and access all browsing data. While powerful, this flexibility became a security liability. Malicious extensions could abuse these permissions to steal credentials, inject ads, or track users without clear consent.

In 2019, Google announced Manifest V3 as a replacement, designed to improve privacy, performance, and security. MV3 restricts certain capabilities—most notably, it replaces background pages with service workers, limits remote code execution, and introduces declarative net request rules for content blocking. Microsoft Edge, being built on Chromium, has followed Google’s timeline, gradually phasing out MV2 support. As of 2024, Edge has begun disabling MV2 extensions for most users, with full removal expected by 2025.

How the Removal Works in Edge

Microsoft Edge is rolling out the MV2 removal in stages. Initially, users see a warning banner in the Extensions hub (edge://extensions) stating that an extension is no longer supported. After a grace period, the extension is automatically disabled. You can still re-enable it temporarily via a developer mode toggle, but this is a stopgap, not a long-term solution. Eventually, Edge will block MV2 extensions entirely, and they will disappear from the Microsoft Edge Add-ons store.

The transition is happening automatically for most users. When you update Edge, the browser checks installed extensions against a list of supported manifest versions. If an extension is MV2, it’s flagged. Some extensions may have already been updated to MV3 by their developers, so you might not notice any change. However, if a developer hasn’t updated, the extension will stop working.

What This Means for Your Existing Extensions

If you rely on extensions that haven’t migrated to MV3, you’ll need to find alternatives or accept the loss. Here’s what typically happens:

• Ad blockers: Popular blockers like uBlock Origin have MV3 versions, but they may have fewer filter list options or use a different blocking mechanism. Some advanced features, like cosmetic filtering, still work but with limitations.
• Password managers: Most major password managers (e.g., LastPass, Dashlane) already support MV3, so you’re unlikely to see issues.
• Productivity tools: Extensions that inject scripts into pages (e.g., Grammarly, Honey) have adapted, but some niche tools may not have the resources to update.
• Developer tools: Extensions that rely on cross-origin requests or remote code execution are hardest hit. Some may be discontinued.

To check your extensions, go to edge://extensions and look for any that show a warning. If an extension is disabled, click “Details� to see if a MV3 version is available. If not, search the Edge Add-ons store for a replacement.

How to Choose a Replacement Extension

When selecting a new extension, prioritize those that are actively maintained and clearly labeled as MV3. Here are steps to evaluate:

1. Visit the extension’s page in the Edge Add-ons store or Chrome Web Store (Edge supports Chrome extensions).
2. Check the “Updated� date—if it’s older than a year, the developer may have abandoned it.
3. Read the permissions list. MV3 extensions should request only what they need. Be wary of extensions asking for “Read and change all your data on all websites� unless it’s essential.
4. Look for a “Manifest V3� mention in the description or support page. If unclear, search the extension’s name plus “MV3� to see if the developer announced the update.
5. Test the extension on a few sites to ensure it works as expected. Some MV3 versions have subtle differences, like slower response times.

Remember, not all extensions need to be replaced. If an extension is disabled and you can’t find a MV3 version, consider whether you truly need it. Removing unused extensions improves browser performance and security.

Common Problems and Workarounds

Users often encounter a few issues during the transition:

• Extension disappeared entirely: If you don’t see the extension in your list, it may have been removed by Edge. Reinstall it from the store—if it’s no longer available, you’ll need an alternative.
• Ad blocker stops blocking ads: MV3 ad blockers use declarative net request rules, which have a limit (currently 30,000 rules per extension). Some filter lists exceed this, so you may need to enable “Optimalâ€� filter lists instead of “Complete.â€�
• Extension works but is slower: Service workers are event-driven and can be unloaded when idle. This may cause a slight delay when the extension first interacts with a page. This is normal.
• Developer mode toggle doesn’t work: If you try to enable a disabled MV2 extension via developer mode, Edge may still block it after a restart. This is a temporary measure, not a permanent fix.

If you’re having trouble, check the extension’s support page or GitHub repository. Many developers post migration guides. You can also ask in the Edge community forums, but avoid unofficial “fix� scripts that could compromise security.

Comparison: MV2 vs. MV3 in Practice

For end users, the differences are subtle but noticeable:

• Permissions: MV3 extensions are more transparent about what they access. You’ll see fewer “on all sitesâ€� prompts.
• Performance: MV3 extensions are generally lighter because they use service workers instead of persistent background pages. This can reduce memory usage.
• Capabilities: Some features are gone. For example, extensions can no longer modify network requests in real time; they must use declarative rules. This affects advanced ad blocking and privacy tools.
• Security: MV3 is safer because it prevents extensions from loading remote code, which was a common attack vector.

For most users, the transition is seamless. The biggest impact is on power users who rely on highly customizable extensions. If you’re one of them, you may need to accept a slightly less flexible experience.

Safety and Security Considerations

Removing MV2 is a security improvement, but you should also take steps to protect yourself:

• Update your extensions: Ensure all installed extensions are up to date. MV3 versions often include security patches.
• Review permissions: After the transition, revisit your extension permissions. Remove any that seem excessive.
• Beware of fake replacements: Scammers create malicious extensions that mimic popular ones. Only download from the official Edge Add-ons store or Chrome Web Store, and check the developer’s name.
• Use Edge’s built-in features: Edge has native ad blocking, password manager, and tracking prevention. You may not need as many extensions as before.

If you’re concerned about losing a specific extension, back up its settings or data before it’s disabled. Some extensions allow export, but this isn’t universal.

Alternatives to Affected Extensions

If your favorite extension doesn’t have a MV3 version, consider these alternatives:

• Ad blocking: Use Edge’s built-in ad blocker (Settings > Privacy > Ad blocking) or switch to a MV3-compatible blocker like AdGuard or Brave’s Shields (if you use Brave).
• Password management: Use Edge’s built-in password manager or switch to a dedicated MV3-compatible manager like Bitwarden.
• Productivity: Many features (e.g., dark mode, tab management) are now built into Edge. Check the browser’s settings before installing an extension.
• Developer tools: For web development, use Edge’s DevTools (F12) instead of extensions that inject scripts.

Remember, you can also use Edge’s “Collections� and “Sleeping Tabs� features to reduce the need for extensions.

Frequently Asked Questions

Will my Edge browser stop working if I have MV2 extensions?

No, the browser itself will work fine. Only the MV2 extensions will be disabled. You can still browse, use built-in features, and install MV3 extensions.

Can I force Edge to keep MV2 extensions?

There is no official way to permanently keep MV2 extensions. You can temporarily enable them via developer mode, but Edge will eventually block them. Using third-party patches is risky and not recommended.

Are all ad blockers affected?

Most ad blockers have MV3 versions, but they may have fewer features. For example, uBlock Origin’s MV3 version has a rule limit, but it still blocks most ads. Some advanced filtering may be less effective.

How do I know if an extension is MV2 or MV3?

Go to edge://extensions, click “Details� on an extension, and look for “Manifest version� in the “Permissions� or “About� section. If it says “2�, it’s MV2. You can also check the extension’s store page for “Manifest V3� in the description.

Will my extension data (like passwords or settings) be lost?

Usually not. Most extensions store data in your browser profile or cloud. When you install a MV3 replacement, you can often import settings. However, some extensions may have separate data stores, so back up important data before uninstalling.

Is there a way to use Chrome extensions in Edge after MV2 removal?

Yes, Edge supports Chrome Web Store extensions. You can install MV3 extensions from there. Just go to edge://extensions, enable “Allow extensions from other stores,� and then install from the Chrome Web Store.

Related

• Workday Alternatives: AI ERP for Mid-Sized Businesses
• Generative AI in Games: What It Means for Artists and Writers
• Ollama vs LM Studio: Which Is Better for Local AI?