Microsoft Edge is preparing to follow Google Chrome down a path that privacy advocates have been dreading for years. The browser will soon begin disabling extensions built on Manifest V2, the older extension framework that powers some of the most capable ad blockers on the market — tools that millions of users rely on to strip trackers, block surveillance ads, and cut page load times in half. The Verge Edge extensions report confirms that Microsoft’s timeline is now in motion, putting Edge squarely in line with Chrome’s controversial 2024 transition. For anyone who assumed Edge was a safe harbor after Google’s crackdown, that window is closing fast.
The stakes here go beyond personal preference. Ad blocking is also a meaningful cybersecurity layer — malicious ads, or malvertising, remain one of the most common vectors for delivering malware to everyday users. Stripping out capable blockers doesn’t just hurt the ad-free browsing experience; it removes a practical defense. That context matters especially now, as threat researchers continue cataloging new vulnerabilities week over week. The move touches a tension that Future Wire has covered in adjacent territory: how AI red team and security research keep bumping up against platform decisions that quietly reduce user protections.
What MV2 vs. MV3 Actually Means for Your Blocker
The technical core of this fight comes down to a single architectural difference. Manifest V2 allows extensions to use a powerful API called webRequest, which can intercept and block network requests before they load — including ads, trackers, and scripts. Manifest V3, the replacement framework, swaps that for a declarativeNetRequest API that works from pre-approved rule lists rather than dynamic interception. The difference sounds abstract, but it’s enormous in practice. Extensions like uBlock Origin in full mode can run tens of thousands of filter rules dynamically; the MV3 framework caps declarativeNetRequest rule sets in ways that crimp the most aggressive configurations.
uBlock Origin, widely considered the gold standard of ad blockers, already has an MV3-compatible version called uBlock Origin Lite — but its developer has been open about the fact that the Lite version is meaningfully less capable than its predecessor. Other tools are in similar positions, caught between adapting to a constrained API or being locked out of Chromium-based browsers entirely. Edge, built on Chromium, inherits the same architectural constraints as Chrome, which means any extension that works in Chrome will work in Edge — and any that doesn’t will be locked out of both.
Microsoft’s Timeline and What Users Should Do Now
Microsoft has not yet published an exact kill date for MV2 support in Edge, but the direction is unambiguous. The company confirmed it is aligning with Google’s phaseout schedule, meaning MV2 extensions in Edge will first be flagged as unsupported, then disabled by default, and eventually blocked from installation entirely. Chrome began warning users in 2024 and has been progressively tightening restrictions since. Edge users should expect a similar staged rollout. Users who rely on uBlock Origin, AdGuard, or similar MV2-based extensions should check now whether their tool has a functional MV3 version available — and test whether that version actually meets their filtering needs before the switch is forced.
For privacy-focused users, the most practical alternative remains Firefox, which has committed to maintaining MV2 support indefinitely and has stated publicly that it views the webRequest API as essential to meaningful extension capability. That stance is increasingly a differentiator as Chromium-based browsers converge on the same restricted framework. Whether Microsoft had any real choice here is a fair question — Edge’s Chromium foundation means diverging from Google’s extension model would require significant engineering investment — but the effect on users is the same regardless of the reason. The era of the most powerful ad blockers running on mainstream browsers is ending, and Edge is now officially part of that story.
