Your Chrome Extensions Broke? How to Fix the Manifest V2 Purge

Chrome extensions not working? It's the Manifest V2 purge

If some of your Chrome extensions suddenly stopped working this year, you're not imagining it. On August 31, 2026, Google permanently purged Manifest V2 extensions from the Chrome Web Store. They can't come back — not from official sources, not with a reinstall, not with a setting. If your favorite ad blocker or privacy tool went dark, the Manifest V2 purge is almost certainly why.

Here's what's happening, how to check which of your extensions are affected, and what to do about each one.

What Manifest V2 was, and why Google killed it

Every Chrome extension ships with a file called manifest.json that declares what the extension is allowed to do. Manifest V2 was the old format, and it was powerful in ways that worried Google: MV2 extensions could download and run code from outside servers after installation. That's a security hole you could drive a truck through — an extension could ship clean, pass review, then pull down malicious code later.

Manifest V3 bans remotely hosted code outright. All executable code must be packaged with the extension and vetted through Web Store review. The tradeoff is capability: MV2 let ad blockers use nearly unlimited dynamic rules and inject scripts deep into pages. MV3 forces them into a static, rule-based model (declarativeNetRequest) with strict limits. Google raised those limits after developer backlash, and for most browsing the MV3 blockers work fine — but power users with huge custom filter lists will feel the difference.

Step 1: audit your extensions

Open chrome://extensions in your address bar. Look for extensions that are disabled or flagged with a badge saying they are no longer supported. Those are your MV2 casualties.

Want to confirm the manifest version yourself? Turn on Developer mode (top right of the extensions page) — each card now shows the extension's ID. Then open chrome://version, find your Profile Path, and open that folder in your file browser. Inside the Extensions folder, open the folder matching the extension's ID, then the newest version folder, and open manifest.json in a text editor. Look for the manifest_version line: a 2 confirms it's a dead MV2 extension; a 3 means something else is wrong. Read the file only — don't edit or delete anything in there.

Step 2: find replacements for the ones that matter

For each dead extension, check whether the same developer ships an MV3 version:

• uBlock Origin (full) → switch to uBlock Origin Lite, the official MV3 build. Less powerful, fully functional for normal browsing.
• Other ad blockers → AdGuard and most major blockers have MV3 versions now.
• Privacy tools → most have migrated; check the developer's site for an updated release.
• Niche utilities with no MV3 version → search the Web Store for alternatives, or check whether you actually still need it. Auditing your app permissions taught us the same lesson on phones: half the tools we install are ones we forgot about.

If your workplace relied on the ExtensionManifestV2Availability enterprise policy to keep MV2 extensions alive, heads up: those temporary exemptions are expiring in upcoming Chrome milestones. Get the migration done before your IT department's workaround stops working.

Step 3: consider the nuclear option — Firefox

Here's the thing nobody at Google will tell you: Mozilla committed to keeping Manifest V2 support in Firefox. If your workflow depends on extensions that can't survive MV3 — deep cosmetic filtering, custom scriptlets, massive filter lists — Firefox is the cleanest escape route, and your extensions will work exactly as they did.

Switching browsers in 2026 is less painful than it sounds: Firefox imports bookmarks, passwords, and history from Chrome in a few clicks. Pair it with the free privacy tools stack and you're arguably better off than before.

The bottom line

The purge already happened — there's no going back, and the sketchy workarounds involving command-line flags and old Chrome versions are temporary at best and insecure at worst. Audit your extensions today, replace what you can, and for the irreplaceable ones, give Firefox a serious look. The extension you depended on isn't coming back to Chrome; the sooner you move on, the sooner you stop noticing.