Edge Drops MV2: uBlock Origin's Last Chromium Refuge Is Gone

On August 7, 2026, Microsoft Edge made it official: Manifest V2 is dead. One consequence matters above all others: uBlock Origin — the most popular ad blocker on Chromium — is about to lose its last foothold.

Chrome went first. Now Edge follows. Two browsers commanding over 80% of the desktop market share have reached the same conclusion: MV2 must go. Developers — both extension authors and web builders — need to understand what this changes.

The timeline

Microsoft published a concrete schedule. Starting this month, a subset of users will see warnings on edge://extensions, with Canary, Dev, and Beta channels affected first. By the end of 2026, all consumer users lose MV2 — extensions stop working, and users are pointed to MV3 equivalents. Early 2027, enterprise devices follow.

The notable detail: managed enterprise devices are exempt throughout the consumer rollout. This gives IT admins a buffer — but it also signals that Microsoft knows this transition isn't painless.

MV2 was already dead — at least on paper

Microsoft's own numbers: 95% of top extensions on the Edge Add-ons Store have migrated to MV3. Only 58 MV2 extensions retain meaningful usage. Just 3 lack a public MV3 version.

In other words, the developer community did the migration work long ago. Edge is formalizing a process that's already nearly complete. But the numbers don't tell the full story — because one of those three "no MV3 version" extensions is the full-featured uBlock Origin.

Why uBlock Origin can't "just migrate to MV3"

The answer is architectural, not motivational.

MV2 lets extensions use the webRequest API to intercept requests before they're sent. uBlock Origin relies on this for dynamic filtering — users can adjust rules per site, in real time. Cosmetic filtering hides ad elements. Scriptlet injection disables anti-adblock scripts. All of it runs through webRequest.

MV3 replaces this with declarativeNetRequest. A "declare ahead" model: extensions define rule sets, the browser applies them. The extension never reads request contents. This is more secure, but it cuts dynamic filtering off at the knees:

Capability	MV2 (webRequest)	MV3 (declarativeNetRequest)
URL pattern filtering	✅	✅
Runtime dynamic filtering	✅	❌
Full cosmetic filtering	✅	⚠️ Limited
Scriptlet injection	✅	❌
Rule limit	None	30K static + 5K dynamic

uBlock Origin Lite — the MV3 version by the same author, Raymond Hill — exists. But Hill is candid: it cannot match the MV2 version's filtering capability. The biggest loss is dynamic filtering. On MV3, you can't open a page, see an ad slip through, click the extension icon, and block it on the spot. Every rule must be declared in advance.

What options do users have?

Three paths, none of them perfect:

uBlock Origin Lite (MV3). Works fine for most everyday sites. Anti-adblock scripts and complex ad networks will defeat it. No dynamic filtering.
Firefox. The only browser that still supports MV2 with no plans to drop it. uBlock Origin runs at full power. The trade-off: leaving the Chromium ecosystem.
Opera. Committed to MV2 support "for as long as it's technically reasonable." But Opera runs on Chromium — this promise is fragile long-term.

Extension developers: time to act

If you're still maintaining an MV2 extension, the clock is ticking. Microsoft provides a migration guide and support through GitHub issues.

The three biggest changes:

webRequest → declarativeNetRequest
Persistent background pages → ephemeral service workers (terminated after 30 seconds of idle)
No more eval() or remote code execution

For most extensions, migrating is a straightforward technical exercise. For ad-blockers and privacy tools, it means redesigning the entire filtering pipeline. And for some extensions — like the full uBlock Origin — it's simply not possible.

Web developers: the second-order effects are real

MV3 doesn't change how you build for the web. But it changes how users experience your site.

Weaker ad-blockers mean more ads. More ads mean heavier page weight, longer load times, and degraded Core Web Vitals. A site that loads in 2 seconds can become 5 seconds purely because of third-party ads — and Google uses Core Web Vitals as a ranking signal.

Here's the second-order problem: more ads also mean more tracking. Ad-blockers don't just block ads — they block trackers too. When both degrade simultaneously, user privacy takes a direct hit. Web developers don't control the third-party scripts ad networks inject — but their sites are where those scripts run.

The real problem: who makes this decision?

This is the most important insight, and the least discussed.

Chromium is developed and controlled by Google. Google is also the world's largest advertising company — ads account for roughly 77% of total revenue. The decision to remove the webRequest API came from Google first, justified on security and performance grounds. Those justifications have real technical merit. But they cannot be separated from a structural conflict of interest: the company that lives on advertising decides the future of ad-blocking tools.

Microsoft follows because Edge shares the Chromium engine — not because they independently chose MV3. Opera runs Chromium. Brave runs Chromium. Nearly every browser that isn't Safari or Firefox runs on Google's engine.

The consequence: when Google changes the platform, every user is affected — even those who don't use Chrome. This isn't a technical problem with MV3. It's a structural problem of engine monoculture.

What you need to know

uBlock Origin MV2 dies on Edge by end of 2026. uBlock Origin Lite (MV3) is the alternative, but it lacks dynamic filtering — the core feature that makes uBlock Origin the most powerful ad-blocker.
Firefox is the only remaining MV2 refuge. If you need full-strength ad-blocking, it's your only option.
MV2 extension developers: migrate now. Consumer deadline is end of 2026, enterprise early 2027. Ephemeral service workers are the biggest technical change to prepare for.
Google — the world's largest ad company — controls the future of ad-blocking across all Chromium browsers. This conflict of interest is structural, with no technical fix.
The web will get heavier, slower, and more surveillance-heavy. MV3 isn't the end of ad-blockers — but it's the end of ad-blocking as we knew it.

Content assisted by AI (Amy 🌸). Reviewed by the author.