Chrome Manifest V2 Removal: What Happened and How to Replace Extensions

Chrome Manifest V2 removal is now complete for current Chrome releases. Google disabled Manifest V2 extensions for regular users with Chrome 138 on July 24, 2025, removed the temporary enterprise ExtensionManifestV2Availability policy with Chrome 139, and removed all remaining Manifest V2 listings from the Chrome Web Store on August 31, 2026. If an extension stopped working because it depended on Manifest V2, the normal fix today is to install the developer’s Manifest V3 version, choose a maintained replacement, or move the workflow to another supported tool or browser.

Old instructions that tell users to re-enable Manifest V2 with a Chrome flag, registry setting or enterprise policy are no longer valid for current Chrome. Keeping Chrome 138 or an even older browser just to preserve one extension is also a poor long-term solution because it leaves the browser without normal security and compatibility updates.

What Is a Chrome Extension Manifest?

Every Chrome extension contains a manifest.json file. It describes the extension’s name, version, permissions, content scripts, background behavior, browser APIs and security rules. One required field is the manifest version.

"manifest_version": 3

Manifest V2 and Manifest V3 are generations of Chrome’s extension platform. They are not versions of Chrome itself.

What Was Manifest V2?

Manifest V2 powered Chrome extensions for many years. It allowed patterns such as persistent background pages, broad host permissions and blocking network-request modification through webRequest. Those capabilities enabled powerful tools, including content blockers, download managers, developer utilities and automation extensions.

That does not mean every Manifest V2 extension was unsafe. Google’s migration was a platform redesign intended to tighten security, privacy and performance controls—not a claim that all MV2 software was malicious.

What Changed With Manifest V3?

Manifest V3 changes several core extension behaviors. Long-lived background pages are replaced by event-driven extension service workers. Remotely hosted executable code is restricted. Host permissions are handled more explicitly. For network filtering, Google emphasizes declarativeNetRequest instead of giving ordinary extensions the same webRequestBlocking capability used by many MV2 tools.

The webRequest API itself still exists in Manifest V3 for observing traffic. What changed for normal extensions is the blocking permission: Google says webRequestBlocking is unavailable to most MV3 extensions, while policy-installed enterprise extensions are a special case.

Why Did Google Remove Manifest V2?

Google says Manifest V3 is intended to improve extension security, privacy and performance. The company specifically points to eliminating remotely hosted executable code, reducing persistent background execution and replacing some blocking network interception with declarative rules processed by the browser.

Developers and privacy communities have criticized parts of the transition, especially limitations and complexity around content filtering, dynamic rules and service-worker lifecycles. Google expanded Manifest V3 over time in response to developer feedback. The result is not that ad blockers disappeared, but that some MV2 features cannot be reproduced identically under Chrome’s MV3 rules.

Manifest V2 Removal Timeline

What Happened to Existing Manifest V2 Extensions?

On Chrome 139 and later, normal Manifest V2 extension operation is no longer supported. On an old Chrome 138-or-earlier installation, an already-installed MV2 extension may technically remain installed, but after the August 31, 2026 store removal it cannot receive Chrome Web Store updates and cannot be reinstalled from the store if removed.

That is not a safe preservation strategy. The extension becomes frozen while the browser is also frozen on an old security baseline.

Can You Re-enable Manifest V2 in Chrome?

Not in normal current Chrome. Older guides may mention a Chrome flag, a registry preference or the enterprise ExtensionManifestV2Availability policy. Those instructions belong to earlier phases of the migration. Chrome 138 ended ordinary user re-enablement, and Chrome 139 removed the enterprise availability policy.

Sideloading an old MV2 package also does not restore runtime support that Chrome has removed. It adds new risks because unofficial .crx packages can be outdated, modified or malicious and will not receive normal Web Store updates.

How to Tell Whether an Extension Used Manifest V2

1. Open chrome://extensions and identify the extension name and publisher.
2. Check the developer’s official website and current Chrome Web Store listing for an updated version or migration notice.
3. For technical inspection, enable Developer mode only to inspect details—not to install untrusted code.
4. If you have legitimate access to the extension source, open manifest.json.
5. Look for "manifest_version": 2 or "manifest_version": 3.

Ordinary users should not download old extension packages from random mirrors just to inspect or restore them.

How to Replace a Manifest V2 Extension That Stopped Working

1. Identify the exact extension and developer. Avoid similarly named clones.
2. Visit the developer’s official website. Look for an MV3 migration notice or new product name.
3. Search the Chrome Web Store for the official replacement.
4. Verify publisher identity and website domain.
5. Compare permissions. A replacement should request access that makes sense for its function.
6. Export old settings first if the extension still exposes an export function.
7. Install the supported replacement.
8. Import settings only if the developer documents compatibility.
9. Test critical workflows such as filters, downloads, password filling or automation.
10. Remove the obsolete extension after confirming the replacement works.
11. Review site access and permissions after installation.

