Manifest V2 Is Finally Dead: Keep Blocking Ads on Chrome

Yesterday, August 31, my co-worker walked up to my desk holding his phone with a familiar look of confusion. “Ublock’s gone,” he said. “Chrome won’t let me reinstall it, the shield is just gray.” He wasn’t hallucinating. Google had just hit the final milestone in a browser-extension transition four years in the making, pulling every remaining Manifest V2 extension out of the Chrome Web Store overnight, and that list includes uBlock Origin, one of the most capable content blockers ever built.

If your blocker suddenly looks broken, there is good news: the situation is easy to sort out in about ten minutes. This is the practical guide I walked my team through this morning, the same steps I used on my own machines, and it covers what changed, why it happened, and the three solid ways to keep blocking ads and trackers in late 2026.

What Actually Just Happened

Manifest V2 (MV2) and Manifest V3 (MV3) are the two “grade levels” of the browser-extension platform. Google began closing the door on MV2 in January 2022 when it stopped accepting new MV2 submissions, and since then it has been steadily disabling old extensions and removing the workarounds that kept them running. The official MV2 deprecation timeline is remarkably transparent about the sequence.

Here is the part most coverage gets wrong, so let me be precise. Chrome had already been phasing out MV2 for months: Chrome 138 in 2025 disabled it for most users, Chrome 150 stripped the kExtensionManifestV2Disabled flag, and Chrome 151 removed the last developer-mode escape hatch. What happened on August 31, 2026 is that Google actually removed all remaining Manifest V2 extensions from the Chrome Web Store itself. You can no longer find or install them there — this affects not just Chrome, but every Chromium-based browser that relies on the Chrome Web Store, including Brave and Edge.

Why This Is Hard on Ad Blockers Specifically

The core problem is technical, not political. Classic uBlock Origin used the webRequest API, which let it intercept each network request in real time, know which page asked for it, and make a judgment call. Manifest V3 replaces that with declarativeNetRequest, a much more limited API designed to give browser extensions tight, pre-compiled rule sets instead of live control of your traffic.

The uBlock project’s own explanation cuts through the noise. In the uBlock Origin Lite FAQ, the maintainers note that declarativeNetRequest “does not support the ability to enforce rules according to the top context,” meaning it cannot see the URL currently in the address bar when deciding what counts as an ad. That one capability gap is why dynamic filtering, generic cosmetic filtering by default, and user-supplied custom filter lists simply cannot work the way they did before.

The flip side of this is that the change has a genuinely legitimate rationale. Browser extensions get an enormous amount of access to everything you do online, and MV3 narrows that attack surface while forcing the filtering work to happen more efficiently. In other words, this is one of those trade-offs where Google has a real security argument — it just happens to cost ad blockers their sharpest edge. It is the same browser-security story I touched on in my article on Google’s AI patching 1,072 Chrome security bugs.

Three Ways to Keep Blocking Ads in 2026

Option 1: Switch to uBlock Origin Lite on Chrome

If you want to stay on Chrome, the cleanest path is uBlock Origin Lite (uBOL), the official MV3-compatible build of the same project. I installed it this morning and it is genuinely good — it ships with uBlock’s default filter lists plus EasyList, EasyPrivacy, and Peter Lowe’s block list, and because it runs declaratively, it actually consumes almost no memory when it is not actively blocking.

• Search the Chrome Web Store for uBlock Origin Lite (the listing is live, unlike the old MV2 one) and install it.
• Open the popup and click the cog icon to reach its options page.
• For heavier filtering, raise the blocking mode to Complete. Be aware this asks for broader site permissions — that is the honest trade-off the Lite version makes.
• Understand what you are giving up: no dynamic per-site filtering, cosmetic filtering is off by default until you raise the mode, and you cannot drop in your own custom filter lists.

This mirrors the mindset I wrote about in my guide to vetting extensions before you install them — check what permissions a tool actually requests before you accept them.

Option 2: Run Full uBlock Origin on Firefox

If you want the complete, untouched uBlock Origin experience — dynamic filtering included — Firefox is where it still lives. Unlike Chromium, Firefox’s extension platform supports the full webRequest-style model, so the classic uBlock Origin that Chrome just lost continues to work at full strength there. On the uBlock Origin repository, the project makes its position clear: uBlock Origin works best on Firefox and is available for both desktop and Android.

This is the route I recommend for anyone who runs heavy ad-blocking on an ad-saturated site. Keep your Chromium browser for daily browsing, add a second Firefox profile strictly for blocking-heavy work, and you get the best of both worlds. It sounds like a hassle, but a single-purpose browser profile costs nothing and pays off the moment a site starts swallowing your screen with pop-overs.

Option 3: Brave, with Its Own MV2 Backend

Brave is a Chromium-based browser, so it is not immune to the removal. But Brave made a deliberate engineering choice: its team hosts four popular Manifest V2 extensions on its own backend — uBlock Origin, AdGuard, uMatrix, and NoScript — and lets users enable them directly in the browser. On top of that, Brave’s built-in Shields blocker operates at the browser-engine level rather than as an extension, so it sidesteps the MV3 problem entirely.

If you are already a Brave user, this is the least-friction fix: just enable Shields, or add the uBlock Origin instance Brave hosts. If you are deciding between browsers and value blocking above brand loyalty, Brave now has a real argument over its Chromium cousins.

What About Microsoft Edge and Opera?

Both are Chromium downstream, and both have signaled they will follow the same path. Microsoft announced Edge will transition consumers off MV2 through the rest of 2026, with enterprise deprecation following in early 2027. So do not treat any MV2 extension still running in Edge or Opera as safe forever — plan as if the same clock is ticking there.

My Step-by-Step Audit for Your Own Browsers

Rather than telling you to trust me, here is the quick checklist I used. Checking your current state takes under two minutes and answers the only question that matters: which blockers still work, and which framework are they running on?

1. List your extensions. Type chrome://extensions into the address bar and scroll the list. Any extension the store just removed will show as disabled or flagged.
2. Check the manifest version. Turn on Developer mode in the top-right of that page, click Details on an extension, and look at Source. The path will reveal whether it is the MV3 build (uBOL) or an abandoned MV2 relic.
3. Decide on your ten-minute fix. Stay on Chrome with uBlock Origin Lite, add Firefox for full uBO, or lean on Brave’s hosted MV2 set.
4. Recheck occasionally. Extension stores change, and — as I covered in my piece on malicious Chrome VPN extensions — the store is also where bad actors plant lookalikes. Refresh your mental inventory now and then.

What I Recommend You Actually Do

For most people, the honest answer is uBlock Origin Lite on Chrome, plus a Firefox profile for the sites that need the heavy artillery. It is free, it is official, it keeps you on a browser you already trust, and you lose far less than the headlines suggest. The dramatic stuff — “uBlock Origin is dead forever” — is technically true on Chromium but ignores that the same project maintains a capable MV3 descendant and a full-featured Firefox twin.

Set up the fix once, verify it is blocking on a news site you know is heavy on ads, and then stop thinking about it. This is one of those rare browser inflection points where a few minutes of setup now saves you weeks of nagging pop-up frustration later. And if you find an extension demanding far more permission than a content blocker should — that is exactly the kind of red flag worth investigating before you click install.