What you need to know
Google’s Manifest V2 timeline says Chrome 138 disabled MV2 extensions for all users on July 24, 2025, the enterprise exemption policy was removed in Chrome 139, and all remaining MV2 extensions were removed from the Chrome Web Store on August 31, 2026. Existing installs on Chrome 138 or earlier can no longer be updated or reinstalled.
Potentially affected
Organizations that rely on Chrome extensions, including internal or vendor-built extensions for kiosks, portals and productivity, and the IT staff who manage Chrome by policy.
DSE recommendation
DSE recommends inventorying every Chrome extension in use, replacing any Manifest V2 extension with a Manifest V3 version, and keeping Chrome current rather than holding at version 138.
Google’s Manifest V2 timeline says Chrome 138 disabled MV2 extensions for all users on July 24, 2025, the enterprise exemption policy was removed in Chrome 139, and all remaining MV2 extensions were removed from the Chrome Web Store on August 31, 2026. Existing installs on Chrome 138 or earlier can no longer be updated or reinstalled.
Source facts
Google’s Manifest V2 support timeline says that with Chrome 138, Manifest V2 extensions were disabled for all users on all channels as of July 24, 2025, and users could no longer turn them back on. It says the ExtensionManifestV2Availability enterprise policy was removed with Chrome 139, so MV2 extensions stopped working for anyone upgrading to Chrome 139 and later, making Chrome 138 the final version to support them with that policy.
On August 31, 2026, all remaining Manifest V2 extensions were removed from the Chrome Web Store; existing installs on Chrome 138 or earlier continue to run but can no longer receive updates or be reinstalled if removed. Earlier steps included the Web Store refusing new public and unlisted MV2 extensions in January 2022 and new private ones in June 2022.
Applicability
Use this for Chrome and ChromeOS fleets. Other Chromium-based browsers set their own timelines, so check each browser in use.
DSE recommendation
DSE recommends inventorying every Chrome extension in use, replacing any Manifest V2 extension with a Manifest V3 version, and keeping Chrome current rather than holding at version 138. Ask vendors of internal and portal extensions for MV3 builds, remove extensions with no supported replacement, and use an allowlist policy so unreviewed extensions cannot be installed.
Verification
Pull an extension inventory report from the management console, confirm no Manifest V2 extensions remain, and confirm every managed browser runs a supported Chrome version.
Official reference
Chrome for Developers — Manifest V2 support timeline. Reviewed October 19, 2026.
Review the official source
Chrome for Developers — Manifest V2 support timeline · Verified October 19, 2026
Need help applying this guidance safely?
DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.
Talk with DSE