Google has set a firm deadline: by August 31, 2026, all Chrome extensions using the old Manifest V2 format will be removed from the Chrome Web Store. After that date, these extensions can’t be updated, reinstalled from the store, or transferred to new devices through normal means.
This marks the final phase of Google’s multi-year transition to Manifest V3, a revamped extension framework designed to improve security and performance. Support for Manifest V2 was already disabled in Chrome in July 2025, followed by the removal of the browser flag that allowed users to bypass these restrictions. Now, Google is shutting down the last remaining avenue: server-based updates for extensions still published under the deprecated Manifest V2 standard.
For users, the practical takeaway is straightforward. Extensions installed before Chrome version 138 that run on Manifest V2 will keep working, but they’ll no longer receive updates. If you reinstall Chrome or switch to a new computer, you won’t be able to reinstall those extensions via the Web Store.
Google justifies this move by citing security concerns and the need to streamline extension performance. Manifest V3 limits how extensions interact with network traffic and disables certain APIs previously used to deeply inspect data flows. The biggest impact has been on ad blockers: for example, uBlock Origin’s Chrome version now effectively exists only as a simplified uBlock Origin Lite, with more limited filtering capabilities compared to earlier versions.
The switch from Manifest V2 to V3 has been in the works since 2019. Google initially announced Manifest V3 to tighten controls around extension permissions and privacy but faced strong pushback from developers. Organizations like the Electronic Frontier Foundation and ad blocker creators have argued that Manifest V3 weakens privacy tools, while Google maintains the older model was too risky and out of date.
This saga also highlights contrasting browser strategies worldwide. Mozilla Firefox continues to support APIs that allow powerful ad blockers and privacy extensions, while Chromium-based browsers-including Microsoft Edge-follow Chrome’s lead and phase out Manifest V2. August 2026 will therefore not just be a cleanup date for Chrome’s extension store, but a clear endpoint for the Manifest V2 era on the most widely used browser platform.
The deadline hits extension developers even harder. Google has already banned publishing new Manifest V2 extensions for some time, and now the final channel for maintaining old versions will disappear. Later in 2026, it will become clear which popular extensions successfully migrated to Manifest V3 and which are now relics preserved only in users’ personal archives.
As the clock ticks down, the big question remains: how many extensions will overcome Manifest V3’s stricter rules and retain their user base, and how many will quietly vanish? The next few years could reshape the extension ecosystem dramatically, forcing developers to balance functionality against Google’s tighter security demands.
Google’s Manifest V2 removal timeline and impact
- July 2025: Support for Manifest V2 disabled in Chrome; browser flag for bypass removed
- August 31, 2026: All Manifest V2 extensions removed from Chrome Web Store
- Post-deadline: Manifest V2 extensions cannot be updated, reinstalled, or transferred via the store
Why Google is transitioning from Manifest V2 to Manifest V3
- Improves security by limiting extension access to network traffic
- Streamlines performance with a revamped extension framework
- Disables certain APIs used for deep data inspection to protect user privacy
Manifest V3’s effect on ad blockers and privacy tools
- Ad blockers like uBlock Origin have reduced filtering capabilities under Manifest V3
- Some privacy-focused APIs removed or restricted
- Faced criticism from privacy advocates and developers
Browser strategies on extension support
- Mozilla Firefox continues supporting powerful ad blocker APIs
- Chromium-based browsers including Microsoft Edge phase out Manifest V2
- Chrome leads the transition with a strict Manifest V3 enforcement timeline