Google to Deprecate MV2 Extensions Starting August 31
💡Critical infrastructure update for developers building browser-based AI tools and agents.
⚡ 30-Second TL;DR
What Changed
MV2 extensions will be removed from Chrome Store starting August 31
Why It Matters
Developers building browser-based AI agents or tools must adapt to MV3 constraints, which limit background processing and request interception capabilities.
What To Do Next
Audit your browser-based AI extensions to ensure compatibility with Manifest v3 declarativeNetRequest rules before the August 31 deadline.
Key Points
- •MV2 extensions will be removed from Chrome Store starting August 31
- •Migration to MV3 is required for better security and performance
- •Ad-blocking tools like uBlock Origin face reduced interception efficiency
🧠 Deep Insight
AI-generated analysis for this event — not the original article.
🔑 Enhanced Key Takeaways
- •The transition to MV3 replaces the blocking webRequest API with the declarativeNetRequest API, which limits the number of rules extensions can apply simultaneously.
- •Google has implemented a phased rollout strategy, initially disabling MV2 extensions for a subset of users before the final August 31 cutoff.
- •Enterprise users on Chrome have been granted a temporary policy override allowing them to continue using MV2 extensions until mid-2025, though this is now expired as of the 2026 date.
- •The deprecation process faced significant backlash from the developer community, leading Google to make minor adjustments to the declarativeNetRequest API limits to accommodate complex ad-blockers.
- •Chrome's move to MV3 aligns with the broader WebExtensions API standard, which aims to increase cross-browser compatibility between Chrome, Firefox, and Safari.
📊 Competitor Analysis▸ Show
| Feature | Chrome (MV3) | Firefox (MV3/MV2) | Safari (WebExtensions) |
|---|---|---|---|
| Ad-blocking Capability | Limited by rule caps | Full support (MV2/MV3) | Limited by API constraints |
| Performance | High (Optimized) | Moderate | High |
| Security Model | Strict (Sandboxed) | Flexible | Strict |
🛠️ Technical Deep Dive
- declarativeNetRequest API: Shifts the responsibility of blocking network requests from the extension to the browser engine, reducing the overhead of context switching between JavaScript and the browser core.
- Rule Limits: MV3 imposes a static limit on the number of rules (e.g., 30,000 global rules) that an extension can define, forcing developers to use dynamic rule sets for larger filter lists.
- Background Service Workers: Replaces persistent background pages with ephemeral service workers, which terminate when idle to save system memory and CPU cycles.
- Content Script Isolation: Maintains the existing isolation model but enforces stricter manifest-based declarations for script injection to prevent unauthorized code execution.
🔮 Future ImplicationsAI analysis grounded in cited sources
⏳ Timeline
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: cnBeta (Full RSS) ↗
This is a summary, not the original. Read the source, or get the weekly briefing.
The weekly digest
One email a week. Unsubscribe anytime.