Google is pulling the remaining support for Manifest V2 extensions from Chrome this month, closing a years-long migration and ending the era of the most powerful content blockers. Manifest V3, the replacement, caps how extensions can inspect and block network requests, which is why the classic uBlock Origin cannot run under it in full form. For most of Chrome's roughly 65% of the browser market, ad and tracker blocking gets meaningfully weaker unless they switch tools or browsers. It is the clearest example yet of platform control shaping what users can do on their own machines.

  • Chrome removes the last Manifest V2 support this month, disabling extensions that have not moved to Manifest V3.
  • MV3's declarativeNetRequest model limits dynamic request blocking, weakening full-strength content blockers.
  • Users can move to uBlock Origin Lite, switch browsers, or accept reduced blocking.
  • DuckDuckGo has added built-in YouTube ad blocking to its browser, going the opposite direction.
How Manifest V2 and V3 block requests differently Manifest V2 lets an extension inspect each network request and decide dynamically. Manifest V3 asks the extension to register static rules the browser enforces, with a cap on rule count. THE MECHANISM THAT CHANGED Manifest V2 webRequest API Sees every request live Decides block per request Unlimited custom filters Full uBlock Origin works Being removed Manifest V3 declarativeNetRequest Pre-registered rules only Browser enforces, not code Capped rule count uBO Lite, reduced power The new default genztech.blog
Fig 1 The shift from live per-request decisions to capped static rules is why blocking gets weaker, not just different.

What is actually being removed?

Chrome extensions declare their capabilities through a manifest, and the version dictates which APIs they can use. Manifest V2 extensions rely on the webRequest API to inspect network traffic in real time and block or modify requests as they happen. Manifest V3 replaces that with declarativeNetRequest, where an extension registers rules ahead of time and the browser enforces them, subject to a cap on how many rules exist. Google frames this as better for privacy and performance, since extensions no longer see all your traffic. The side effect is that the most flexible blocking, the kind that adapts to new ad and tracker patterns on the fly, is no longer possible at full strength.

RelatedOne fiber cut broke half the web: the CDN fragility problem

Why does this hit ad blockers hardest?

Powerful content blockers depend on large, frequently updated filter lists and the ability to make dynamic decisions. The classic uBlock Origin is the poster child, and its author has said MV3 cannot support the full feature set. The lighter uBlock Origin Lite works within MV3's constraints but is deliberately less capable. So the practical outcome for a typical Chrome user is not a total loss of blocking, but a downgrade, fewer rules, less adaptability, and more ads and trackers slipping through over time as lists cannot keep pace as freely.

What are the alternatives?

Three realistic paths. Stay on Chrome and accept uBlock Origin Lite with reduced power. Switch to a browser that still supports stronger blocking, Firefox continues to allow more capable extensions, and several Chromium forks have signaled they will keep MV2-style support alive longer. Or lean on browsers building blocking in natively, DuckDuckGo just added YouTube ad blocking directly into its browser, sidestepping the extension model entirely. The irony is sharp: as Chrome narrows what blockers can do, rivals are turning blocking into a built-in selling point.

OptionBlocking strengthTrade-off
Chrome + uBO LiteReducedStay put, weaker filtering
Firefox + uBOFullSwitch browsers
DuckDuckGo browserBuilt-inDifferent ecosystem
Chromium forksExtended MV2Support timelines vary

What does this mean for the open web?

The deeper issue is who sets the rules of the browser you use to reach everything else. Chrome is not just a popular app; at roughly two-thirds of the market it is effectively the reference implementation of the web, and decisions it makes about extension capabilities ripple out to how billions of people experience the internet. Narrowing what content blockers can do is defensible on its own technical terms, but it also happens to serve the interests of a company whose revenue depends on ads being seen. That alignment is why the change feels bigger than a version bump. It is a reminder that user agency online is mediated by a handful of engines, and that features users rely on, blocking trackers, controlling what loads, can be quietly constrained by the entity that ships the engine. The encouraging counter-trend is that rivals are treating this as an opening: Firefox keeps stronger extensions alive, DuckDuckGo bakes blocking in, and Chromium forks compete on exactly the capability Chrome is trimming. The web stays open only as long as those alternatives stay viable and people actually use them.

RelatedChrome Web Store's new rules gut data-hungry add-ons

Our take

Google can make an honest technical case for MV3, extensions with total visibility into your traffic are a real risk, but it is impossible to ignore that the company selling most of the world's ads is also the one deciding how well ad blockers may work in the world's most used browser. The conflict of interest is structural, not hypothetical. The healthy response is the one already happening: treat blocking as a reason to choose a browser, not just an add-on you bolt onto whatever ships by default. Competition on this exact feature is the best check on any single vendor's incentives.

Primary sources

Original analysis by GenZTech. Reporting via gHacks.