WEB Signal 342
Microsoft Edge is about to lock out older ad blockers, just like Chrome did
↗
Edge will phase out the Manifest V2 extension model, disabling older ad-blocking add-ons such as uBlock Origin.
Developers and users who rely on legacy ad-blockers will lose functionality unless they migrate to Manifest V3 versions or switch browsers. The change also signals a broader industry move toward a newer extension API, affecting any tooling that interacts with the older platform.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Edge will start disabling Manifest V2 extensions by default this month, with a full consumer transition to Manifest V3 slated for the end of the year.
Only a handful of extensions still depend on Manifest V2, and most have equivalents or newer builds available on the Edge store.
Enterprise deployments will see the deprecation delayed until early 2027, while managed devices are exempt during the consumer rollout.
THE READ
What the cluster adds up to.
Microsoft has announced that the older extension framework, known as Manifest V2, will be turned off in Edge. The rollout begins in the pre-release channels and will spread to the stable channel over the coming months. Users will receive prompts directing them to newer versions of the affected extensions where they exist. This mirrors a similar shift that Google made in Chrome earlier in the year.
For engineers maintaining web-related tooling, the immediate impact is that any scripts or automation that depend on the legacy ad-blocking extensions will stop receiving traffic filtering once the extensions are disabled. The change does not affect extensions that have already been rebuilt for Manifest V3, so updating to those versions restores functionality. The transition period gives a window to test and replace the affected add-ons before they are fully removed.
The cost of adopting the new model is largely limited to updating or replacing the extensions in use. Users can switch to a lightweight version of uBlock Origin that already targets the newer API, or move to browsers that continue to support Manifest V2, such as Opera, if they prefer to keep the same add-on. Enterprises will need to plan for a separate migration timeline that extends into early 2027, but managed devices are currently shielded from the consumer-focused rollout.
Where the change stops working is clear: any extension that remains on Manifest V2 will be disabled by default and eventually removed from the store. This includes the full-featured uBlock Origin and similar blockers that have not been ported. After the deprecation deadline, those extensions will no longer load at all, even if manually installed, unless the browser provides a legacy compatibility mode, which Edge does not indicate it will.
Overall, the shift pushes the ecosystem toward a more uniform extension platform, reducing the maintenance burden for the browser vendor but requiring developers and power users to audit their extension dependencies. The limited number of affected extensions suggests that most users will have a ready replacement, but any custom or niche tools built on Manifest V2 will need to be rewritten or abandoned.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER