Chrome Finally Changed the Locks on uBlock Origin

Imagine renting an apartment for a decade, then getting a notice that the landlord is replacing every door in the building. The new doors are safer, they say. Stronger frames, better hinges. But your key doesn’t fit, and the locksmith who made it has decided he’s not making a new one for this building. That’s roughly where Chrome users stand with uBlock Origin right now.

The Manifest V2 shutdown has been coming for years. Google announced it, delayed it, announced it again, and the extension community treated each postponement like a stay of execution. That period is over. MV2 extensions have been pulled from the Chrome Web Store, uBlock Origin included, and BleepingComputer reported Chrome now warns users the extension may soon be disabled outright. Tech Times pegged June 30 as the point where dynamic filtering ends and the last workaround closes.

Why the workarounds mattered more than people realized

For a while there was a shell game happening. Users flipped enterprise policy flags, toggled the extension-unpacking settings, or relied on dynamic filtering to keep the old behavior alive. All About Cookies covered the closure of that last gap, and it’s the part I find most telling as someone who reviews tools for a living.

A workaround is a signal. When a large chunk of a user base is willing to edit registry keys or fiddle with policy configs to keep one extension running, that’s not nostalgia. That’s a functional gap in the replacement. MV3’s declarativeNetRequest model asks extensions to hand a list of rules to the browser and step back. uBlock Origin’s design depends on watching requests as they happen and deciding in the moment. Those two approaches don’t reconcile with a compatibility shim. You either get one or the other.

uBlock Origin Lite is not the same product

This is where I’d caution anyone reading a “just switch to Lite” recommendation without asking what gets lost. Lite exists, it works within MV3, and for a lot of casual browsing it will be fine. But calling it a drop-in replacement flattens a real difference in capability. If you were using uBO for its filtering precision, per-site rules, and the ability to react to what a page actually does rather than what a static rule anticipated, Lite is a step down. Not a scam, not vaporware, just less.

Cybernews noted that development continues on Firefox. That’s the honest read on the situation: the tool didn’t die, it moved. Firefox still supports the extension model uBO was built for, and Raymond Hill has been consistent about where his attention goes.

What this says about building on someone else’s platform

I write about toolkits constantly, and this is the pattern I keep circling back to. Every tool that lives inside a platform you don’t control carries a dependency you can’t audit. Chrome’s extension API was never a contract. It was a permission, and permissions get revoked when the platform owner’s priorities shift.

Google’s stated reasoning is security and performance, and there’s a defensible case in there. Extensions with wide-open request interception are genuinely a large attack surface. Plenty of sketchy extensions abused exactly that access. But the same change that closes that surface also narrows what a good-faith developer can build, and the company making the call happens to run the largest ad business on the planet. Both things can be true at once. You don’t need a conspiracy to notice the incentives line up conveniently.

Practical options right now

• Move to Firefox if content filtering is a real requirement for you. It’s the only path that keeps the full tool intact.
• Accept uBlock Origin Lite on Chrome if you want to stay put and can live with static rule sets. Set expectations accordingly.
• Consider DNS-level or network-level blocking as a supplement. It doesn’t replace in-browser filtering, but it covers ground the browser can’t.
• Stop assuming a browser extension is permanent infrastructure. If your workflow can’t survive an extension disappearing, that’s a fragility worth designing around.

The honest verdict

Chrome is still a fast, capable browser with an enormous extension catalog. It just made a decision that meaningfully reduces what one specific category of extension can do, and it did so after years of warnings that many users chose to treat as noise. Nobody was ambushed here.

What I’d push back on is the framing that this is a small adjustment. For users who cared about filtering, it isn’t. The tool they chose no longer runs in the browser they use, and no amount of positive spin about API modernization changes that arithmetic. If you’re one of those users, the migration is annoying but the answer is clear. If you’re not, this is still a useful lesson in how quickly the ground under a favorite tool can move.

🕒 Published: September 1, 2026