Google has begun disabling installed Chrome extensions that still use Manifest V2, turning a years-long deprecation plan into an immediate experience for users on the stable browser channel.
The developer documentation in the packet says the rollout is happening gradually over several weeks and that users whose extensions are disabled will be directed to the Chrome Web Store, where Manifest V3 alternatives are recommended. For some users, there will still be a short window in which the extensions can be re-enabled. But the direction is now clear: the browser is moving from notice to enforcement.
The change is the latest stage in a transition that has been unfolding across Chrome channels and the Chrome Web Store. According to the source, all users across Chrome channels have already had Manifest V2 extensions disabled by default, while the company has also been warning users through the chrome://extensions page. The timeline notes that Chrome 138 is the last version that supports Manifest V2 in limited circumstances, and that Chrome 139 removes support for enterprise policy exceptions as well. For organizations relying on ExtensionManifestV2Availability, the reprieve lasts only until June 2025.
That matters because browser extensions are deeply embedded in everyday workflows. Password managers, content tools, productivity plugins and niche utilities can all depend on the extension system. When Chrome removes support, the problem is not abstract. It becomes a question of whether a user’s browser still behaves as expected after an automatic update. For developers, it means migration work must be complete, tested and rolled out before the platform changes underneath them.
The packet also shows how Google is framing the transition. Users are not just being told that old extensions are obsolete; they are being pointed toward alternatives. The move suggests Google wants the ecosystem to converge on Manifest V3 rather than preserve a long tail of incompatible extensions. That may improve security and platform consistency from Google’s point of view, but it also creates unavoidable churn for users who have depended on older extensions for years.
The timing is important. The documentation says some users had already seen warning banners and pre-stable deactivations before the stable rollout began. In other words, this is not a surprise change. It is the point at which the warning lights become the actual shutdown.
For enterprise customers, the story is more complicated. The packet says organizations using the policy exception will continue to be exempt until at least June 2025, but only temporarily. That buys IT teams time to audit their fleets, test replacements and decide whether to retire older extensions or rebuild them for Manifest V3.
The wider implication is that browser platforms are increasingly willing to dictate the shape of the extension ecosystem. Chrome is not merely announcing a preference; it is actively removing compatibility. The result will be felt unevenly. Some users will barely notice if their extensions have already been updated. Others will discover that parts of their daily browser setup have simply vanished.
That is the practical meaning of a deprecation timeline becoming reality: the old web toolchain is being switched off one extension at a time.
