Microsoft announced on August 7, 2026 that Microsoft Edge will begin transitioning consumers away from Manifest Version 2 (MV2) extensions starting in August 2026, with the goal of completing the consumer shift to Manifest Version 3 (MV3) by the end of the year. The company disclosed the plan in a post on the Microsoft Edge Insider blog. Microsoft Edge Insider Blog

The deprecation rollout will start in Edge's Canary, Dev, and Beta channels before gradually broadening to the Stable channel. Microsoft will gradually turn off MV2 extensions by default in Edge over the coming months. Users will be notified in advance before their MV2 extensions are disabled and directed to recommended MV3 versions where available. The Verge

Managed devices will not be affected during the consumer MV3 rollout. Enterprise deprecation of MV2 extensions in Edge is scheduled to follow in early 2027.

The path to this transition has been years in the making. Microsoft first announced in October 2020 that Edge Add-ons would support the changes proposed as part of Manifest Version 3. The Edge Add-ons storefront stopped accepting new MV2 extensions from July 11, 2022. Microsoft Edge Dev Blog

For extension developers, the practical implication is straightforward: any extension still shipping an MV2 manifest needs an MV3 migration path, and the window for keeping MV2 code alive in Edge is now measured in months for consumers and roughly a quarter or two beyond that for enterprise. The notification-and-recommendation flow Microsoft describes suggests the company will attempt to shepherd users toward MV3 equivalents rather than simply stripping functionality, but the effectiveness of that approach depends on whether MV3 versions actually exist for every extension a given user relies on.

The MV3 transition has been contentious across the Chromium ecosystem since Google first proposed the changes, primarily because MV3's replacement of blocking webRequest with declarativeNetRequest imposes constraints on how ad blockers and privacy extensions operate. Microsoft, building Edge on the Chromium engine, inherits the same architectural shift. Ad-blocking extensions in particular have faced the most scrutiny under MV3, since declarativeNetRequest's rule-count limits and performance-oriented design trade filtering flexibility for a more constrained but faster model. Extensions that depended on dynamic, runtime-evaluated request interception have had to rearchitect around static rule sets.

Microsoft's decision to exempt managed devices from the consumer rollout is a pragmatic one. Enterprise environments often depend on internally developed or specialized extensions, and a forced MV2 cutoff in those settings could break line-of-business workflows with no straightforward remediation. Staging enterprise deprecation separately in early 2027 gives IT administrators a longer runway to audit their extension inventories and migrate or replace MV2 dependencies.

What remains genuinely uncertain is how many MV2 extensions in the Edge Add-ons catalog still lack MV3 counterparts. Microsoft's notification flow presumes that recommended MV3 versions will be available, but the company has not publicly quantified the gap. For users of niche or abandoned extensions, the practical outcome may be a quiet loss of functionality rather than a seamless transition.