How to Choose a Safe Chrome Extension Alternative

Check the developer identity, official website, recent update history, privacy disclosure, permissions and independent reputation. Open-source code can improve transparency, but open source alone is not a guarantee of safe distribution. A high review count is also not enough: ownership can change and malicious updates can occur.

Be especially cautious with password managers, download managers and extensions that can “read and change all your data on websites.” Those permissions may be legitimate for the extension’s purpose, but the publisher should be trustworthy and the access should be necessary.

For broader security hygiene, see FrediTech’s device security best-practices guide and advanced cybersecurity guide.

What Manifest V3 Means for Ad Blockers

Manifest V3 did not eliminate ad blocking. It changed how Chrome extensions can perform network filtering. Many MV2 blockers relied heavily on blocking webRequest; Chrome MV3 instead emphasizes declarative rule sets through declarativeNetRequest, which has static, dynamic and session-rule limits.

A useful current example is uBlock Origin. The traditional uBlock Origin extension is Manifest V2 and was removed from the Chrome Web Store with the August 31 cutoff. Raymond Hill’s official project provides uBlock Origin Lite as an MV3-based alternative, but the developer explicitly says it is not identical to the traditional uBlock Origin and is not automatically substituted for it.

That distinction is safer than installing a similarly named third-party blocker. Users who choose uBlock Origin Lite should use the official project/Web Store path and understand that some advanced filtering behavior differs.

Can Extension Settings Be Transferred?

Sometimes. A developer may migrate settings automatically, provide JSON export/import, sync preferences to an account or require manual recreation. Unrelated extensions should not be expected to understand each other’s configuration. Export settings before removing an old extension whenever the developer provides a supported export mechanism.

What If There Is No Manifest V3 Replacement?

Look for another maintained Chrome Web Store extension, a built-in Chrome feature, the service’s desktop application, a web application or operating-system functionality. If the workflow genuinely depends on capabilities Chrome no longer provides, another actively supported browser may be appropriate—but only if that browser and extension are actually maintained.

Can You Use the Extension in Firefox, Edge, Brave or Opera?

Browser extension policies are not identical even when browsers share Chromium code. Last checked: September 28, 2026.

Vivaldi supports Chrome Web Store extensions and has a built-in tracker/ad blocker, but FrediTech did not find a sufficiently current first-party 2026 statement defining a precise MV2 cutoff. This guide therefore avoids claiming an exact Vivaldi MV2 status.

For related browser-security context, see FrediTech’s Firefox ad-blocking guide and Chrome OS setup guide.

Should You Downgrade Chrome to Keep Manifest V2?

No for normal long-term use. Old Chrome releases miss security patches, browser fixes and compatibility changes. Websites can also break as APIs and TLS/security requirements move forward. An obsolete browser plus an extension that can no longer receive Web Store updates compounds the risk.

Developers: How to Migrate an Extension to Manifest V3

Migration is more than changing one number in manifest.json. Google’s current migration documentation groups the work into manifest changes, service-worker migration, API updates, network-request migration and extension-security changes.

• Change the manifest to version 3 and review renamed/changed keys.
• Replace background pages with an extension service worker.
• Persist state with extension storage instead of assuming global variables stay alive.
• Register event listeners synchronously at the top level.
• Convert timers to alarms where appropriate.
• Review webRequestBlocking usage and migrate suitable cases to declarativeNetRequest.
• Move DOM-dependent background work to appropriate pages/offscreen documents.
• Review host permissions and optional permissions.
• Move executable code into the extension package and remove remotely hosted executable code.
• Update the extension Content Security Policy.
• Use chrome.scripting for script injection where required.
• Test installation, updates, incognito behavior and enterprise deployment.

Background Pages vs Service Workers

Manifest V2 extensions could keep background pages alive for long periods. Manifest V3 uses extension service workers that wake for events and can terminate when idle. Developers cannot assume global variables remain available indefinitely. State should be saved to appropriate storage, listeners should be registered synchronously, and long-running behavior must be redesigned around the service-worker lifecycle.

webRequest vs declarativeNetRequest

Chrome still allows MV3 extensions to observe requests with webRequest. What most extensions lose is the old webRequestBlocking permission. declarativeNetRequest lets an extension provide rules that Chrome evaluates inside the browser to block, allow, redirect or modify requests without sending each request through extension JavaScript.

Google argues this reduces access to sensitive browsing data and lowers performance overhead. Content-blocker developers have argued that declarative rules can be less flexible for some advanced filtering patterns, which is why MV3 blockers may not behave exactly like their MV2 predecessors.

Remote Code Restrictions

