Chrome phasing out Manifest V2, impacting ad blockers

🔑 Enhanced Key Takeaways

•Google's stated rationale for transitioning to Manifest V3 includes improving security, performance, and user privacy by limiting extensions' access to sensitive data and preventing malicious code execution.
•The declarativeNetRequest API, which replaces the blocking webRequest API, requires extensions to pre-define filtering rules, significantly limiting dynamic filtering capabilities and the total number of rules an ad blocker can apply.
•The developer of uBlock Origin has created a limited version, uBlock Origin Lite, to comply with Manifest V3, which sacrifices some features and effectiveness compared to the full Manifest V2 version.
•Mozilla Firefox has explicitly stated its intention to continue supporting the blocking webRequest API and Manifest V2 alongside Manifest V3, offering a different approach to extension capabilities.
•Beyond ad blockers, Manifest V3 also mandates the replacement of persistent background pages with event-driven service workers and prohibits remotely hosted code, aiming to reduce resource usage and enhance security.

📊 Competitor Analysis▸ Show

Feature/Browser	Google Chrome	Mozilla Firefox	Brave
Manifest V2 Support	Phased out; Chrome 149 is the last version with full support, with workarounds removed in Chrome 150/151.	Continues to support Manifest V2 and the blocking `webRequest` API alongside Manifest V3.	May continue supporting some privacy-relevant MV2 extensions (e.g., uBlock Origin, AdGuard) for the time being.
Manifest V3 Implementation	Fully transitioned, enforcing `declarativeNetRequest` and service workers.	Implements Manifest V3 but retains blocking `webRequest` API and supports both V2 and V3.	Based on Chromium, so it will eventually adopt MV3, but its built-in ad blocker ("Brave Shields") operates independently of extension restrictions.
Ad Blocker Impact	Full uBlock Origin no longer available; users must use uBlock Origin Lite with limited functionality.	Full uBlock Origin continues to work effectively due to continued `webRequest` API support.	Built-in Brave Shields block ads and trackers by default, independent of MV2/MV3.

🛠️ Technical Deep Dive

API Replacement: Manifest V3 replaces the webRequest API's blocking and modification capabilities with the declarativeNetRequest API.
Declarative vs. Programmatic: webRequest allowed extensions to dynamically inspect and modify network traffic in real-time using JavaScript. declarativeNetRequest requires extensions to provide a pre-defined, static list of rules to the browser, which then handles blocking or modification without exposing request details to the extension.
Rule Limitations: The declarativeNetRequest API imposes limits on the number of filtering rules an extension can use (e.g., 330,000 rules, up from an initial proposal of 30,000), which is significantly less than the dynamic filtering rules used by extensions like uBlock Origin (e.g., 300,000+).
Background Script Model: Manifest V3 replaces persistent background pages with event-driven service workers. Unlike persistent pages that could run continuously, service workers wake up only when needed and can shut down when idle, reducing resource usage but making long-running tasks harder.
Remote Code Prohibition: Manifest V3 prohibits extensions from executing remotely hosted code. All JavaScript must be bundled within the extension package, which is subject to Chrome Web Store review, aiming to enhance security by preventing malicious code injection after initial review.
Unified Action API: Manifest V3 unifies browser_action and page_action into a single chrome.action API.

🔮 Future ImplicationsAI analysis grounded in cited sources

User adoption of alternative browsers will increase among privacy-conscious users.

Browsers like Firefox and Brave, which maintain stronger ad-blocking capabilities or built-in ad blockers, will become more attractive to users seeking robust content control.

The effectiveness of ad-blocking and privacy extensions in Chrome will be permanently reduced.

The limitations of the declarativeNetRequest API and the inability to dynamically filter requests will make it harder for Chrome extensions to adapt to evolving ad formats and tracking methods.

Google's advertising revenue may see a slight increase due to reduced ad-blocking efficacy in its dominant browser.

By limiting the capabilities of ad blockers, a larger percentage of ads, including Google's own, are likely to be displayed to Chrome users.

⏳ Timeline

2018

Google outlines a plan for "Trustworthy Chrome Extensions, by default" as part of Manifest V3.

2021-01

Chrome Web Store starts accepting Manifest V3 extensions.

2022-01-17

The Chrome Web Store stops accepting new Manifest V2 extensions.

2023-06

The Chrome Web Store no longer allows Manifest V2 extensions to be published with public visibility.

2025-07-24

Manifest V2 becomes disabled everywhere in Chrome, with the re-enable option removed.

2026-06-02

Chrome 149, the last version with full support for legacy Manifest V2 extensions, is released to stable.

Chrome phasing out Manifest V2, impacting ad blockers

⚡ 30-Second TL;DR

Key Points

🧠 Deep Insight

🔑 Enhanced Key Takeaways

🛠️ Technical Deep Dive

🔮 Future ImplicationsAI analysis grounded in cited sources

⏳ Timeline

📎 Sources (21)

👉Related Updates

Great Wall Wey V8X EV SUV Specs Revealed

US DoD launches low-cost drone swarm project

LG Display study: High refresh rates improve FPS accuracy