Manifest V3 Explained (2026): What Changed, What Broke, and What Still Works
A clear explainer on Manifest V3 for users and developers: the MV2 shutdown timeline in Chrome and Edge, why ad blockers changed, and how Firefox and Brave differ.
“Manifest V3” is the name of the current rulebook for browser extensions. If you’ve heard about it, it was probably because your favorite ad blocker stopped working in Chrome, or because an extension you relied on vanished. If you’re a developer, it was the migration you put off for as long as possible.
This guide explains what actually changed, where each browser stands as of November 2026, and what it means in practice. The developer sections focus on the walls migrations most often hit.
What a “manifest” is
Every extension has a file called manifest.json. It declares the extension’s name, version, icons, permissions, background code and the pages where it runs. The manifest_version field tells the browser which set of rules and APIs apply. Version 2 was the standard for most of the last decade. Version 3 replaces it in Chromium-based browsers (Chrome, Edge, Brave, Opera, Vivaldi), and Firefox supports it too, with some important differences.
The four changes that matter
1. Background pages became service workers
In MV2, an extension could keep a hidden background page running for as long as the browser was open. In MV3 (in Chrome), background logic runs in a service worker that Chrome starts when an event arrives and stops when it’s idle. Per Chrome’s documentation, a service worker is normally terminated after 30 seconds of inactivity, and each event or extension API call resets that timer.
For users, that means less memory used by extensions sitting idle. For developers, it means global variables vanish, so you have to save state in chrome.storage, register listeners at the top level of the script, and use chrome.alarms instead of setInterval for anything periodic.
2. No more remotely hosted code
An MV3 extension must ship all its executable code in the package that Google reviews. It can’t download a script from a server and eval() it. This closes a common trick where an extension passed review with harmless code and then fetched the harmful part later. It doesn’t make extensions perfectly safe, since 2026 still saw extensions abuse loopholes after changing owners, but it raised the bar. In the Chrome Web Store, violating this rule has its own rejection code (“Blue Argon”).
3. Blocking webRequest was replaced by declarativeNetRequest
This is the change that made headlines. In MV2, an extension could intercept every network request with the webRequest API, inspect it in its own code and decide whether to block or change it. That’s how the classic version of uBlock Origin works.
In Chrome’s MV3, the blocking form of webRequest is gone for normal extensions. Instead, extensions hand Chrome a list of rules through the declarativeNetRequest (DNR) API, for example “block requests to this domain” or “remove this header”. Chrome applies the rules itself without showing the extension each request. Google’s argument is privacy and performance: the extension never sees your traffic. Critics argue that rule-based filtering is less flexible and capped in size.
The caps, from the declarativeNetRequest reference as of November 2026:
| Limit | Value |
|---|---|
| Static rules guaranteed per extension | 30,000 (more can come from a shared global pool) |
| Static rulesets declared / enabled at once | 100 / 50 |
| Dynamic rules (“safe” rules) | 30,000 |
| “Unsafe” dynamic rules (e.g. redirects, header changes) | 5,000 |
| Regex rules | 1,000 |
These limits have grown since MV3 launched, and most mainstream content blockers now work within them. The trade-off is advanced, dynamic filtering. Things like uBlock Origin’s element-picker logic and some scriptlet techniques are harder or impossible to do the same way.
4. Stricter content security
MV3 extension pages run under a stricter Content Security Policy. Inline scripts and eval aren’t allowed in extension pages, and remote scripts can’t be loaded. If you’re building a popup with a framework, make sure your build outputs plain bundled files.
The shutdown timeline, browser by browser
Chrome
Chrome’s official MV2 timeline went in stages:
- June 2024: warning banners in pre-release channels.
- October 2024: MV2 extensions start being disabled in stable Chrome, with a temporary option to turn them back on.
- March 31, 2025: MV2 disabled by default on all channels.
- July 24, 2025 (Chrome 138): the re-enable option is gone for regular users.
- Chrome 139: the enterprise policy
ExtensionManifestV2Availabilityis removed, ending the exemption for managed machines. - 2026: Chrome 150 and 151 removed the remaining internal flags and code paths, which ended the command-line workarounds some power users relied on. On August 31, 2026, Google removed all remaining MV2 extensions from the Chrome Web Store. Old installs on outdated Chrome versions can no longer update or be reinstalled.
In short: in current Chrome, MV2 extensions do not run. Chrome has also moved to a two-week release cycle since September 2026 (announcement), so these Chrome version numbers fly by quickly.
Microsoft Edge
Edge followed later. On August 7, 2026, Microsoft announced that it would start retiring MV2 extensions for consumers that month, rolling through Canary, Dev, Beta and then Stable over the following months. It aims to finish the consumer transition by the end of 2026 and start on enterprise devices in early 2027. If you use Edge, expect MV2 extensions to stop working during this window.
Brave
Brave uses Chromium but has said it will keep supporting a small set of MV2 extensions, including uBlock Origin, by hosting them on its own servers. You enable them from a Manifest V2 section in Brave’s extension settings. Brave’s built-in Shields blocker doesn’t depend on extension APIs at all.
Firefox
Firefox supports both MV2 and MV3, and its MV3 implementation keeps blocking webRequest alongside declarativeNetRequest (Mozilla’s explanation). Firefox MV3 also supports event pages, a non-persistent background page, rather than requiring service workers. That’s why the full uBlock Origin still works on Firefox. In August 2026 Firefox’s official account said its support for uBlock Origin “is not going anywhere.”
Summary table (as of November 2026)
| Browser | Runs MV2 extensions? | MV3 blocking webRequest? | Full uBlock Origin? |
|---|---|---|---|
| Chrome | No | No | No (uBlock Origin Lite instead) |
| Edge | Being phased out for consumers through end of 2026 | No | Going away |
| Brave | Selected MV2 extensions, hosted by Brave | No | Yes, via Brave’s MV2 section |
| Firefox | Yes | Yes | Yes |
What this means if you just use extensions
- Your ad blocker: in Chrome, use an MV3 blocker. The uBlock Origin developer publishes uBlock Origin Lite, an MV3 version with fewer advanced features. Other major blockers have MV3 versions too. If advanced filtering matters a lot to you, Firefox is the browser with the fewest compromises.
- An extension disappeared: check whether it was MV2 and abandoned. Look in the Chrome Web Store for an MV3 alternative from a trustworthy publisher, and run our safety check before installing a replacement. Abandoned extensions are often bought and relaunched by people you shouldn’t trust.
- Performance: MV3 service workers mean idle extensions use less memory than old persistent background pages did. It’s a real benefit, if not a dramatic one.
What this means if you build extensions
If you’re starting today, MV3 is the only option for Chrome, and a single MV3 codebase can target Chrome, Edge, Brave and Firefox with small adjustments:
- Namespace: Chrome has supported the standard
browser.*namespace alongsidechrome.*since Chrome 148, per Chrome’s browser namespace docs. Firefox has always usedbrowser.*. This makes cross-browser code simpler than it used to be. Test DevTools extensions separately, since support forbrowser.*there arrived later. - Background: Firefox accepts
background.scripts, Chrome requiresbackground.service_worker. You can declare both, and each browser uses the one it supports. - Network filtering: design for
declarativeNetRequestfirst. Use Firefox’s blockingwebRequestonly as an enhancement. - State: assume your service worker can be killed at any moment. Save state in
chrome.storage.sessionorchrome.storage.local.
Our hands-on first extension tutorial walks through a working MV3 extension from an empty folder.
Is Manifest V3 good or bad?
Both, honestly. MV3 closed real security holes, especially remote code, and made idle extensions lighter. It also took power away from a category of privacy tools that users valued, and Firefox and Brave have deliberately chosen to keep some of that power. For most people the practical answer is simple: use reputable MV3 extensions in Chrome, and if your workflow depends on advanced content filtering, use a browser that still supports it.