What Manifest V3 Is and Why Chrome Is Switching
Manifest V3 Chrome is a newer extension framework that replaces Manifest V2, changing how browser add-ons request permissions, filter web traffic, and run code in the background, with the goal of improving security, privacy, and performance across the extension ecosystem. Google announced the transition away from Manifest V2 a few years ago and began moving users to Manifest V3 extensions in 2024. The company argues that keeping the old system alive adds “technical debt” and security risks, since engineers have found bugs specific to MV2 code. According to Google engineer Devlin Cronin, “we won't be able to provide / maintain this functionality indefinitely due to the complexity and tech debt, as well as the security risks it entails.” With the next major Chrome releases, Manifest V2 support will be fully removed, forcing all extensions to comply with the Manifest V3 Chrome rules.
How Manifest V3 Breaks Classic Ad Blockers Like uBlock Origin
The most controversial Manifest V3 Chrome change is the new rules-based filtering system, which limits what extensions can do with network requests. Under Manifest V2, powerful ad blockers like uBlock Origin Chrome could dynamically inspect and block traffic using custom code and large, frequently updated filter lists. Manifest V3 replaces this with a declarative API that caps the number of filtering rules and removes the dynamic blocking logic these tools rely on. As The Next Web explains, Manifest V3 “caps the number of filtering rules an extension can apply and eliminate the dynamic blocking that makes tools like uBlock Origin effective against rapidly evolving ad-delivery systems.” That means traditional uBlock Origin and similar privacy extensions cannot function at full strength under MV3, even if they are rewritten to meet the new requirements.
The Timeline: When Ad Blocker Support Is Ending in Chrome
The end of full ad blocker support in Chrome is no longer a distant plan; it is tied to upcoming Chrome extension changes in the next couple of releases. Chromium contributor Anton Bershanskiy notes that Chrome 149 is the last version with any remaining Manifest V2 compatibility hooks. From Chrome 150 onward, users will no longer be able to install MV2 extensions from the Chrome Web Store. Soon after, Chrome 151 will remove additional compatibility flags such as ExtensionManifestV2Unsupported, ExtensionManifestV2Availability, and AllowLegacyMV2Extensions. PCMag reports that once Chrome 150 and 151 are released, “it’s on to Manifest V3,” and MV2 extensions are “no longer allowed in any supported version of Chrome.” Chromium-based browsers like Edge and Opera inherit these changes, so uBlock Origin Chrome users on those platforms will also lose MV2-based ad blocker support.
Alternatives: uBlock Origin Lite, Firefox, and Other Options
With ad blocker support ending for Manifest V2 in Chrome, users dependent on uBlock Origin Chrome have a few paths forward. One option is uBlock Origin Lite, a Manifest V3-compatible extension. However, reports note that the Lite version allows some tracking, uses a much smaller blocklist than the original, and cannot perform the same dynamic filtering, so protection is weaker. For those who want full-strength uBlock Origin, switching browsers is the most reliable workaround. Mozilla has said it has no plans to abandon Manifest V2, and Firefox’s Gecko engine still supports the classic uBlock Origin with all its features. On the uBlock Origin subreddit, users emphasize that “uBO works best on Firefox,” making it the main refuge for people who want powerful, customizable blocking rather than the more limited MV3 model.
What This Shift Means for the Future of Browser Extensions
The Chrome extension changes driven by Manifest V3 mark a turning point for how browsers balance control between users, developers, and the browser vendor. By cutting off Manifest V2, Google is standardizing extensions around a more locked-down model, with strict limits on what code can do to network traffic and how long background logic can run. Google frames this as a security and reliability upgrade, and there are benefits: fewer long-lived background scripts, clearer permission scopes, and a more predictable API surface. But the trade-off is less flexibility for advanced tools, especially privacy and security extensions that depend on granular, real-time filtering. Other engines, such as Firefox’s Gecko, become more important for users who want that level of control. The end of uBlock Origin on Chrome signals a broader shift toward curated, constrained extension ecosystems.
