On August 31, after more than four years of warnings, deadline extensions, and one closed loophole, Google finished what it started: every extension still built on the old Manifest V2 framework was permanently pulled from the Chrome Web Store. Nothing about how those extensions worked changed that day — Chrome had already stopped running most Manifest V2 code back in mid-2025. What actually happened on August 31 is narrower, and for a specific group of power users, worse: the store itself, the only official channel for installing or updating these extensions, is now closed for good.
What Actually Died, and What Didn’t
The mechanics matter here because Google’s own rollout has been staged across more than a year. Manifest V2 extensions stopped executing on Chrome 138 and later back in mid-2025. A workaround that let some users re-enable disabled MV2 extensions anyway was closed off in June 2026. And as of August 31, Chrome 139 and newer versions exclusively support Manifest V3, with the Web Store itself no longer distributing MV2 code at all. Anyone still running Chrome 138 or older with a legacy extension installed can keep using it — but that extension can never be updated again, and if it’s ever uninstalled, or the browser reinstalled, or a new device set up, it cannot be reinstalled from the official store under any circumstances. Because the Chrome Web Store also supplies extensions to Microsoft Edge and other Chromium-based browsers, the removal effectively cuts off distribution for those browsers too, not just Chrome itself.
Google’s stated case for Manifest V3 rests on three real architectural changes: replacing extensions’ persistent background processes with event-driven service workers to cut memory use, especially on lower-end hardware; replacing raw network-request inspection with a more limited, declarative filtering API; and banning remotely hosted, unvetted code from running inside extensions at all, closing off a category of attack where a seemingly benign extension could quietly fetch and run malicious code after passing review. Those are legitimate security and performance arguments, and for most casual browsing, the difference is invisible.
The Extension Everyone Actually Noticed
The transition’s highest-profile casualty is uBlock Origin, the open-source ad and tracker blocker long considered the gold standard by privacy-focused users, and its removal is what turned a developer-forum debate into a mainstream story. The full version of uBlock Origin relied on Chrome’s older webRequest API, which let it inspect and block network requests with a level of granularity Manifest V3’s replacement — the declarativeNetRequest API — simply doesn’t allow. Chrome users are left with uBlock Origin Lite, a purpose-built, reduced-capability version designed to work within Manifest V3’s constraints; anyone who wants the full original extension now needs Firefox, which still supports the old architecture, or a Chromium-based holdout like Brave, Edge, or Opera, all of which have so far continued supporting the full version through their own extension stores.
The stakes here go beyond intercepted banner ads. Survey data on why people actually install ad blockers found that while 71% cite simply wanting fewer ads, 59% install them specifically to block malware and 54% cite privacy protection as their reason — meaning a meaningful share of the millions of people affected by this change picked their ad blocker as a security tool, not an annoyance filter. For that group, “install Lite instead” is a real downgrade in what the tool can actually do, not a cosmetic inconvenience.
The Bigger Pattern
What makes this moment more than a browser-settings story is what it says about who actually controls the extension ecosystem millions of people rely on daily. Chrome commands the largest share of the global browser market by a wide margin, which means Google’s architectural decisions about what an extension is allowed to do function less like one vendor’s product choice and more like a platform-wide policy that ad blockers, password managers, privacy tools, and countless business-productivity extensions all have to build around, whether their developers agree with the tradeoffs or not.
What This Means for Philippine Founders
Any Philippine company building a browser extension — for fintech transaction alerts, e-commerce price tracking, productivity tooling, or anything else — should treat this week’s cutover as the final, hard confirmation that Manifest V2 is not a supported target for new development, full stop, if Chrome and Chromium-based Edge are anywhere in the user base. More broadly, the uBlock Origin story is a useful case study for any local team building browser-based tooling on top of a platform API: the rules can change under a product with a genuinely enormous, security-critical user base, and building tightly around a single browser vendor’s current permissions carries real platform risk. For consumer-facing PH startups whose users lean on ad blockers or privacy extensions as part of their own security hygiene — particularly anything handling payments or personal data — it’s worth directly testing how the product behaves for users who’ve been pushed onto uBlock Origin Lite or a different browser entirely, rather than assuming ad-blocking behavior hasn’t changed.
Share this article