Chrome’s Store Purge Makes Manifest V2 Extensions Unrecoverable

Google removed every remaining Manifest V2 extension from the Chrome Web Store on August 31, 2026. Copies that still sit on Chrome 138 or earlier stay installed, but they no longer get updates and they cannot be put back from the store once they leave a machine.

Stable Chrome already stopped running those extensions in July 2025. The August wipe closes the last official way to find, install, or patch them.

Google Emptied the Store of Manifest V2 Listings

The all remaining Manifest V2 extensions removed line on Chrome’s own timeline is the distribution cutoff, not the first time the old platform stopped working. Chrome 138, shipped around July 24, 2025, disabled Manifest V2 for users on every channel and took away the toggle that had let people turn those add-ons back on.

Enterprise holdouts lasted one more version. The ExtensionManifestV2Availability policy, which IT teams used to keep Manifest V2 running, is removed with Chrome 139, and that cut hits every profile on 139 at once. Chrome 138 is the last build that can still load Manifest V2 when that policy key is set.

The store step is colder than a disable flag. Listings are gone from search and from the catalogue. A direct link does not bring them back. A developer cannot push a filter-list update, a security fix, or a version bump through Google’s servers.

HOW GOOGLE CLOSED MANIFEST V2

1. January 2022: The Chrome Web Store stops accepting new public and unlisted Manifest V2 extensions.
2. June 2022: The store stops accepting new private Manifest V2 extensions.
3. June 3, 2024: Warning banners begin on Beta, Dev, and Canary, and Featured badges drop off remaining Manifest V2 items.
4. October 9, 2024: Stable Chrome starts disabling installed Manifest V2 extensions, with a short window to turn them back on.
5. March 31, 2025: Manifest V2 is off by default on all channels; a re-enable path still exists for a while.
6. July 24, 2025: Chrome 138 disables Manifest V2 everywhere and removes the re-enable toggle.
7. Chrome 139: The enterprise policy that still allowed Manifest V2 is removed.
8. August 31, 2026: Remaining Manifest V2 listings are deleted from the Chrome Web Store.

Google’s stated reasons have not moved. Manifest V3 replaces always-on background pages with event-driven service workers, hands network blocking to the Declarative Net Request engine inside Chrome, and bans remotely hosted code so reviewers see the scripts that actually run.

Leftover Copies Survive Only on Chrome 138

The timeline’s fine print is easy to miss if you only read “Manifest V2 is dead.” Google says Manifest V2 extensions installed on Chrome 138 or earlier remain installed after the store wipe. They just cannot receive updates, and they cannot be reinstalled from the Chrome Web Store once they are removed from Chrome.

That leftover population is not the typical auto-updated desktop. Anyone on current stable Chrome lost the runtime more than a year ago. The people who still have a working binary are on old builds, frozen images, or managed fleets that never left 138 with the policy key turned on.

Those copies are now static. Filter lists go stale. Bug fixes stop. If the extension is disabled on chrome://extensions, or uninstalled in a cleanup, Google’s store will not hand it back. The file on disk is a souvenir that still runs only for as long as that old Chrome stays old.

Chromium forks that still pulled packages from Google’s catalogue lose that pipe on the same day. The engine can keep Manifest V2 code in a fork. It cannot restock from a store that no longer carries the files.

What a Factory Reset Now Costs You

The second-order hit is not a new crash on a machine that already updated. It is what happens the next time Chrome is new. A wiped Chromebook, a reinstalled Windows profile, a fresh Mac user, or a cloned enterprise image that does not pin Chrome 138 comes up against an empty shelf.

WHAT THE STORE WIPE MAKES PERMANENT

• New machines: A new Chromebook or a clean Chrome install cannot download a Manifest V2 extension, even with an old bookmark or a remembered item ID.
• Reinstalls: Uninstalling a leftover copy, or turning it off and later looking for it again, has no official recovery path.
• Updates: Developers cannot ship security patches or filter refreshes through the Web Store to any remaining install.
• Managed fleets: The ExtensionManifestV2Availability override does not exist on Chrome 139 and later, so an upgrade ends the exception for the whole fleet at once.

The louder fight this week still treats the date as the death of ad blocking in Chrome. That fight is a year late for anyone who stayed on current Chrome. The date that actually changed on August 31 is recoverability: leftover binaries cannot be restocked, and every future Chrome starts with no path back.

Raymond Hill Refuses to Pretend Lite Is uBlock Origin

uBlock Origin is the extension most people name when they talk about this purge. Developer Raymond Hill shipped 1.74.0 on August 25, 2026, and the project called that the last stable build expected to reach Google’s store. The README on GitHub now carries a Chrome Web Store listing marked removed on August 31, 2026.

Hill already built a Manifest V3 product, uBlock Origin Lite. He will not let the store silently swap one for the other.

I consider uBO Lite to be too different from uBO to be an automatic replacement. You will have to explicitly find a replacement to uBO according to what you expect from a content blocker.

