Google plans to disable extensions built with the older Manifest V2 framework on June 3, beginning with users of Chrome's Beta, Dev, and Canary versions
Michael Kan / PCMag :
Context & Ripple Effects
This is the enforcement step in a longer Chrome-extension policy shift: Google had already tightened distribution by ending third-party inline extension installation and signaled that some ad-blocking capabilities would be restricted outside enterprise use.
The phased rollout starts with Chrome’s pre-release channels rather than the general user base, making it an early compatibility deadline for developers. It also sits alongside Mozilla’s decision not to mirror Google’s more restrictive Manifest V3 approach in Firefox.
First-order effects
- Developers whose extensions still depend on Manifest V2 face an immediate breakage risk in Chrome Beta, Dev, and Canary and must move affected products to the newer framework.
- Pre-release Chrome users lose access to unsupported Manifest V2 extensions first, while Google uses the staged rollout to surface compatibility problems before wider enforcement.
Second-order effects
- Extension publishers, especially those with complex content-blocking or network-request features, are pushed to redesign products around Manifest V3’s available APIs; later Chrome warnings about uBlock Origin’s pending disablement illustrate the user-facing consequence.
- Firefox can present its differing extension implementation as an alternative for developers and users whose tools cannot retain equivalent functionality under Chrome’s rules.
Third-order effects
- Browser vendors are becoming more explicit gatekeepers of extension capabilities: platform API changes can determine which privacy, security, and customization tools remain viable.
- If staged deprecations become the standard, extension makers will need to design for browser-specific policy divergence rather than assume a single cross-browser feature baseline.
The trend: This is part of a broader shift toward browser-controlled extension platforms, where security and performance policy changes also reshape the capabilities available to third-party tools.