The Future of Browser Extensions: Manifest V3 and Beyond

The transition to Manifest V3 has fundamentally changed browser extension development. Here is where things stand in 2026.

What Manifest V3 Changed

The biggest change was replacing persistent background pages with service workers. Extensions can no longer maintain long-running background processes. The webRequest API was replaced with declarativeNetRequest, which uses predefined rules instead of programmatic interception. This limits what ad blockers and privacy tools can do dynamically.

Impact on Ad Blockers

Ad blockers were the most affected category. The rule limit in declarativeNetRequest initially capped filter lists at 30,000 static rules. This has been increased, but complex ad blockers still needed architectural changes. uBlock Origin required a Lite version with reduced capabilities for Manifest V3.

Developer Migration

Most major extensions have completed migration. The main challenges were adapting to service worker lifecycles (they can be terminated at any time), replacing blocking webRequest calls with declarative rules, and handling the loss of persistent state.

Cross-Browser Compatibility

Firefox supports both Manifest V2 and V3, giving developers and users more choice. Safari aligned with V3 but has its own quirks. The divergence means extension developers must test across browsers more carefully than before.

New Capabilities

Manifest V3 also brought improvements: the Side Panel API enables persistent UI alongside web pages, the Offscreen API allows DOM access for background processing, and improved security with tighter permission scoping reduces the attack surface.

The Ecosystem in 2026

The Chrome Web Store has grown to over 200,000 extensions. AI-powered extensions are the fastest-growing category, adding capabilities like page summarization, translation, and code assistance. Browser extensions remain one of the most direct ways to enhance developer workflows without waiting for browser vendors to add features.