Raymond Hill, uBlock Origin developer, uBO Lite FAQ

He wrote in that same FAQ that Lite is too different to be an automatic replacement, and that only the user can judge whether the sites they visit need the pieces that never moved to Manifest V3. Dynamic filtering, per-site “no remote fonts” and “no scripting” switches, and several filter options do not map onto Declarative Net Request. CNAME uncloaking is still missing from DNR implementations.

Generic cosmetic filtering is on by default in uBlock Origin. In Lite you raise the mode to Complete to get it. Hill also notes Lite is weaker against sites that fight blockers, because many filters cannot be turned into DNR rules.

UBLOCK ORIGIN AND LITE ON CHROME

Hill says the DNR cap is not the crisis it was in early Manifest V3 drafts. Extra annoyances, privacy, and regional rulesets push Lite a little above 30K rules, still under Chromium’s 330K global ceiling if you are not stacking other blockers. The default set sits near 17K.

The uBlock Origin Lite on the Chrome Web Store listing shows 19 million users, a 4.5 rating from 3.5K reviews, and a September 1, 2026 update (version 2026.901.1442). That is the supported Chrome path from the same developer. It is also a different product, which is why Hill refused an automatic migration.

Firefox, Brave, and the Remaining Homes

Full uBlock Origin did not vanish. It left Google’s shelf. Firefox still ships the complete extension on its own add-ons site, and the Firefox account said in August, “Our support for uBlock Origin isn’t going anywhere.” Mozilla’s Gecko stack still lets extensions intercept requests in ways Chromium’s Manifest V3 engine does not.

Brave runs on Chromium and still chose not to follow the store cutoff. It hosts uBlock Origin, AdGuard, NoScript, and uMatrix on its own servers and surfaces them under Settings, Extensions, Manifest V2 extensions (or brave://settings/extensions/v2). Users who had installed uBlock Origin from Google’s store need that Brave-hosted copy if they want updates after the purge.

https://x.com/brave/status/2087227867646079410

The practical fork is now blunt. Stay on current Chrome and you get Lite, or another Manifest V3 blocker, with Chrome applying packaged rules. Move to Firefox, or to Brave’s self-hosted Manifest V2 list, and the original engine still runs. GitHub still publishes Chromium Manifest V2 builds for manual install, with the usual warning that those packages will not auto-update.

The argument that this was only about memory on cheap Chromebooks does not explain why the catalogue had to disappear. Service workers and DNR already shipped. Deleting the listings is what stops a reset, a new laptop, or a Chromium browser that still trusted Google’s store from ever bringing the old extensions back.

Microsoft Put Edge on a Delayed Clock

Microsoft is walking the same road on a lag. Its developer docs put a Manifest V2 warning in Partner Center in August 2026 and describe a consumer transition by the end of 2026, with enterprise deprecation expected to begin in early 2027. The Windows blog language quoted on the uBlock Origin README is the same: consumer move starting in August 2026, finished by year end, enterprises the next year.

WHERE FULL UBLOCK ORIGIN STILL RUNS

Opera and other Chromium browsers that still ingest Google’s store lose that catalogue with Chrome. A fork can keep the old APIs only if it maintains them itself, the way Brave did for a short list.

Current Chrome users who want blocking keep Lite, or they leave. Anyone still sitting on a Chrome 138 image should treat that leftover copy as unpatchable. The next reset, the next new Chromebook, and the next fleet upgrade will not get those extensions back from Google.

Frequently Asked Questions

Does uBlock Origin Lite Update Filter Lists on Its Own?

No. Lite does not keep remote filter lists the way classic uBlock Origin does. Hill’s FAQ says the lists are compiled into declarative rulesets and scripts when the extension package is built, so those rules change only when the extension itself updates, and Lite never makes network requests to remote servers for lists.

Will Chrome Replace uBlock Origin With Lite Automatically?

No. Hill said Chrome will not migrate an old uBlock Origin install to Lite, and he will not treat Lite as the same product in the store. Users who want Lite have to install that listing themselves, which is why the two items kept separate identities through the purge.

Which Policy Values Used to Keep Manifest V2 Alive at Work?

ExtensionManifestV2Availability accepted four integers on Chrome and ChromeOS from version 110 through 138: 0 for default browser behavior, 1 to disable Manifest V2, 2 to enable it, and 3 to enable it only for force-installed extensions. Chrome 139 removes the policy, so those values no longer do anything on current Chrome.

Can You Still Sideload Manifest V2 Builds From GitHub?

The uBlock Origin project still posts Firefox, Chromium Manifest V2, and Thunderbird packages on GitHub Releases and says the Chromium builds must be placed manually and usually will not auto-update. Current Chrome 139 and later will not run Manifest V2, so a GitHub file does not revive the extension on an updated Chrome; it only matters on a browser that still loads that platform.