Microsoft Edge has started the consumer transition away from Manifest Version 2 extensions, with plans to complete the move to Manifest Version 3 by the end of 2026. Enterprise deprecation will follow in early 2027. Microsoft Edge Team
According to Microsoft’s official announcement, 95% of the top MV2 extensions on the Edge Add-ons store have already migrated to MV3, and only 58 MV2 extensions with meaningful usage remain. Of those, just three do not have a publicly available MV3 replacement. Microsoft says this milestone justifies moving forward with the planned deprecation schedule, which was first announced in 2020 as part of the broader Chromium project’s Manifest V3 initiative.
Starting in August 2026, a subset of users with MV2 extensions installed will see notices on the edge://extensions page and on add-on product detail pages. Over the next few months, Edge will gradually disable MV2 extensions by default, notify users in advance, and direct them to recommended MV3 versions. The rollout begins in Canary, Dev, and Beta channels and will broaden to Stable in following months. Managed enterprise devices are excluded from the consumer rollout, with enterprise deprecation scheduled for early 2027. Microsoft Edge Team and Microsoft Edge Developer documentation confirm this timeline.
Manifest V3 introduces several structural changes that affect how extensions operate. Remotely hosted code is no longer allowed, meaning all JavaScript must be packaged within the extension itself for validation. Background pages have been replaced by service workers, and the Web Request API has been superseded by the declarativeNetRequest API for network request modifications. These changes are designed to improve security, privacy, and performance across the extensions ecosystem. For users, the practical impact is that most popular extension types—including password managers, VPNs, and ad blockers—have already transitioned without loss of functionality. Microsoft Edge Team and Microsoft Edge Developer documentation
For developers still maintaining MV2 extensions, the required path is clear: ship an MV3 version and submit the update through Microsoft Partner Center. The official migration guide details the specific code changes needed. Users who depend on specific legacy extensions should check the Edge Add-ons store now for an available MV3 version, because the automatic disablement will proceed after the initial notice period without further escalation. The extensions team has pledged direct outreach to the few remaining developers who need assistance completing their migrations. Microsoft Edge Team
For more on Microsoft’s recent Windows platform updates, see Microsoft PowerToys Rolls Out Free Windows Power Tools.
