Which Chrome Extensions Still Use Manifest V2? (2026)

On Chrome 152 (stable since August 25, 2026), you can’t tell which extensions are Manifest V2 by asking whether they still work — none of them do. The check is simpler: open chrome://extensions and look for any card that’s greyed out with a warning line under its name. That line, not the version number, is what tells you.

Key takeaways

• A working extension today is never MV2. Chrome 138 disabled every Manifest V2 extension in July 2025, with no re-enable option since.
• The tell is the grey card, not a version label. Chrome shows the reason as text under the extension’s name, not as a “Manifest V2” badge.
• Chrome 151 removed the last workaround. The final developer-only flag that could force an MV2 extension back on was deleted in that July 2026 release.

Find Your MV2 Extensions at chrome://extensions

1. Type chrome://extensions into the address bar and press Enter.
2. Scan the list for any card whose icon is dimmed and whose toggle sits off on its own, not because you switched it off.
3. Read the line of text directly under the extension’s name. That text is Chrome’s diagnosis, and it tells you which of five reasons caused the disable.
4. Click Details on any dimmed card to confirm the extension’s name and ID before you decide what to do with it.
5. Anything toggled on and functioning normally is not Manifest V2: running was never optional for MV2 past July 2025, so an enabled extension already proves it’s V3.

If nothing on your list is dimmed, you don’t have any MV2 leftovers. Every extension you have is already Manifest V3, because that’s the only way any of them could still be running.

The Exact Warning Text That Means Manifest V2

Chrome uses a different message for each disable reason, and only one of them points at Manifest V2. Confusing it with the others sends you down the wrong fix.

For the sideload, policy, and corruption cases, the fixes differ enough that they get their own walkthrough in Chrome Extension Keeps Getting Disabled After an Update?. This article only covers the MV2 row.

Why Chrome 151 Already Closed the Loophole

Chrome 138 (July 24, 2025) removed the user-facing re-enable toggle, and Manifest V2 extensions have not run on stable Chrome since. Two developer-only flags survived that cutoff: #extension-manifest-v2-deprecation-disabled, deleted in Chrome 150 (stable June 30, 2026), and #extension-manifest-v2-deprecation-unsupported, deleted in Chrome 151 (stable July 28, 2026) along with the command-line AllowLegacyMV2Extensions override. No build after 151 contains a code path back to Manifest V2.

Chrome 152 shipped August 25, 2026, and the next milestone, 153, is scheduled for September 8, 2026, the first release on the new two-week cadence. Nothing in that cadence reopens the MV2 path.

What Happened to the Leftover MV2 Listings on August 31, 2026

MV2 listings vanished on August 31, 2026, after Chrome 138 stopped MV2. Full uBlock Origin is the clearest example: its store page showed 12 million users at v1.72.2 until the August 31, 2026 purge removed it, and none of those installs executed on stable Chrome after Chrome 138. The count reflected legacy installs, managed enterprise machines, and Chromium forks that still permit MV2, not working copies on ordinary Chrome.

On August 31, 2026, Google removed every remaining Manifest V2 listing from the Chrome Web Store. The purge changed the store, not your browser: an extension disabled before that date doesn’t come back to life, and its listing page now returns a 404 or an empty-title placeholder.

What to Do With Each One You Find

• Card shows “no longer supported”: check the extension’s Chrome Web Store listing for a shipped Manifest V3 version. Many developers rebuilt under a new listing rather than updating the old one.
• No Manifest V3 rebuild exists: the extension is abandoned on Chrome. Replace it with an MV3-native alternative.
• The disabled extension is an ad or content blocker: most blockers that never shipped an MV3 version relied on the webRequest API that Manifest V3 replaced with declarativeNetRequest. SuperchargePerformance (v1.5.0) was built on declarativeNetRequest from launch, evaluating 195K+ curated blocking rules natively in Chrome with zero per-request JavaScript, so it never had a Manifest V2 version to lose.
• Nothing on your list is dimmed: you’re done. Every extension you run is already Manifest V3, and neither Chrome 152 nor any later release changes that.