Chrome 150 removes Manifest V2 support June 30, ending uBlock Origin and rival extensions

Google is weeks away from permanently disabling every Manifest V2 browser extension in Chrome. If you run, fund, or build anything in the content-blocking space, the practical headline is simple: this move is designed to kill uBlock Origin and fundamentally limit what content blockers can do inside the world’s most popular browser.

The deadline is June 30. That is when Chrome 150 is scheduled to reach the stable channel, and that release will remove the ExtensionManifestV2Disabled flag, which the piece describes as the last mechanism enabling Manifest V2 extensions to function.

To understand why this matters, it helps to translate “Manifest V2” out of the weeds. Browser extensions rely on a manifest, a structured file that tells the browser what the extension is, what permissions it needs, and how it integrates with the browser. Manifest V2 became the default for many existing extensions because it was widely supported for a long time. Over time, Google pushed developers toward newer extension capabilities and architectures, and Manifest V2 gradually lost ground. The Next Web’s report is basically saying the long runway is ending: the last safety valve is being removed, so the remaining V2 extensions lose their way to operate.

uBlock Origin is the obvious name because it is a flagship content blocker, widely used and commonly referenced in conversations about ad load, tracking, and unwanted scripts. But the impact is broader than one extension. The source frames the change as “permanently disabling every Manifest V2 browser extension in Chrome,” meaning the blast radius covers many competitors, not just the single most famous extension.

This is not just a developer inconvenience. It is a platform policy shift that changes the economics of the whole category. Content blocking sits at the intersection of user behavior and publisher incentives. When blockers can work effectively, users experience faster pages, fewer intrusive ads, and less tracking. When blockers are weakened or forced into different technical constraints, the same user behavior can translate into different revenue outcomes for publishers and different costs or friction for platforms. Even if the extension makers keep up, “keeping up” means engineering time, new compliance work, and revalidation of what does and does not work under the new rules.

There is also a trust and governance dimension. Content blockers are a frequent target in the broader debate about how the web should balance privacy and openness with ad-supported business models. Regulators have been watching browser gatekeeping for years, especially where platform-wide changes can reshape competition without necessarily changing the user interface in a dramatic way. A change like this can look technical on the surface, but it has real-world consequences: it can alter which tools can operate, how they operate, and therefore what users can practically control.

For executives, the second-order effect is that Chrome policy timelines become operational risk. If your product relies on browser extension ecosystems, you need a plan for breakpoints that do not require a software update from your side. The key date here is not a vague “sometime this year.” It is a specific stable-channel milestone tied to Chrome 150 and a specific internal mechanism being removed, the ExtensionManifestV2Disabled flag. When Google removes that kind of switch, extensions do not just “degrade.” They lose the mechanism that allowed them to exist under the old model.

Board-level stakes are straightforward: platform changes can rapidly reduce optionality across adjacent markets. Extension developers may need to migrate, rebuild, or redesign feature sets to fit whatever newer extension model is allowed. Ad tech and analytics teams can see tracking behavior shift. Publisher and brand stakeholders can see traffic quality and user engagement change. Even companies that do not directly build extensions can be affected because user adoption and browsing friction can ripple through performance, measurement, and conversion.

Bottom line: Chrome is getting more decisive, not more permissive. With Chrome 150 set to reach stable on June 30 and the ExtensionManifestV2Disabled flag removed, the report is signaling the end of the line for Manifest V2 browser extensions in Chrome. That is a big deal because uBlock Origin and other content blockers are not minor add-ons. They are a core lever users use to shape how they experience the open web.