Manifest V3 Chrome Web Store extensions must package executable extension logic locally. An extension can still contact servers and download data or configuration, but it cannot simply fetch arbitrary remote JavaScript and execute it as extension code. That distinction allows cloud-backed extensions to work while making the executable code subject to store review.

What IT Administrators Should Do Now

• Inventory business-critical extensions, IDs and versions.
• Identify remaining workflows that depended on MV2.
• Deploy official MV3 updates or replacement software.
• Test authentication, downloads, filtering, automation and companion-app integration.
• Review enterprise allowlists/blocklists and required permissions.
• Remove obsolete ExtensionManifestV2Availability configuration.
• Communicate replacement steps before removing old tools from managed profiles.
• Use Chrome Enterprise reporting to track extension inventory and risky permissions where available in the organization’s management setup.

Is Manifest V3 More Secure?

It introduces meaningful security controls, especially around remotely hosted executable code, background execution and permission handling. But Manifest V3 does not automatically make every extension trustworthy. A malicious or compromised MV3 extension can still abuse permissions it legitimately receives.

Users should continue checking publisher identity, permissions, privacy practices, update history and ownership changes.

What Chrome Users Should Do Today

1. Keep Chrome updated.
2. Open chrome://extensions.
3. Identify disabled or abandoned extensions.
4. Visit the original developer’s official site.
5. Find the official MV3 update or replacement.
6. Verify publisher identity and permissions.
7. Export settings before removal where possible.
8. Install and test the maintained replacement.
9. Reapprove only the website permissions the new extension needs.
10. Remove obsolete extensions once migration is complete.

Troubleshooting Replacement Extensions

If a replacement does not work, update Chrome and the extension, restart Chrome, check site-access permissions, review the developer’s migration notes and confirm any required desktop companion app is also current. Incognito permission is not automatically carried to a replacement extension and may need to be re-enabled manually.

If settings fail to migrate, restore only from a backup format documented by the developer. Do not disable Chrome security protections or install a random archived CRX as a workaround.

Final Takeaways

Chrome’s Manifest V2 transition is over for current Chrome, not merely approaching. Chrome 138 ended normal user re-enablement, Chrome 139 removed the enterprise availability policy and the Chrome Web Store removed the remaining MV2 listings on August 31, 2026.

For users, the safest response is straightforward: keep the browser current and move essential workflows to maintained extensions. For developers, migration requires real architectural work around service workers, request handling, permissions and packaged code. For organizations, the priority is inventory and controlled replacement rather than preserving an obsolete browser branch.

Frequently Asked Questions

Is Manifest V2 still supported in Chrome?

No. Current Chrome releases do not provide normal Manifest V2 extension support.

When did Chrome disable Manifest V2?

Chrome 138 disabled Manifest V2 everywhere for regular users on July 24, 2025. Chrome 139 removed the enterprise transition policy.

Why did my Chrome extension stop working?

If it still used Manifest V2, current Chrome can no longer run it normally. Check the developer’s official site for an MV3 update or replacement.

Can I turn Manifest V2 back on?

Not through the old user or enterprise mechanisms in current Chrome.

Can I reinstall an old Manifest V2 extension?

Not from the Chrome Web Store after the August 31, 2026 removal. Unofficial archived packages are risky and do not restore removed Chrome support.

Do ad blockers still work with Manifest V3?

Yes, but MV3 blockers can have different filtering capabilities from older MV2 blockers.

Does uBlock Origin still work in current Chrome?

The traditional uBlock Origin is Manifest V2 and was removed from the Chrome Web Store. Its developer offers uBlock Origin Lite as an MV3 alternative, but it is not feature-identical.

Is it safe to use Chrome 138 to keep an old extension?

It is not recommended. Staying on an obsolete browser means missing normal security and compatibility updates.

Can developers convert Manifest V2 extensions to Manifest V3?

Yes, but complex extensions may require substantial redesign around service workers, request handling, permissions and remote-code restrictions.

Does Microsoft Edge still support Manifest V2?

Microsoft is following a separate timetable. Consumer deprecation began in 2026, while enterprise deprecation is expected to begin in early 2027.

Does Firefox support Manifest V2-style capabilities?

Firefox’s WebExtensions implementation differs from Chrome. Mozilla still documents blocking webRequest capabilities that Chrome MV3 does not provide to ordinary extensions, so extension behavior can differ between browsers.

Sources and Further Reading

• Chrome for Developers — Manifest V2 support timeline
• Chrome for Developers — Manifest V3 migration guide
• Chrome for Developers — What changed in Manifest V3
• Chrome for Developers — webRequest API
• Microsoft Learn — Edge Manifest V3 migration timeline
• MDN — Firefox/Chrome webRequest differences
• uBlock Origin project — Chrome Manifest V2 transition