Manifest V3 Explained: What Changed for Your Extensions

What is Manifest V3, in plain terms?

Manifest V3 (MV3) is the current version of Chrome's extension platform, the rulebook that defines what an extension is allowed to do and how. It replaced Manifest V2 (MV2), the previous rulebook that most Chrome extensions were built on for years.

The three biggest changes are: background code now runs in a service worker instead of a permanently open background page, extensions can no longer execute code fetched from a remote server, and network-request blocking moved from an open-ended API to a more restricted, declarative one. Each of those changes traded some extension capability for better performance, security or privacy.

What actually changed between Manifest V2 and Manifest V3?

The differences sound abstract until you line them up side by side. Here's what changed structurally, and why Chrome made each change.

Google frames the remote-code change specifically as a security fix: unreviewed code fetched at runtime was a way for a compromised or malicious update to slip past the Chrome Web Store's review process, so Manifest V3 closes that path entirely.

Why did ad blockers get worse under Manifest V3?

The old blocking webRequest API let an ad blocker's own code inspect every network request as it happened and decide, on the fly, whether to block it. That flexibility came at a cost: Chrome notes it required extensions to proxy all network traffic, which hurt both performance and privacy for every user, not just people running ad blockers.

declarativeNetRequest replaces that with a rule-based approach: an extension registers a set of blocking rules up front, and Chrome applies them without handing the extension's code a look at your live traffic. That's safer and lighter, but it constrains how dynamic or exhaustive a filter list can be compared to code that could evaluate every request individually.

How did different types of extensions fare under Manifest V3?

Not every extension category felt Manifest V3 the same way. Content blockers took the biggest visible hit, while tools that don't rely on inspecting network traffic mostly carried on unaffected once they updated their manifest file.

How do you check whether an extension uses Manifest V2 or V3?

You don't need developer tools to check this; Chrome shows an extension's manifest version right in its own settings page.

1. Open chrome://extensions in a new tab.
2. Find the extension you want to check.
3. Click Details on that extension's card.
4. Scroll to find the Manifest version field.
5. Compare it against the version shown for other extensions you use, to spot which ones haven't updated.

If a listing shows Manifest V2, treat it as a signal to check for an update or an alternative, since Chrome has been steadily reducing support for Manifest V2 extensions across recent versions.

What did Manifest V3 actually fix, beyond the ad blocker debate?

The ad blocker story gets the attention, but Manifest V3 also addressed problems that affected every Chrome user's battery life, memory usage and security, whether or not they ran a content blocker.

• Lower idle resource use: a Manifest V2 background page stayed open and consumed memory even when an extension had nothing to do; a Manifest V3 service worker shuts down when idle.
• No more remote code execution: every line of JavaScript an extension runs now ships inside the reviewed package, closing off a path malicious or compromised updates used to exploit.
• Safer network handling by default: declarativeNetRequest avoids routing all of your traffic through an extension's own inspection code just to apply a handful of blocking rules.
• Modern API design: promise-based methods sit alongside the older callback style, making extensions easier to write correctly and debug.

Is Manifest V2 still supported in Chrome today?

Google has been phasing out Manifest V2 support in stages rather than switching it off everywhere at once, and the exact status can shift between Chrome releases. Rather than rely on a fixed cutoff date here, check chrome://extensions directly: Chrome flags Manifest V2 extensions there when it plans to disable or remove them on your device.

What should you do if an extension you rely on hasn't migrated to Manifest V3?

An extension stuck on Manifest V2 isn't necessarily broken today, but it's a maintenance and security warning sign, since it means the developer either hasn't updated it or has stopped maintaining it altogether.

Check the extension's Chrome Web Store listing for a recent update date and look for the developer's own migration notes; a well-maintained extension usually announces a Manifest V3 rebuild rather than going silent. If it has gone silent, look for an actively updated alternative in the same category, for example ublock-origin-lite in place of an unmaintained Manifest V2 blocker, or privacy-badger if you specifically need automatic tracker detection.