For about a decade, the single most effective thing you could do to make the web tolerable was install one extension and never think about it again. That era has an expiration date now, and it is printed on the calendar. On August 31, Google removes every remaining Manifest V2 extension from the Chrome Web Store. Microsoft Edge started walking the same path this month. When both are finished, the original uBlock Origin, the one that actually inspects every request your browser makes, will not run in either browser at all.
Mozilla and Brave used the moment to say the quiet part loudly: they are not following. Firefox keeps the old extension system alongside the new one, and Brave now hosts the affected extensions on its own servers so its users can still install them after Google stops distributing them. That leaves a strange situation where the most popular content blocker in the world works perfectly well, just not in the browsers most people use.
What Actually Changes on August 31
It helps to separate the milestones, because Chrome has been retiring Manifest V2 in slow motion for years and a lot of coverage has blurred the steps together.
| When | What happened | Could you still get around it? |
|---|---|---|
| July 2025, Chrome 138 | Manifest V2 disabled across the stable channel | Yes, with an enterprise policy or a command-line flag |
| June 30, 2026, Chrome 150 | The last command-line flag removed | Barely, and not for typical users |
| July 28, 2026, Chrome 151 | Remaining Manifest V2 flags stripped out | No |
| August 31, 2026 | All remaining MV2 extensions pulled from the Chrome Web Store | No, the listings simply stop existing |
The August date matters less for people who already lost their blocker and more for everyone downstream. Once the listings are gone, so are the install links, the reviews, the update channel and the paper trail. Anyone still running an old build on an old machine keeps whatever they have, frozen in place, with no more filter engine updates coming through the store.
Why the Replacement Is Weaker, in Plain Terms
The disagreement is not really about extensions. It is about one API. Under Manifest V2, an extension could use webRequest to see every network request the browser was about to make, compare it against filter lists that can run to hundreds of thousands of rules, and decide in the moment whether to let it through. The extension did the thinking.
Manifest V3 replaces that with declarativeNetRequest. The extension hands Chrome a list of rules in advance, and Chrome does the blocking. Google’s argument is reasonable on its face: an extension that reads every request is also an extension that could read every request, and a rule list the browser enforces itself is faster and harder to abuse.
The cost is flexibility. Rules registered ahead of time cannot react to what a page does after it loads, cannot be generated on the fly in response to a site’s countermeasures, and live inside limits on how many rules can be active at once. Sites that rotate their ad domains or reshuffle element names have a much easier time when the blocker cannot adapt mid-page.
| Capability | Manifest V2 blocker | Manifest V3 blocker |
|---|---|---|
| Inspect requests live | Yes, request by request | No, rules are declared in advance |
| Filter list size | Effectively limited by memory | Capped by the browser’s rule budget |
| React to anti-blocker scripts | Strong, logic runs in the extension | Limited, logic runs in the browser |
| Custom user rules | Unrestricted | Allowed, within quotas |
| Update speed after a site changes | Filter list refresh, often same day | Often needs an extension update |
That last row is the one power users notice first. Streaming sites in particular treat blocking as an arms race, and the winning side has historically been whoever could ship a fix fastest. Our walkthrough on how to block Twitch ads with uBlock Origin exists precisely because that cat and mouse game runs on a weekly cycle, and it is exactly the kind of fight a pre-registered rule list is not built to win.
Edge Is Doing the Same Thing, Just Later
Microsoft spent a while sounding noncommittal, which gave some people the impression Edge would hold the line. It will not. The consumer retirement began this month in the Canary channel, then moves through Dev and Beta before reaching Stable over the following months. Microsoft is aiming to have consumers fully transitioned by the end of 2026, with enterprise deprecation starting in early 2027.
The staggered schedule is worth understanding if you use Edge daily. You are not going to wake up tomorrow with a dead blocker. You are going to wake up one day in the next several months with a dead blocker, and the exact morning depends on which channel you are on.
The Browsers That Are Not Going Along
Two holdouts remain, and they hold out in different ways.
Firefox is the cleaner answer. It runs on Gecko rather than Chromium, it supports Manifest V3 for compatibility while keeping Manifest V2 alive next to it, and it retains the full webRequest API. Mozilla has said it has no current plans to remove that support. In practice Firefox is now the only major browser where uBlock Origin runs at genuinely full power, which is a sentence nobody would have written five years ago.
Brave is the more interesting case, because it is Chromium based and therefore inherits Google’s engine decisions. Its workaround is distribution rather than engineering: Brave hosts uBlock Origin and other supported Manifest V2 extensions on its own servers, so its users can keep installing them after Chrome’s store purge. Brave also does a lot of blocking natively, below the extension layer, which softens the blow either way.
What About Phones
Mobile is where this gets genuinely annoying, because the extension question barely applies. Chrome on Android has never supported extensions at all, so nothing changes there, and it was already the weakest option for anyone who cares about this. Firefox on Android does support a curated set of add-ons including uBlock Origin, which makes it the closest thing to a desktop-grade answer on a phone. If you are weighing that switch, our ranking of the best browsers for Android covers how the alternatives compare on speed and sync, not just blocking.
On iPhone and iPad the whole discussion is different again, since content blocking there works through a separate system extension model rather than through anything resembling Manifest V2 or V3. If that is your situation, the mechanics of blocking ads in Safari are unaffected by any of this week’s news.
Is uBlock Origin Lite Good Enough?
For a lot of people, honestly, yes. Lite is the Manifest V3 version built by the same developer, it ships sensible default filter lists, and on an average news site the difference is not dramatic. If your browsing is mostly mainstream sites and you mainly want fewer banners and less tracking, you will probably be fine.
The gap shows up at the edges. Sites that actively fight blockers, sites that inject ads through the same infrastructure that serves the content, and any situation where you want to write your own rules are all places where Lite gives ground. It is not a scam or a token gesture. It is a smaller tool wearing a familiar name, and the confusion between the two is going to generate a lot of support threads over the next month.
The Bottom Line
Google’s stated reasoning about security and performance is not fabricated, and extensions with unrestricted access to every request have genuinely been abused. It is also true that the company that sells most of the advertising on the internet has now removed the technical capability that made the strongest ad blockers strong. Both of those things can be true at once, and reasonable people land in different places on how much weight to give each.
What is not ambiguous is the practical situation. After August 31 there is no version of Chrome, no flag and no policy that brings the old blocker back. If that matters to you, the fix is not a setting. It is a different browser, and the two that still work are sitting there waiting.
