SourceZDNet AI•Stalecollected in 41m
Chrome update to restrict adblocker functionality
#web-scraping#browser-privacy#manifest-v3google-chromegooglechrome
Major browser architecture shift affecting web automation and data collection pipelines.
30-Second TL;DR
What Changed
Chrome update restricts Manifest V2 adblockers
Why It Matters
This shift impacts web scraping, data collection, and privacy-focused AI tool development.
What To Do Next
Audit your web scraping infrastructure to ensure compatibility with Manifest V3 restrictions.
Who should care:Developers & AI Engineers
Key Points
- •Chrome update restricts Manifest V2 adblockers
- •Changes aimed at privacy and performance
- •Significant reduction in user-side browsing control
Deep Insight
AI-generated analysis for this event — not the original article.
Enhanced Key Takeaways
- •The transition involves the mandatory migration from Manifest V2 to Manifest V3, which replaces the blocking 'webRequest' API with the more restrictive 'declarativeNetRequest' API.
- •Under the new architecture, extensions are limited to a fixed number of static and dynamic filtering rules, forcing adblockers to manage complex lists within strict memory and rule-count constraints.
- •Google's 'Web Environment Integrity' proposal and related privacy initiatives have been criticized by the Electronic Frontier Foundation (EFF) for potentially undermining the open web ecosystem.
- •Enterprise users have been granted temporary extensions to continue using Manifest V2 policies, acknowledging that many corporate environments rely on legacy filtering capabilities.
- •The shift has accelerated the adoption of server-side ad blocking and DNS-based filtering solutions, as browser-based extensions lose their efficacy in granular content manipulation.
Competitor Analysis
Ad Blocking Method
- Chrome (Manifest V3)
- DeclarativeNetRequest API
- Firefox (Manifest V3+)
- Hybrid (V3 + WebRequest support)
- Brave (Native Shield)
- Native Rust-based engine
Rule Limits
- Chrome (Manifest V3)
- Strict (30k-300k rules)
- Firefox (Manifest V3+)
- Flexible
- Brave (Native Shield)
- Unlimited (Native)
Privacy Focus
- Chrome (Manifest V3)
- Google-defined (Privacy Sandbox)
- Firefox (Manifest V3+)
- User-defined
- Brave (Native Shield)
- Anti-fingerprinting focus
| Feature | Chrome (Manifest V3) | Firefox (Manifest V3+) | Brave (Native Shield) |
|---|---|---|---|
| Ad Blocking Method | DeclarativeNetRequest API | Hybrid (V3 + WebRequest support) | Native Rust-based engine |
| Rule Limits | Strict (30k-300k rules) | Flexible | Unlimited (Native) |
| Privacy Focus | Google-defined (Privacy Sandbox) | User-defined | Anti-fingerprinting focus |
Technical Deep Dive
- The declarativeNetRequest API requires extensions to provide a JSON-based rule set to the browser, which then evaluates and executes the filtering logic internally.
- This architecture prevents extensions from executing arbitrary JavaScript code for every network request, significantly reducing the performance overhead of content filtering.
- The rule limit constraint forces developers to implement complex 'rule-sharding' techniques, where extensions dynamically swap rule sets based on the current domain to stay under the browser-imposed caps.
- By removing the ability to intercept and modify requests in real-time via the blocking webRequest API, Chrome effectively eliminates the possibility of 'dynamic' ad-blocking that adapts to anti-adblock scripts in real-time.
Future ImplicationsAI analysis grounded in cited sources
Market share shift toward privacy-focused browsers
Users dissatisfied with restricted ad-blocking capabilities are increasingly migrating to browsers like Brave or Firefox that maintain support for more robust filtering APIs.
Increased reliance on server-side ad injection
As client-side ad-blocking becomes less effective, advertisers will likely shift toward server-side rendering to bypass browser-level filtering entirely.
Timeline
2019-01
Google announces the initial proposal for Manifest V3, sparking controversy over the future of ad-blocking.
2022-09
Google officially begins the deprecation process for Manifest V2, outlining the timeline for extension removal.
2024-06
Google begins disabling Manifest V2 extensions for the majority of Chrome users in the stable channel.
2025-06
Final sunsetting of Manifest V2 support for enterprise and managed browser environments.
- 2019-01Google announces the initial proposal for Manifest V3, sparking controversy over the future of ad-blocking.
- 2022-09Google officially begins the deprecation process for Manifest V2, outlining the timeline for extension removal.
- 2024-06Google begins disabling Manifest V2 extensions for the majority of Chrome users in the stable channel.
- 2025-06Final sunsetting of Manifest V2 support for enterprise and managed browser environments.
Weekly AI Recap
Read this week's curated digest of top AI events →
Related Updates
AI-curated news aggregator. All content rights belong to original publishers.
Original source: ZDNet AI ↗
This is a summary, not the original. Read the source, or get the weekly briefing.
The weekly digest
One email a week. Unsubscribe anytime.