Today is a store-removal deadline, not a new universal shutdown
Modern Chrome releases already disabled Manifest V2. August 31 removes the remaining V2 listings from the Chrome Web Store. Copies installed on Chrome 138 or earlier may remain installed, but they cannot receive updates or be reinstalled after removal.
Fact-checked: August 31, 2026
Google’s final Chrome Manifest V2 store deadline arrives on August 31, 2026. All remaining Manifest V2 extensions are being removed from the Chrome Web Store, ending normal discovery, updates and reinstallation through the store.
The date is easy to misunderstand. Google says Manifest V2 was already disabled for all users on current Chrome channels with Chrome 138 in July 2025, and enterprise support ended with the Chrome 139 policy change. Today’s event primarily closes the remaining store-distribution path.
Users should now identify any old productivity, privacy, accessibility, password, shopping or content-filtering extension they still rely on, record its settings and move to a maintained Manifest V3 replacement. Keeping an old browser to preserve one extension creates a larger security and compatibility problem.
What Chrome Users Should Do Today
Open Chrome’s extension manager, remove software you no longer use, identify disabled legacy extensions and replace important ones with actively maintained Manifest V3 versions. Export settings first when the extension supports it, then test the replacement before deleting the old profile.
- August 31 change: remaining Manifest V2 listings leave the Chrome Web Store.
- Old installations: may remain on Chrome 138 or earlier but cannot update or be reinstalled.
- Current Chrome: Manifest V2 was already disabled.
- Best response: use maintained V3 alternatives and keep the browser updated.
Manifest V2 Timeline in Plain English
| Date | Chrome change | User impact |
|---|---|---|
| March 31, 2025 | V2 disabled by default with temporary re-enable path | Transition warning period |
| July 24, 2025 | V2 disabled everywhere with Chrome 138 | Ordinary users cannot turn legacy extensions back on |
| Chrome 139 | Enterprise V2 availability policy removed | Managed exceptions end |
| August 31, 2026 | Remaining V2 extensions removed from Web Store | No updates or store reinstallation |
How to Audit Your Chrome Extensions
- Type chrome://extensions in the address bar.
- Enable Developer mode only if you need to inspect extension IDs; do not install unknown unpacked code.
- Create a list of every extension and the task it performs.
- Remove unused add-ons and investigate anything you do not recognize.
- Open the Web Store page for each essential extension and check recent updates, developer identity and privacy disclosures.
- Export settings or filter lists where supported, then test the replacement in a separate Chrome profile.
Fewer extensions reduce exposure
Every browser add-on receives some level of access. Keep only tools that provide a clear benefit, come from a verifiable publisher and continue to receive maintenance.
How to Choose a Manifest V3 Replacement
| Check | Good sign | Warning sign |
|---|---|---|
| Maintenance | Recent version history and clear changelog | No update for years or abandoned support page |
| Publisher | Identity matches an established project or company | Copycat name, misspelling or unknown redirect |
| Permissions | Access matches the extension’s function | Requests every site or browsing history without need |
| Privacy | Specific data-use disclosure and deletion path | Vague resale or advertising language |
| Migration | Imports settings from the former tool | Requires uploading sensitive configuration to an unknown site |
What Happens to an Extension on Chrome 138?
Google says a Manifest V2 extension installed on Chrome 138 or earlier may remain installed after store removal. That does not restore normal support: it cannot receive Chrome Web Store updates and cannot be reinstalled after removal. Chrome 138 is also an old browser branch, so retaining it for a legacy extension sacrifices security fixes and web compatibility.
Do not copy an extension directory between machines as an improvised migration. Side-loaded packages bypass normal store review and update controls, and a binary or script from an unverified mirror can be malicious.
Work and School Devices
Managed environments should use the replacement selected by their administrator. Employees should not disable policy, install a personal alternative or move corporate data into a consumer extension. IT teams should map each legacy extension to its business owner, data access, V3 successor and retirement date.
For broader update hygiene, see FrediTech’s Windows 11 KB5120998 guide, which explains why an optional preview update should be treated differently from routine security maintenance.
FrediTech Verdict
The August 31 cutoff is the end of distribution and updates for remaining Manifest V2 listings, not a surprise activation switch. Treat it as the final prompt to inventory your extensions, retire abandoned tools and migrate essential workflows to maintained V3 software without freezing Chrome on an insecure old release.
Frequently Asked Questions
Do all Manifest V2 extensions stop working on August 31, 2026?
No. Manifest V2 was already disabled in current Chrome. August 31 removes remaining V2 listings from the Web Store and ends store updates and reinstallation.
Can I reinstall a removed Manifest V2 extension?
Not from the Chrome Web Store after removal. Downloading copies from unofficial mirrors introduces substantial security risk.
Should I keep Chrome 138 for an old extension?
No. Keeping an outdated browser for one extension means missing browser security and compatibility updates. Migrate the workflow instead.
Is every Manifest V3 extension safe?
No. Review publisher identity, permissions, privacy terms, maintenance history and user reports before installing any extension.
Related FrediTech Guides
- Windows 11 KB5120998 Install Guide
- Acer Swift Neo AI India Buying Guide
- Nikon Image Space Backup Guide
Sources and Editorial Notes
The timeline and installation behavior are taken from Google’s official migration documentation. The article distinguishes store removal from the earlier browser disablement and avoids recommending unsupported side-loading.
