Deprecation of Manifest V2 extensions in Chrome's Beta, Dev, and Canary channels began in June 2024, putting a hard clock on the ad blockers, privacy tools, and content filters that tens of millions of users rely on daily.

The MV2 sunset has been years in the making. Google announced the Manifest V3 platform back in October 2018, framing it around three pillars: stronger security, improved privacy, and tighter performance guarantees. The Chrome Web Store started accepting MV3 extensions in January 2021, following the stable release of Chrome 88, giving developers a roughly three-year runway before the enforcement phase began. That runway is now exhausted in pre-release channels.

The friction between Google and the ad-blocking ecosystem stems from one of MV3's most contested changes: the replacement of the webRequest API's blocking capability with the declarativeNetRequest API. Under MV2, extensions could intercept network requests dynamically and apply arbitrarily complex filtering logic at runtime. Under MV3, filtering rules must be declared statically in advance, and Chrome enforces a cap on the number of rules an extension can register. Critics argued from the start that this cap would blunt the effectiveness of sophisticated blockers that maintain large, frequently updated filter lists. Google has adjusted the rule limits over time, but the architectural constraint remains.

The developer community has not stood still. AdGuard released a beta of its MV3-compatible ad blocker, demonstrating that meaningful blocking is achievable within the new constraints — though the company has been candid about the tradeoffs involved, particularly around dynamic filter updates. Other major players, including uBlock Origin's developer Raymond Hill, have been more pessimistic, with Hill releasing a separate uBlock Origin Lite built to MV3 spec while maintaining that it is a diminished product compared to its predecessor.

It is worth placing this alongside what Chrome already does natively. Since February 2018, Chrome has automatically blocked ads on sites that fail the Better Ads Standards — a coalition-backed framework targeting the most disruptive ad formats. In July 2019, that protection was extended: Chrome began suppressing all ads on repeat violator sites, not just the offending units. Separately, Chrome has enforced resource thresholds since 2020, blocking ads that consume more than 4 MB of network data, 15 seconds of CPU in any 30-second window, or 60 seconds of cumulative CPU. Chrome's built-in ad filtering is real, but it targets the egregious tail of the distribution. It does not address the far larger universe of tracking pixels, retargeting scripts, and fingerprinting vectors that motivated most users to install a third-party blocker in the first place.

The policy and commercial dimensions here are hard to ignore. Google's core business is advertising, and the company controls both the dominant browser and a significant share of the ad infrastructure that extensions seek to filter. That conflict of interest has shadowed the MV3 debate since 2018. Google has consistently maintained that the architectural changes are motivated by security — and it is true that powerful, dynamically executing extensions represent a genuine attack surface — but the timing and specific design choices have fueled skepticism that will not dissipate with reassurances alone.

Looking at what this means for developers right now: the deprecation in Canary, Dev, and Beta channels is the harbinger of a stable-channel cutoff. Extensions still running on MV2 in production will eventually stop functioning for stable Chrome users. The migration path exists. It is narrower than what MV2 permitted, but vendors like AdGuard have shown it is navigable. Developers who have been deferring the port are running out of road.

The longer-term effect on the extension ecosystem is genuinely uncertain. Some categories of extension — password managers, developer tools, productivity utilities — adapt to MV3 with minimal disruption. Content filtering tools bear the heaviest burden. Whether the MV3 rule limits prove sufficient for real-world blocking at scale, or whether users end up with a materially weaker privacy posture in Chrome, will play out over the next several browser release cycles. Firefox, notably, continues to support MV2 alongside MV3, giving users with strong blocking requirements an alternative that is not going away imminently.