Chrome Web Store Deleted Manifest V2: uBlock Origin Is Gone for Good
On 31 August 2026 Google finished a migration it had been running for years: the Chrome Web Store deleted the last extensions built on Manifest V2, and the full version of uBlock Origin went with them. The listings are gone from the store catalogue and from its search index, so the most capable ad and tracker blocker on the web can no longer be installed or restored from Google's own store. A copy that is still running on your machine keeps working for now, but it is a copy with no supply line behind it.
What was actually deleted
Google did not reach into anyone's computer and remove extensions. It removed the listings, and that is enough to make the outcome permanent. An installed Manifest V2 extension no longer receives updates, security patches or filter list updates through the store. And if you disable it or uninstall it from chrome://extensions, there is no way to get it back from any official Google repository. The extension you have today is the last version you will ever have.
The escape hatches closed earlier in the summer
The store purge is the final step, not the first one. Chrome had already been closing the technical detours that power users relied on. Through Chrome 150 at the end of June and Chrome 151 in late July, the enterprise policy that had kept Manifest V2 extensions alive stopped working, first partly and then completely. By the time the listings disappeared, there was nothing left to fall back on inside Chrome itself.
Why Manifest V3 blocking is weaker
The difference is not cosmetic. Under Manifest V2 a blocker could inspect every request the page made and decide, in that moment, what to do with it. Manifest V3 replaces that with rules declared in advance: the extension hands Chrome a rule set, and Chrome does the filtering. It is faster and easier to audit, and it also means the blocker no longer reacts to what a page is actually doing.
On top of that come quotas. Manifest V3 caps how many static and dynamic rules an extension may load. Google raised the static limits and added interfaces for updating filter lists dynamically after developers pushed back, but a ceiling is still a ceiling, and the large community filter lists are what made the original blockers effective in the first place.
What you can use in Chrome now
- uBlock Origin Lite: the Manifest V3 build from the same developer. It covers the common cases and is the closest thing to a drop-in replacement, but it works from pre-declared rules rather than deciding per request.
- AdGuard: a Manifest V3 blocker with its own filter lists, available both as an extension and as a separate application.
- A different browser: the browsers that never depended on the Chrome Web Store are not affected by any of this.
Brave keeps four Manifest V2 extensions alive
Brave chose a different answer: it hosts a short list of Manifest V2 extensions on its own backend, so they survive the store purge. The browser explicitly supports four of them, AdGuard, NoScript, uBlock Origin and uMatrix, and installs them from Brave's servers rather than from Google's. Brave has spent the year adding privacy features of its own, from built-in email aliases to hiding the GPU model from fingerprinting scripts, and keeping the old blockers running fits that line. Firefox is the other option: it kept support for the blocking interface that Manifest V2 extensions rely on.
The tracking layer just got thinner
Ad blocking is the visible part of this story, but the quieter loss is tracker blocking. For a lot of people, a browser extension was the only thing standing between them and the analytics, pixels and fingerprinting scripts that follow them between sites. That layer is now weaker for roughly a billion Chrome users, and it did not get replaced by anything on Google's side.
What is left is filtering further down the stack, at the level of DNS rather than the page: on the router, in the operating system, or in the network app you already run. It resolves known tracker and ad domains into nothing before the browser ever reaches them, which is why this layer keeps working no matter what happens to extension APIs. It is a blunter instrument, it cannot hide elements inside a page, and it is worth setting up precisely because it does not depend on a store listing that someone else can withdraw.