Google to Disable Manifest V2 Extensions in Chrome

🔑 Enhanced Key Takeaways

•Google's stated rationale for Manifest V3 is to enhance security, privacy, and performance by limiting the extensive permissions granted to Manifest V2 extensions and preventing malicious code execution.
•Manifest V3 replaces persistent background pages with event-driven service workers, which are ephemeral and wake up only when needed, aiming to reduce resource usage but making long-running tasks more challenging for developers.
•A key technical change is the deprecation of the blocking webRequest API in favor of the declarativeNetRequest API, which requires extensions to pre-declare filtering rules, thereby limiting dynamic, real-time content modification capabilities crucial for advanced ad blockers.
•Manifest V3 also prohibits remotely hosted code, requiring all JavaScript to be included within the extension package, which aims to reduce security risks from unreviewed code but impacts rapid hotfixing and updates.
•The transition has been controversial, with critics arguing that while security and performance are cited, the changes disproportionately benefit Google's ad-driven business model by weakening ad-blocking capabilities.

📊 Competitor Analysis▸ Show

Feature/Browser	Google Chrome	Mozilla Firefox	Microsoft Edge	Brave Browser	Apple Safari
Manifest V3 Adoption	Mandatory for new extensions since Jan 2022; V2 disabled in stable since Oct 2024, fully by July 2025.	Supports both V2 and V3; V3 is less restrictive than Chrome's, no immediate plans to deprecate V2.	Embraced MV3 for reduced fragmentation, enhanced privacy, security, and performance; new MV3 extensions accepted since July 2022.	Force-enabled MV2 support for some privacy extensions; native ad blocker (Brave Shields) operates independently of MV3.	Uses Safari App Extensions bundled with macOS apps, not directly comparable to WebExtensions MV2/MV3.
`webRequest` API (Blocking)	Deprecated in favor of `declarativeNetRequest` API; blocking capabilities removed.	Still supports `browser.webRequest` blocking in MV3, allowing powerful ad blocking.	Supports `declarativeNetRequest` API; claims changes will not compromise extension capabilities.	Brave Shields uses a native ad-blocking engine, sidestepping `webRequest` limitations; continues to support MV2 `webRequest` for some extensions.	Ad-blocking capabilities are generally weaker; best ad-blocking apps often run as desktop applications communicating with an extension.
Impact on Ad Blockers	Full uBlock Origin no longer available; uBlock Origin Lite has significant limitations (rule limits, no cosmetic filtering, limited dynamic filtering).	Full uBlock Origin continues to work effectively due to continued `webRequest` blocking support.	Developers believe a majority of content blocker concerns resolved; aims to continue offering capabilities.	Brave Shields is unaffected; continues to support some MV2 ad blockers like uBlock Origin.	Ad-blocking capabilities are generally weaker compared to Chrome/Firefox with MV2 or Firefox with MV3.

🛠️ Technical Deep Dive

Background Script Model: Manifest V2 used persistent background pages that remained active, consuming resources. Manifest V3 replaces these with event-driven service workers, which are ephemeral and wake up only when needed, then shut down when idle. This requires developers to manage state using chrome.storage instead of in-memory variables.
Network Request Modification: The webRequest API in Manifest V2 allowed extensions to intercept, block, redirect, or modify network requests in real-time. Manifest V3 deprecates the blocking capabilities of webRequest and introduces the declarativeNetRequest API. This new API requires extensions to register a static set of rules with the browser, which then handles the blocking or modification declaratively, without the extension directly inspecting each request.
Rule Limitations in declarativeNetRequest: The declarativeNetRequest API imposes limits on the number of filtering rules an extension can use. While Google has increased these limits over time (e.g., from an initial 30,000 to 330,000 for static rules, and up to 100 rulesets with 50 enabled simultaneously), these are still finite and can restrict comprehensive ad-blocking lists. It also lacks full regular expression support and dynamic rule prioritization needed by advanced blockers.
Remotely Hosted Code: Manifest V3 prohibits extensions from executing remotely hosted code. All JavaScript must be included within the extension's package, which is then reviewed by the Chrome Web Store. This aims to improve security by preventing unreviewed code from being run but removes the ability for developers to quickly hotfix or update logic without a full extension update.
Promise Support: Manifest V3 APIs generally support Promises, making asynchronous code cleaner, though callbacks are still supported for backward compatibility.
Content Security Policy (CSP): Manifest V3 enforces a stricter Content Security Policy, disallowing 'unsafe-eval' and remote scripts, further requiring all scripts to be bundled within the extension.

🔮 Future ImplicationsAI analysis grounded in cited sources

User choice in content blocking will be significantly reduced within the Chrome ecosystem.

The limitations of Manifest V3's declarativeNetRequest API prevent advanced ad blockers from offering the same level of dynamic and comprehensive filtering as their Manifest V2 predecessors, pushing users towards less effective solutions or alternative browsers.

Innovation in privacy and security extensions for Chrome may be stifled.

The architectural changes and API restrictions in Manifest V3, particularly the shift away from real-time webRequest modification, limit the tools available to developers for creating sophisticated privacy and security tools, potentially hindering their ability to adapt to evolving web threats.

There will be a continued divergence in extension capabilities and user experience across different browsers.

Browsers like Firefox and Brave have adopted Manifest V3 with different implementations or maintained support for Manifest V2 features (like blocking webRequest), allowing them to offer more powerful content blocking and privacy tools compared to Chrome.

⏳ Timeline

2018

Google announces Manifest V3 proposal.

2019-06

Chromium team details `declarativeNetRequest` API and plans to change rule limits.

2020-12

Manifest V3 becomes available for experimentation with Chrome 88 Beta.

2021-01

Chrome Web Store starts accepting Manifest V3 extensions.

2022-01

Chrome Web Store stops accepting new Manifest V2 extensions.

2024-10

Manifest V2 extensions begin to be disabled in stable Chrome (Chrome 127+).

2025-03

Manifest V2 extensions are disabled by default for all users, with a temporary option to re-enable.

2025-07

Manifest V2 is disabled everywhere, and the re-enable option is removed.

Google to Disable Manifest V2 Extensions in Chrome

⚡ 30-Second TL;DR

🧠 Deep Insight

🔑 Enhanced Key Takeaways

🛠️ Technical Deep Dive

🔮 Future ImplicationsAI analysis grounded in cited sources

⏳ Timeline

📎 Sources (34)

👉Related Updates