Google Chrome’s next update will mark the end of popular ad blockers
At a glance:\n- Chrome 150 will remove the ExtensionManifestV2Disabled flag, ending a key workaround for MV2 ad blockers.\n- Manifest V3 enforcement in Chrome 150/151 will disable most MV2‑based extensions, including uBlock Origin.\n- Microsoft Edge, Opera, and other Chromium browsers can still support MV2, but Chrome will drop all support by July 2026.\n\n## Manifest V3: the final nail in the ad blocker coffin\nGoogle’s long‑running plan to shift all Chrome extensions to Manifest V3 is now reaching its last stop. The company has removed the “kExtensionManifestV2Disabled” flag from Chromium, a piece of dead code that had allowed users to keep legacy MV2 extensions running. With the flag gone, the final loophole that kept many ad blockers alive has vanished.\n\n## What the change means for users and developers\nChrome 150, slated for release on June 30, 2026, will strip the ExtensionManifestV2Disabled flag. A residual DevTools method will remain, but it requires manual page‑element patching each session, making it impractical for everyday use. The subsequent Chrome 151 release, expected in July 2026, will clear the remaining MV2 flags:\n- ExtensionManifestV2Unsupported\n- ExtensionManifestV2Availability\n- AllowLegacyMV2Extensions\n\nThese removals will render most MV2‑based ad blockers, such as uBlock Origin, non‑functional unless they are rewritten for Manifest V3.\n\n## How Google explains the move\nA Googler quoted in the Chromium commit notes:\n\n> MV2 extensions are no longer allowed in any supported version of Chrome, and we are removing support for them and the associated functionality. We won’t be able to provide / maintain this functionality indefinitely due to the complexity and tech debt, as well as the security risks it entails (we’ve actually found a number of bugs that are specific to MV2 lately).\n\nThe engineer also added that other browsers can continue supporting MV2 if they wish, hinting that Microsoft Edge and Opera may follow suit.\n\n## The broader ecosystem impact\nWhile Chrome will be the first major browser to end MV2 support, the decision could prompt a shift in the ad‑blocking community. Developers will need to migrate to Manifest V3 or abandon their extensions. Users relying on MV2 ad blockers will face a temporary loss of protection until new versions are released.\n\n## Chrome’s new AI‑powered features\nAlongside the extension overhaul, Google is rolling out Gemini to Latin America, Africa, and the Middle East, and adding full Gemini integration and auto‑browse to Chrome for Android. The browser also introduces AI detection for photos, videos, and audio in Search and Chrome, signalling a broader push toward AI‑enhanced browsing.\n\n## Looking ahead\nThe final removal of MV2 support will mark a significant policy shift for Chrome users. As developers scramble to adapt, the ad‑blocking ecosystem may see fragmentation or consolidation. Meanwhile, other Chromium‑based browsers may retain MV2 support, creating a split landscape where Chrome users experience stricter extension policies.
Editorial
SiliconFeed is an automated feed: facts are checked against sources; copy is normalized and lightly edited for
readers.
FAQ
When will Chrome stop supporting Manifest V2 extensions?
Chrome 150, scheduled for release on June 30, 2026, will remove the ExtensionManifestV2Disabled flag. The final removal of all MV2 flags will occur in Chrome 151, expected in July 2026.
Which ad blockers will be affected by the Manifest V3 transition?
Popular ad blockers built on Manifest V2, such as uBlock Origin, will no longer function in Chrome after the 150/151 releases, unless they are updated to comply with Manifest V3.
Will other browsers still support Manifest V2 extensions?
Yes, Microsoft Edge, Opera, and potentially other Chromium-based browsers can continue to support MV2 extensions if they choose to, as Google’s change is specific to Chrome.
More in the feed
Prepared by the editorial stack from public data and external sources.
Original article