The store, not just the switch, is now closed
On August 31, 2026, Google removed every remaining Manifest V2 (MV2) extension from the Chrome Web Store, closing out a transition that began roughly four years earlier. The most-noticed casualty is the full-featured version of uBlock Origin, one of the most capable content blockers ever built for a browser, but it was far from the only extension affected - every listing still built on the old MV2 architecture is gone from Google's official store.
What actually changes for a user right now
The distinction that matters is between what is already installed and what can still be installed. Copies of MV2 extensions already running in a browser keep working for now; Chrome is not reaching into installed browsers and deleting them. What stops is everything downstream of that: no security patches, no bug fixes, no updated filter lists, and no way to reinstall the extension from Google's store if it is ever disabled or removed. Setting up a new computer, resetting a browser profile, or simply uninstalling the extension by mistake means it cannot be recovered through official channels, even with a direct link that used to work.
Google had already disabled most installed MV2 extensions on Chrome's stable channel earlier in the rollout, and closed off the last enterprise policy - ExtensionManifestV2Availability - that let organizations keep them running on managed fleets past mid-2025. The August 31 store purge is the final step in that sequence: the point at which Google stops distributing MV2 code at all, to anyone, through any official channel.
A four-year transition, not a sudden change
The shift away from MV2 has been telegraphed since 2022, when Google first began outlining Manifest V3 (MV3) as the successor extension platform. The practical phase for most users started in October 2024, when Chrome began disabling installed MV2 extensions on the stable channel in a gradual rollout, followed by the closure of workaround flags and enterprise exceptions through 2025. Extension developers had years of notice and a series of deadline extensions to migrate, which is part of why the strongest objections have focused less on the timeline itself and more on what MV3's technical limits mean for a specific category of extension: ad and tracker blockers.
Why Google is doing this
Google's stated reasons for retiring the old platform center on security and performance rather than content blocking specifically: MV2 allowed extensions to keep persistent background processes running that consumed memory indefinitely, granted broad access to inspect and modify network traffic through the webRequest application programming interface (API), and in some cases could execute code fetched remotely after installation, which made reviewing an extension's actual behavior harder for Google to audit. MV3 replaces the always-on background process model and restricts remote code execution, at the cost of also restricting how deeply an extension can filter network requests - which is precisely the capability the strongest ad and tracker blockers depended on.
What replaces the old extensions
There isn't a direct swap available inside Chrome itself. uBlock Origin's developer, Raymond Hill, has maintained uBlock Origin Lite, an MV3-compatible version that works within Chrome's new limits, but it relies on predefined filter lists rather than the more flexible, extension-controlled filtering the original version used, so it blocks less in some cases. Chrome users who want the original engine have two options outside Google's own store: switch to a Chromium-based browser that has chosen to keep hosting it - Brave has said it will continue serving four MV2 extensions, including full uBlock Origin, AdGuard, uMatrix, and NoScript, through its own backend rather than Google's - or move to Firefox, which has committed to continuing MV2 support and is the platform Hill himself now recommends for the extension. Other Chromium-based browsers, including Edge and Opera, currently still support the older extensions, but neither has made a long-term commitment the way Firefox and Brave have, since both ultimately build on Chromium's extension platform decisions.
What it means in practice
For most Chrome users, nothing changes today: existing extensions keep running. The risk builds over time, as those extensions go without security updates and their filter lists age against new tracking and ad-serving techniques. Anyone who relies on a strong ad or tracker blocker and wants to keep using the original uBlock Origin engine, rather than the lighter MV3 rewrite, now needs to make a deliberate choice - Brave or Firefox - rather than assuming Chrome will keep working as it has. For extension developers still shipping MV2-only code, the store removal is the actual deadline that matters; anything not migrated to MV3 is no longer distributable through Chrome's official channel at all, regardless of how long it keeps functioning on machines where it is already installed.
