Microsoft plans to end support for Manifest V2 extensions in Edge starting this month, following Google Chrome, and for enterprise users in early 2027
Microsoft's plan for Edge means that uBlock Origin users are losing one of their browser options.
Context & Ripple Effects
Microsoft is following the path Google had already set: Chrome began disabling the older extension framework in pre-release channels and later warned that uBlock Origin could be disabled. Edge’s move removes a remaining major browser option for users of extensions built on Manifest V2, while its enterprise timetable extends that transition into early 2027.
The change also fits Edge’s longer record of shedding older browser technologies, from excluding legacy extension and scripting components at launch to Microsoft’s retirement of Internet Explorer in favor of Edge.
First-order effects
- uBlock Origin users on Edge lose support for the Manifest V2 version as Microsoft begins the phaseout, narrowing their browser choices.
- Enterprise Edge deployments retain Manifest V2 longer, but must plan for support to end in early 2027.
Second-order effects
- Extension developers serving both Chrome and Edge face a consolidated migration deadline, because the two browsers are now retiring the same older framework.
- Organizations that rely on Manifest V2 extensions will have to validate replacements or updated versions before Edge’s enterprise exception expires.
Third-order effects
- Chrome and Edge aligning on Manifest V2 retirement concentrates extension-platform policy in the Chromium browser ecosystem, leaving fewer large-scale outlets for legacy extensions.
- If this alignment persists, browser compatibility will increasingly depend on developers maintaining extensions for the current platform rules rather than preserving older APIs.
The trend: Major Chromium browsers are converging on the retirement of legacy extension frameworks, forcing users and enterprise deployments toward maintained alternatives.