Google Removes All Manifest V2 Extensions from Chrome Web Store

Google just yanked uBlock Origin from the Chrome Web Store—not by accident, but as the final step in a years-long purge of Manifest V2 extensions.

That matters because the Chrome Web Store isn’t just another app store; it’s the only marketplace most Chromium-based browsers let you use. Brave, Edge, Opera, Vivaldi—all of them pull their extensions from the same place. When Google flips the switch on something this big, it stops being a browser decision and becomes an ecosystem one.

Technical Overview

The Android browser landscape hasn’t changed much in years, but recent shifts in WebView make it worth a closer look. Chrome remains the default WebView provider on most devices, but Firefox for Android now bundles its own Gecko-based WebView that can replace it. This isn’t just about removing Google dependencies—Firefox’s WebView is a fully functional alternative with its own quirks.

For most users, the swap is seamless. Firefox’s WebView integrates with the browser itself, so tabs and session management stay consistent whether you’re viewing web content in Firefox or another app. Under the hood, it uses Mozilla’s Gecko engine, which means differences in JavaScript performance and CSS rendering compared to Blink (Chrome’s engine). Benchmarks aren’t always reliable here, but Gecko tends to handle complex layouts and heavy JS slightly worse than Blink in controlled tests. That said, the gap isn’t massive—unless you’re pushing WebGL or heavy animations, the experience feels close enough.

The real advantage comes from avoiding Chrome’s update cycle. On Android, WebView is tied to system updates, which means security patches and new APIs arrive whenever your OEM pushes them. Firefox’s WebView updates independently, so you get fixes faster. The tradeoff is app compatibility: some sites and SDKs assume Blink and behave differently under Gecko. Rarely enough to break things, but enough to notice if you’re testing edge cases.

If you want to try it, the setup isn’t complicated. First, install Firefox for Android from the Play Store. Then, open Firefox, go to about:config, and search for webview.use_firefox. Set it to true. Some devices might require enabling developer options first. After that, apps using the system WebView will silently fall back to Gecko.

adb install org.mozilla.firefox

adb shell am start -n org.mozilla.firefox/org.mozilla.gecko.webview.WebViewActivity

The links in your quotes hint at the bigger picture: if you’ve been avoiding Chrome for years, Firefox’s WebView gives you an escape hatch without losing core functionality. It’s not perfect, but it’s a viable alternative—and one that’s getting better with each release.

Industry Impact

Manifest V2’s extinction isn’t just another version bump—it’s the first time Chrome has forcibly stripped functionality from extensions users actually rely on. uBlock Origin, AdNauseam, and dozens of other high-impact blockers are gone from the store, not because they’re buggy or abandoned, but because their architecture no longer fits Chrome’s security model. The migration path was technically open, but the friction was real: Manifest V3’s service worker model demands constant revalidation of persistent state, and many extensions simply can’t afford the latency or resource cost of restarting workers every few seconds. Google framed this as a security win, but the practical effect is that some of the most effective privacy tools no longer exist in the platform where they’re needed most.

What this reveals is less about Chrome’s dominance and more about its brittleness when dealing with power users. The same team that spent years warning developers about MV2’s impending removal then shipped a replacement that breaks core behaviors those same tools depend on. Firefox’s response—keeping the legacy extension APIs alive through its own MV2 fork—isn’t altruism; it’s a recognition that Chrome’s security theater comes at the cost of actual user agency. Safari’s occasional usefulness for web dev still doesn’t offset its glacial pace on standards, but at least it doesn’t pretend to care about tinkerers while dismantling their tools.

I don’t think Firefox will win back a meaningful share of Chrome refugees, but I do think users are going to notice the gaps. Without ad blockers that actually work, the web becomes louder, trackers more aggressive, and the promise of a clean browsing experience a relic. Chrome’s not removing extensions because they’re dangerous; it’s removing them because it never wanted them that powerful in the first place.

Conclusion

The fact that Google finally yanked all Manifest V2 extensions,uBlock Origin included,from the Chrome Web Store in September 2026 isn’t just a technical footnote. It’s the moment where most Chromium users woke up to an ecosystem where their ad blocker, script blocker, and privacy tools are no longer a one-click install from the dominant storefront. Brave’s workaround of hosting four MV2 holdouts isn’t a fix; it’s a finger in the dam. The real question isn’t whether Chrome’s move was inevitable,it was,but what happens when the next adblocker, the next privacy tool, hits the same wall.