Google is weeks away from permanently disabling every Manifest V2 browser extension in Chrome, a change that will kill uBlock Origin and fundamentally limit what content blockers can do inside the world's most popular browser. Chrome 150, scheduled to reach the stable channel on June 30, 2026, removes the last MV2 override flag, and Chrome 151 will strip the remaining MV2 flags entirely. Once they're gone, there is no workaround, no enterprise policy override, and no hidden setting that will restore MV2 functionality (The Next Web, 2026).
What Exactly Is Changing in Chrome 150?
The technical change is straightforward. A Chromium code commit removes the ExtensionManifestV2Disabled flag, the last mechanism that allowed power users and enterprise administrators to keep MV2 extensions running. Google engineer Devlin Cronin confirmed the timeline in a Chromium code review, calling the flag infrastructure "dead code" since Chrome no longer officially supports MV2. Chrome 151, expected roughly four weeks later, will remove the remaining MV2-related flags: ExtensionManifestV2Unsupported, ExtensionManifestV2Availability, and AllowLegacyMV2Extensions (9to5Google, 2026).
Google first announced the Manifest V3 migration in 2019, arguing the new framework would improve security, privacy, and performance. The core technical change replaces the webRequest API, which let extensions intercept and modify network traffic in real time, with the declarativeNetRequest API, which requires extensions to submit static filtering rules in advance. That distinction matters enormously for ad blockers (Digital Trends, 2026).
Why This Kills uBlock Origin
uBlock Origin, the most widely used content blocker on Chrome with more than 40 million users, relies on dynamic filtering to block ads, trackers, and malicious content on the fly. Its developer, Raymond Hill, has stated plainly that a Manifest V3 version cannot replicate the original's full functionality. A lighter version called uBlock Origin Lite exists for MV3, but it supports only a fraction of the filter lists and cannot perform the cosmetic filtering that makes the original effective against modern advertising techniques (The Next Web, 2026).
The difference between the two APIs isn't academic. webRequest let extensions examine every network request a browser made and decide in real time whether to allow, modify, or block it. That's how uBlock Origin could adapt instantly to new tracker domains, rotating ad server IPs, and obfuscated malvertising campaigns. declarativeNetRequest forces extensions to declare every rule upfront, and Chrome enforces them natively. Extensions can't adapt without pushing an update through the Chrome Web Store review process, which can take days or weeks.
The Security Argument Has Merit. But It Also Has a Conflict.
Google's security case isn't without foundation. The webRequest API gives extensions deep access to every network request a browser makes, which means a compromised extension can silently intercept passwords, redirect traffic, or inject code into any page a user visits. A recent case illustrates the risk: the popular "Save Image As Type" extension, which had hundreds of thousands of users, was hijacked by a group calling itself Karma and silently modified to steal affiliate commissions from e-commerce transactions. The compromise went undetected for months (The Next Web, 2026).
But the conflict of interest is impossible to ignore. Google generated an estimated $239.5 billion in advertising revenue in 2025 and is projected to be overtaken by Meta as the world's largest digital advertising company in 2026, with Meta expected to reach $243.5 billion versus Google's $239.5 billion (Emarketer, 2026). Content blockers directly reduce the number of ads users see. While Manifest V3 doesn't ban ad blocking entirely, it caps the number of filtering rules an extension can apply and eliminates the dynamic blocking that makes tools like uBlock Origin effective against rapidly evolving ad-delivery systems.
The same company that built Chrome and sells the ads it displays also wrote the rules governing what ad blockers can do inside it.
— Reclaim the Net
CISA Says Ad Blockers Are a Security Layer. Chrome Is Weakening Them.
Here's where the backfire becomes undeniable. The US Cybersecurity and Infrastructure Security Agency, CISA, has recommended the use of ad-blocking software as a defense against malvertising, the practice of distributing malware through legitimate advertising networks. A 2024 CISA guidance document specifically cited ad blockers as a layer of protection against drive-by downloads and malicious redirects served through programmatic ad exchanges. The Manifest V3 migration weakens the most effective tool in that category on the browser used by roughly 65% of desktop internet users worldwide (CISA, 2024).
Malvertising isn't a theoretical threat. Attackers routinely compromise legitimate ad networks to serve malicious payloads through trusted websites. Without robust content blocking, users on Chrome become exposed to an attack surface that the US government itself has told them to defend against. Google weakening the tool CISA recommends is, at minimum, an awkward look. At worst, it puts millions of users at increased risk.
Where Do Users Actually Go?
Firefox, which is not built on Chromium and is not subject to Google's extension framework, continues to support Manifest V2 and uBlock Origin in full. Mozilla implemented its own version of Manifest V3 but maintained backward compatibility with the webRequest API, allowing content blockers to function without restriction. Brave, which is Chromium-based, has built its own ad-blocking engine directly into the browser, bypassing the extension framework entirely. Both are free and switching takes about ten minutes (The Next Web, 2026).
Microsoft Edge and Opera, both Chromium-based, are expected to follow Chrome's lead on MV2 deprecation. Switching to either of those browsers won't save your ad blocker. The practical alternatives narrow to Firefox for full-extension support or Brave for built-in blocking that operates at the browser engine level, outside the extension system altogether.
| Browser | Engine | MV2 Status | uBlock Origin | Built-in Blocking |
|---|---|---|---|---|
| Chrome 151+ | Chromium | Removed | Disabled | None |
| Firefox | Gecko | Supported | Full support | None |
| Brave | Chromium | Removed at extension level | Available but unnecessary | Shields (built-in) |
| Edge | Chromium | Following Chrome | Will be disabled | None |
| Opera | Chromium | Following Chrome | Will be disabled | None |
- Switch to Firefox for full uBlock Origin support (recommended for most users)
- Switch to Brave for a built-in Shields blocker that bypasses extensions entirely
- Install uBlock Origin Lite and accept reduced filtering capability
- Do nothing and let Chrome 150 silently disable the extension with a notification
The Browser Wars Just Got More Interesting
The MV2 shutdown arrives at a moment of unusual flux in the browser market. Google's Chromium dominance means most browsers share the same rendering engine, but the extension framework is where differentiation lives. Firefox has leaned into privacy as its core identity for years, and the MV3 fight validates that positioning. Brave has gone further by baking ad blocking into the engine itself, making the extension question irrelevant for its users.
The irony is that Google's push to standardize on Chromium was supposed to reduce fragmentation. Instead, it's pushing users toward the one major browser that isn't Chromium at all. Firefox downloads spiked in previous MV3 controversy rounds, and there's little reason to expect this time will be different. Mozilla has been quietly gaining ground among privacy-conscious users who see the MV3 transition as confirmation that Chrome's interests and theirs have diverged.
The Bigger Picture: Google's Two-Pronged Web Grip
The timing is notable. Google's AI search overhaul, announced at I/O 2026, is already accelerating a traffic collapse for publishers who depend on search referrals. AI-generated answers increasingly replace the need to click through to source websites. The simultaneous weakening of content blockers in Chrome means users will see more ads on the pages they do visit, while Google's own AI-generated answers increasingly replace those pages altogether. The combined effect tightens Google's grip on both the discovery and monetization layers of the web (The Next Web, 2026).
Consider the math from the publisher's perspective. Google's AI Overviews reduce click-through traffic, shrinking the audience that sees a publisher's ads. Meanwhile, the MV3 restrictions mean the users who do click through see more ads because their content blockers are less effective. Google wins on both sides: fewer clicks to publishers, and more ad impressions on the pages that survive. It's a squeeze play, and the publisher has no good move.
For the estimated 40 million uBlock Origin users on Chrome, the timeline is now concrete. Chrome 150 on June 30 removes the primary workaround. Chrome 151 in late July cleans up every remaining MV2 reference. After that, the only options are switching browsers, accepting uBlock Origin Lite's limitations, or browsing without any content blocker at all.
Google has framed the Manifest V3 transition as a necessary modernization of a platform that serves billions of users. The security concerns it cites are real, and the "Save Image As Type" hijacking is exactly the kind of incident a more restrictive API framework is designed to prevent. But the question of whether the same company that sells the ads should also control the tools available to block them is one that the technical merits alone do not answer. The answer, it seems, will be written by the users who leave.
Key Takeaways
- Chrome 150 (June 30) removes the last MV2 workaround flag; Chrome 151 (late July) removes all remaining MV2 infrastructure.
- uBlock Origin's 40 million Chrome users lose full-featured ad blocking. uBlock Origin Lite covers only a fraction of the original's capabilities.
- CISA recommends ad blockers as a defense against malvertising, directly contradicting Chrome's decision to weaken them.
- Firefox remains the best alternative for full uBlock Origin support; Brave sidesteps the issue with built-in engine-level blocking.
- Google's dual actions, weakening ad blockers while replacing publisher traffic with AI answers, tighten control over both web discovery and monetization.
- The Next Web — Google is about to disable uBlock Origin and every other Manifest V2 extension in Chrome
- 9to5Google — Google Chrome update will fully close the door on ad blockers
- Digital Trends — Chrome is removing the last workaround keeping Manifest V2 ad blockers alive
- The Next Web — Meta is about to overtake Google as the world's biggest advertising company
- CISA — Securing Web Browsers and Defending Against Malvertising (2024)
- The Browser Engine Wars: WebKit Loses Its Last Friend
- The Great Self-Hosting Boom: Why Everyone Is DIYing
- AI Slop Is Eating the Web. Here's What That Means for You.
Will uBlock Origin stop working in Chrome?
Yes. Chrome 150 (June 30) removes the last MV2 workaround, and Chrome 151 removes all MV2 infrastructure. uBlock Origin Lite exists but supports only a fraction of the original's capabilities.
What browser should I switch to for ad blocking?
Firefox fully supports Manifest V2 and uBlock Origin. Brave has built-in engine-level ad blocking through Shields. Both are free and switching takes about ten minutes.
Why is Google removing ad blocker support?
Google says Manifest V3 improves security. Critics note Google generated $239.5 billion in ad revenue in 2025, and the change weakens ad-blocking tools. CISA recommends ad blockers against malvertising.
Bottom line
Google has framed the Manifest V3 transition as a necessary modernization of a platform that serves billions of users. The security concerns it cites are real, and the "Save Image As Type" hijacking is exactly the kind of incident a more restrictive API framework is designed to prevent. But the question of whether the same company that sells the ads should also control the tools available to block them is one that the technical merits alone do not answer. The answer, it seems, will be written by the users who leave.
What we still don't know
This is a fast-moving story. We update the post as new facts land — and we'll flag it when we do.
Enjoyed this? Pay it forward
A sharp story is worth passing on. Share it with the people who read tech like it matters.
