What is Manifest V3?

The Manifest in a Chrome extension is a JSON configuration file (manifest.json) that declares the extension's metadata, permissions, and capabilities. Google versioned this format, and Manifest V3 represents the most significant overhaul of the extension platform since Chrome launched. The transition was controversial because MV3 imposes restrictions that affect how extensions can intercept and modify network requests — the core capability used by ad blockers, privacy tools, and many productivity extensions.

Key Changes from Manifest V2 to V3

The most impactful change is the replacement of the background page with a Service Worker. Background pages in MV2 were persistent — they could run indefinitely and maintain state. MV3 service workers are ephemeral: they start when needed and stop when idle, forcing extensions to persist state externally (in chrome.storage) rather than in memory. Another major change replaced the webRequestBlocking API — which allowed extensions to intercept and modify network requests on the fly — with a declarative API called declarativeNetRequest (DNR), which requires extensions to pre-declare rules rather than running dynamic JavaScript on every request.

Why Google Made These Changes

Google's stated motivations were security and performance. Persistent background pages consumed memory and battery. The webRequestBlocking API gave extensions the ability to silently inspect and modify all network traffic, creating privacy risks if an extension was malicious or compromised. By moving to declarative rules, Google argued that extensions become more auditable — reviewers can read the rules directly rather than inferring behavior from JavaScript. Critics countered that the DNR ruleset limit (originally 5,000 static rules, later raised to 30,000) would hamper sophisticated ad blockers that maintain hundreds of thousands of filter rules.

Impact on Ad Blockers and Privacy Extensions

The transition sparked significant debate. uBlock Origin's developer argued that MV3's limitations would fundamentally weaken ad-blocking capabilities. Google ultimately raised the rule limit and made some concessions, but the transition still required major rewrites. uBlock Origin Lite (a reduced MV3-compatible version) launched alongside the original. Most major extensions — including ad blockers, password managers, and developer tools — have completed MV3 migrations, though some capabilities remain limited compared to their MV2 versions.

What MV3 Means for Extension Developers

Developers building new extensions today must use MV3. Content scripts and the permission model are largely unchanged, but background logic must be refactored to handle the ephemeral service worker lifecycle. Extensions that previously stored state in background page variables must now use chrome.storage.session or chrome.storage.local. The host_permissions field is now separate from permissions, giving users and the Web Store clearer visibility into what sites an extension can access.