TL;DR

Google Chrome has begun deprecating Manifest V2 extensions, effectively ending uBlock Origin bypasses. Edge and Opera are expected to follow, affecting ad-blocking capabilities. The change is due to security and technical concerns.

Google Chrome has begun the process of removing support for Manifest V2 extensions, effectively ending the ability of ad-blockers like uBlock Origin to bypass restrictions. This change is part of Chrome’s final phase of deprecating MV2, with Edge and Opera likely to follow, impacting users relying on workarounds for ad-blocking.

Recent updates to Chromium, the core engine behind Chrome and other browsers, have led to the removal of key flags that supported MV2 extensions. Chromium contributor Andrey Bershanskiy confirmed that the flag ‘kExtensionManifestV2Disabled’ has been completely removed, signaling the end of support for MV2 extensions in supported Chrome versions. Google engineer Devlin Cronin explained that maintaining MV2 functionality has become too complex and insecure, prompting its discontinuation.

This development directly affects popular ad-blocking extensions like uBlock Origin, which relied on MV2 bypass techniques to function despite browser restrictions. The removal of support means that these workarounds will no longer work in Chrome, with the timeline indicating that support will cease entirely after Chromium version 151. For example, the Windows Registry mod used to extend MV2 support will stop functioning after this update.

Other Chromium-based browsers, including Opera and Microsoft Edge, are expected to phase out MV2 support as well. Opera had already signaled plans to abandon MV2 support earlier, and recent communications suggest that they may fully disable MV2 extensions soon. Meanwhile, browsers like Brave and Vivaldi continue to support MV2, but their future support remains uncertain. Firefox remains unaffected, supporting both MV2 and MV3, providing an alternative for users seeking consistent ad-blocking.

Impact on Ad-Blocking and Browser Security

This change matters because it effectively ends the workarounds that allowed extensions like uBlock Origin to bypass Chrome’s restrictions, potentially reducing the effectiveness of ad-blockers in Chrome and other browsers following suit. It reflects a broader push toward more secure, standardized extension architectures but raises concerns about user privacy and control. Users relying on these extensions may need to switch browsers or update to MV3-compatible versions, which could impact their browsing experience and ad-blocking capabilities.

Amazon

ad blocker for Chrome

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Background on Extension Support Transition

The transition from Manifest V2 to MV3 has been underway for several years, with Chrome announcing plans to phase out MV2 support to improve security and performance. Chrome’s support for MV2 extensions has been gradually withdrawn, with the latest developments marking the final removal of key flags that enabled bypasses for extensions like uBlock Origin. Other browsers based on Chromium, such as Opera and Edge, initially committed to supporting MV2 longer but are now following Chrome’s lead, with official notices indicating support will soon end. Firefox remains a major alternative, supporting both MV2 and MV3, and is unaffected by these changes.

“The removal of the ‘kExtensionManifestV2Disabled’ flag means that MV2 extensions will no longer be supported in Chrome, ending many workarounds used by ad-blockers.”

— an anonymous researcher

Amazon

uBlock Origin alternative extension

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unclear Timeline for Full Browser Support Changes

While Chrome has begun removing support for MV2 extensions, the exact timeline for complete discontinuation across all Chromium-based browsers remains uncertain. Opera and Edge have indicated plans to phase out MV2, but specific dates and the extent of support removal are still to be confirmed. Additionally, the impact on user experience and extension functionality during the transition period is still evolving.

Amazon

MV3 compatible ad blocker

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Users and Developers

Users relying on uBlock Origin and similar extensions should prepare for reduced functionality as support ends. They may need to switch to browsers like Firefox or Vivaldi, which continue supporting MV2, or update to MV3-compatible versions of their extensions. Developers are encouraged to migrate their extensions to MV3 to ensure ongoing support. Browser vendors will likely finalize the rollout of support discontinuation in the coming months, with further updates expected as the transition progresses.

Amazon

browser extension for ad blocking

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

Will uBlock Origin still work in Chrome after support is removed?

Likely not, as workarounds that relied on MV2 support will cease to function once support is fully removed in Chromium version 151 and later updates.

Are other browsers affected by this change?

Yes, Chromium-based browsers like Opera and Edge are expected to phase out MV2 support soon, although the exact timelines are still being confirmed.

Can I still use ad-blockers in Chrome after this change?

Yes, but you may need to switch to MV3-compatible extensions or alternative browsers like Firefox for full ad-blocking capabilities.

Why is Chrome removing MV2 support?

Chrome cites security concerns, technical complexity, and the need to modernize extension architecture as reasons for discontinuing MV2 support.

What should extension developers do now?

Developers should update their extensions to MV3 to ensure compatibility and support in future browser versions.

Source: Hacker News

You May Also Like

Incident postmortem builder for managed service providers

A new incident postmortem builder tailored for small managed service providers is being tested, aiming to streamline incident communication and reporting.

The $9 Billion Signature Tax: How DocuSign’s Business Model Survives on One Assumption

A new open-source project, DocuSeal, challenges DocuSign’s dominant market position by offering a self-hosted, cost-effective digital signature solution.

So Reddit Has Decided That Plain HTML Is Unsafe

Reddit has announced it will disable the use of plain HTML in posts to enhance security, citing potential vulnerabilities and abuse.

Your ‘App’ Could Have Been A Webpage (So I Fixed It For You)

A developer publicly fixed a mobile app by recreating it as a webpage, highlighting issues with app design and offering a practical alternative.