Google Chrome Manifest V3 Transition and the End of MV2 Ad Blockers

Google Chrome is finalizing its transition to Manifest V3 (MV3), a move that removes the final technical loopholes allowing Manifest V2 (MV2) extensions to function. This transition effectively ends support for many popular ad blockers, including the original uBlock Origin, as Google removes the flags that power users previously used to bypass MV2 restrictions.

Chrome 150 and 151: The Final Removal of MV2 Support

Google is implementing a two-stage removal process to eliminate all remaining Manifest V2 functionality from the browser. This removes the "dead code" associated with the legacy system to reduce technical debt and security risks.

  • Chrome 150 (Expected June 30, 2026): This version will remove the ExtensionManifestV2Disabled flag. This was the primary technical workaround that allowed power users to continue running MV2 extensions. While a limited DevTools method remains, it requires manual patching of page elements per session and is not viable for daily use.
  • Chrome 151 (Expected July 2026): This version will remove all remaining MV2-related flags, including ExtensionManifestV2Unsupported, ExtensionManifestV2Availability, and AllowLegacyMV2Extensions.

According to a Google engineer, MV2 extensions are no longer permitted in any supported version of Chrome. The engineer cited the complexity of maintaining the legacy code and the discovery of several bugs specific to MV2 as primary drivers for the removal.

Impact on Chromium-Based Browsers

Because Chrome is built on the Chromium open-source project, these changes impact the broader ecosystem. While Google noted that other browsers can choose to continue supporting MV2 if they wish, industry reports suggest that Microsoft Edge and Opera are likely to follow Google's lead in disabling these extensions.

Technical Trade-offs: Security vs. Ad Blocking

The shift to Manifest V3 introduces a new permissions structure that changes how extensions interact with browser requests.

The Security Argument

Google and some developers argue that MV3 improves user security and privacy. A Google employee noted that the new policy aligns with Safari's approach and prevents extensions from scraping sensitive information by requiring block lists to be declared in advance.

The Ad Blocking Argument

Critics argue that the move is designed to protect Google's advertising revenue. By limiting the ability of extensions to dynamically modify network requests, MV3 makes it significantly harder for ad blockers to filter content with the same granularity and efficiency as MV2 extensions.

Community Perspectives and Alternatives

Users and developers on Hacker News have expressed significant concern over the "Chromium monoculture," where Google's decisions dictate the web experience for the majority of users.

Browser Alternatives

Many users recommend switching to non-Chromium browsers to maintain full ad-blocking capabilities:

  • Firefox: Frequently cited as the primary alternative for those wanting to avoid Google's ecosystem and maintain a more open internet.
  • Zen Browser: A community-driven Firefox fork mentioned as a modern alternative.
  • Brave: While based on Chromium, Brave is often used for its built-in ad-blocking features that operate outside the extension system.

Alternative Blocking Methods

Some technical users suggest moving away from browser-level extensions entirely in favor of DNS-based ad and tracking blockers, which filter traffic at the network level before it even reaches the browser.

User Experience with MV3

Some users report that MV3-compliant versions of ad blockers (such as uBlock Origin Lite) provide a similar experience to their predecessors, suggesting that for average users, the impact may be less disruptive than for power users who rely on advanced filtering rules.

Sources