Chrome has disabled Manifest V2 extensions in all channels, and Google says the last ones were removed from the Chrome Web Store on August 31, 2026. If an extension you rely on never moved to Manifest V3, it is either gone, frozen on an old browser, or replaced by something else.
The timeline in plain terms
Google's own timeline has several steps. New Manifest V2 uploads stopped in 2022. In October 2024 Chrome began disabling installed Manifest V2 extensions. By March 2025 they were disabled by default, though users could still switch them back on. On July 24, 2025, Chrome 138 disabled them everywhere and removed the option to re-enable them.
The enterprise exemption policy was slated for removal in Chrome 139. Then on August 31, 2026, the Web Store removed all remaining Manifest V2 extensions. The page listing these dates was last updated on September 9, 2026.
What this changes for security
Manifest V3 removes remotely hosted code, so an extension can only run JavaScript that shipped in the package the store reviewed. It also moves the background context to a service worker that runs only when needed. Both shrink what a bad update can do.
That is a real improvement, but it is not a guarantee. A malicious extension can still ship bad code inside the package, and Manifest V3 extensions can still ask for broad site access. See how site access works.
What to check this week
- Open your extension list and look for anything that has been disabled or marked as no longer supported.
- Ask why it is disabled. A developer who abandoned the migration may also have abandoned maintenance.
- Be careful with "replacement" extensions found through search. Replacement listings for popular tools are a common way to get users to install something else, so verify the publisher before moving over.
- If you manage browsers centrally, remove any leftover Manifest V2 policy exceptions and confirm your allowlist only names extensions that still exist.
Old installs that still run
Google notes that existing installs on Chrome 138 or earlier keep running but cannot receive updates or be reinstalled if removed. That is a good reason to keep browsers current. An extension that can no longer update will never get a security fix.
Common mistakes
Teams often assume a disabled extension is harmless. It is, until someone installs a lookalike to get the feature back. Others leave old exception policies in place for years. Write down which tools staff lost, offer a vetted replacement quickly, and the pressure to improvise goes away.
Quick check
Can I still turn a Manifest V2 extension back on?
According to Google's timeline, not in current Chrome. Chrome 138 removed the option to re-enable them, and the enterprise policy was slated for removal in Chrome 139.
Does Manifest V3 make an extension safe?
No. It limits some techniques, such as loading code from a remote server, but a reviewed package can still request broad access and misuse it.
Sources
Last reviewed: 19 October 2026.
