On 1 September 2026, Google reached a milestone that has been years in the making: all remaining Manifest V2 extensions were removed from the Chrome Web Store. Among them was uBlock Origin, one of the most effective and widely trusted content blockers ever built for the browser. The company’s position is that the newer Manifest V3 platform provides stronger security, privacy, and performance — and it has been transparent about the transition. But the practical outcome is that a tool relied upon by millions to shape their own online experience has been made unavailable through the largest extension marketplace on the web.
The consequences reach beyond Google Chrome itself. Most Chromium-based browsers, including Brave, Edge, and Opera, use the Chrome Web Store as their primary source for extensions. So even if a browser still supports Manifest V2 at the engine level, its users can no longer find or install these extensions through the store. Brave has responded by hosting four popular MV2 extensions — AdGuard, uBlock Origin, uMatrix, and NoScript — on its own backend, allowing users to enable them manually. It is a useful workaround but also a sign of how dependent the ecosystem has become on a single distribution channel.
From a developer’s perspective, this is about more than one extension. It is a shift in who decides what code can run in the browser. The Manifest V3 framework imposes stricter limits on what extensions can do, particularly around network request modification — the very capability that makes content blockers effective. Developers who built their tools on the old system must now either accept reduced functionality or find alternative platforms. For many, the path of least resistance is to comply, which quietly narrows the range of what browser extensions can achieve.
There is a legitimate case for tightening extension permissions. Poorly designed or malicious extensions have caused real harm, and the Chrome Web Store has struggled with review quality. But the removal of uBlock Origin also highlights a tension between platform security and user agency. When a browser vendor controls both the rendering engine and the extension marketplace, a single decision can reshape the available tools for billions of users — often without their direct awareness. The web’s historical strength has been its openness, allowing anyone to build and distribute tools that modify the browsing experience. That openness is now being redefined by a small number of gatekeepers.
The Islamic concept of Al Baari — the Maker of Order — reminds us that order is not an end in itself; it is meant to serve justice and benefit. A well-ordered system should protect users without removing their ability to choose what happens on their own devices. The hadith about the sanctity of Mecca, where even the cutting of thorny bushes was prohibited, points to the idea that some spaces carry a trust that should not be lightly altered. The open web is not a sanctuary in the religious sense, but it has functioned as a commons where innovation and user control could flourish. When that commons is managed through a single store, the trust shifts from the user to the platform.
For developers and users alike, the removal of Manifest V2 extensions is a reminder that browser choice matters. Firefox continues to support both Manifest V2 and V3, and independent efforts like the Ladybird browser project are building new engines from scratch. The tools exist to maintain a browser ecosystem that respects user autonomy. The question is not whether Google is acting in good faith — it likely is, from its own security standpoint — but whether a healthy web can afford to have one company’s definition of safety override the distributed decision-making that made the web powerful in the first place. That is a conversation that belongs to every developer who writes for the browser, and every user who installs an extension. It is not a technical question alone; it is a question about who gets to shape the digital world.