Manifest V3 explained for users: what changes for AI Chrome extensions in 2026

In March 2025 Chrome switched off, by default, thousands of extensions that had worked for years. In July of the same year it removed them from the browser entirely. If the AI extensions you use are still alive today, it is because they are built on Manifest V3 — Chrome’s new technical standard. This guide explains what changed, why your old ad blocker may have stopped working, what it means for your privacy as a user, and why the eight extensions in the AutoKuak suite were native MV3 from day one.

What Manifest V3 is, without developer jargon

A Chrome extension is basically a program that lives inside the browser and can read or change what happens on the pages you visit. To do that, every extension declares in a file (the “manifest”) which permissions it asks for, which domains it touches and how it works internally. That file is the boundary between what it can and cannot do.

Manifest V2 was the standing format since 2012. V3 is the major update Google started rolling out in 2020 and completed in 2025. It is not a cosmetic improvement — it changes the underlying security model.

The migration timeline (what already happened)

• 2018: Google announces the redesign that will become MV3.
• 2020-2021: Chrome starts accepting new MV3 extensions.
• June 2022: Chrome stops accepting new MV2 extensions in the Web Store.
• June 2023: the phase-out begins — Google warns that MV2’s clock has started.
• March 2025: MV2 disabled by default in every Chrome. A temporary toggle can turn it back on.
• July 2025 (Chrome 138): MV2 fully disabled. The toggle disappears.
• Chrome 139+ (August 2025): MV2 support is removed from the source code.
• 2026: 85 %+ of active extensions are already on MV3.

MV2 extensions that did not migrate simply vanished. Some had tens of millions of users. The quiet blackout of March 2025 was one of the biggest browser events in years, and mainstream press barely covered it.

The three technical changes that matter to you

1. Service workers instead of background pages

Under MV2, an extension could keep a “background page” always running: a process sitting in the background using RAM and CPU around the clock, whether or not anything was happening. Convenient for the developer, expensive for your machine: 20 MV2 extensions could hold 500-800 MB of RAM permanently.

MV3 replaces that with service workers: the process only starts when it is needed (an event, a click, a network request) and goes to sleep on its own when it is done. What you get: less RAM used and less battery burnt in the background. The difference is noticeable on laptops and phones.

2. declarativeNetRequest instead of blocking webRequest

An extension used to be able to intercept every network request your browser made (every image, every stylesheet, every script, every API call) and decide what to do with it. Useful for ad blockers inspecting each request. Also useful for malicious extensions that wanted to read all your traffic.

MV3 replaces that model with declarativeNetRequest: the extension declares a set of rules up front (block X, redirect Y, modify Z) and Chrome applies them internally, without passing the content through the extension. Faster, safer, less invasive. Also less powerful for advanced ad blocking.

This is why many traditional ad blockers — uBlock Origin above all — struggled with MV3. The technique they relied on, inspecting every request in real time and deciding with complex scripting, is no longer possible. “Lite” versions exist, with less capability.

3. The ban on remote code

Under MV2, an extension could download and run additional JavaScript from the internet after installation. That means the extension Google reviewed at install time could change its behaviour the next day with no new review. A massive abuse vector: apparently harmless extensions that later turned into spyware or adware.

MV3 bans this outright. All executable code has to be in the installed package and to have passed Google’s review. If the extension wants to change behaviour, it publishes a new version and goes through review again. It is one of the most important changes for your security as a user.

What it actually means for you

1. More security by design

The net security change is clearly positive. Spyware and adware extensions that mutated after installation — a common pattern — are no longer technically possible. A malicious MV3 extension is still possible, but Google sees all of its code on every release, which greatly raises the chance of catching it in review.

2. Fewer resources used

Modern extensions (Grok AutoKuak, Flow AutoKuak, ChatGPT AutoKuak, TubeKRadar) use service workers that sleep nearly all the time. While you are not actively using them, their RAM footprint is close to zero. Noticeable if you have 10+ extensions installed.

3. Traditional ad blockers downgraded

Classic uBlock Origin no longer works. uBlock Origin Lite exists but blocks less. Alternative browsers (Brave, Firefox for the more extreme cases) or behaviour changes (paying for YouTube Premium to avoid ads without a blocker) are the routes many users have taken.

4. More predictable extensions

With no remote code, an extension does exactly what its installed version does. If you want to know what it can reach, reading the permissions on its Web Store page gives you the real picture, not a partial one. For the AutoKuak suite that transparency is actively maintained: the eight extensions declare only the hosts they need (Grok only grok.com, x.com and x.ai; Flow only labs.google; ChatGPT only chatgpt.com; TubeKRadar only youtube.com).

Why the AutoKuak suite was unaffected

The eight extensions in the suite — Grok, Flow, ChatGPT, Higgsfield and Seedance AutoKuak, TubeKRadar, Inspector and Recorder — are native MV3. They were born in 2025 on the new standard from the first commit. That means no painful migration, no downtime, and no lost features because something from the old model could not be reproduced.

What that means for you in practice:

• Background batches keep working. Even when the service worker sleeps, scheduled timers (the MV3 alarms API) wake it. Long runs in Grok, Flow and ChatGPT AutoKuak keep moving.
• RAM use at rest is tiny. An extension running the afternoon’s batch only uses RAM while it processes. Then it sleeps.
• No remote code means full transparency. What you see in the published version is exactly what runs. No silent updates.
• Minimum permissions. Only the hosts that are strictly needed. If you only use Grok AutoKuak, the others have no access to your Grok data.

---

How to check whether an extension you use is MV3

1. Open chrome://extensions in Chrome.
2. Turn on “Developer mode” (top right).
3. Every extension now shows an ID and an “Inspect views” link. Click “Details”.
4. If you see “Manifest Version: 3” or a field mentioning “service worker”, it is MV3. If it mentions “background page”, it is still MV2 (rare in 2026 — it should be impossible on a recent Chrome).

The quick alternative: if the extension still works on Chrome 138+ (July 2025 or later), it has to be MV3.

Common myths about Manifest V3

• “MV3 kills ad blocking completely.” False. It limits it, it does not end it. uBlock Origin Lite, AdGuard MV3 and others still block most ads — they just cannot do exotic techniques that 95 % of users never needed.
• “MV3 is only so Google can sell more ads.” There is a real conflict of interest (Google owns Chrome and AdSense), but the technical gains in security and resource use are real too. It is both things at once.
• “MV3 extensions are less capable.” For most cases they are more capable (better performance, more predictable). For extreme ad blocking or deep network manipulation, yes, they lose ground.
• “Migrating to MV3 is just a file change.” False. For many extensions it meant rewriting large parts of the code. Some never migrated because it was not economically viable.

What to do if your favourite extension died

• Look for an MV3 alternative: there almost always is one. Best Chrome extensions for YouTube creators in 2026 and best AI Chrome extensions list the modern options.
• Consider another browser: Firefox and Brave still accept WebExtensions with more capability. Switching your main browser is rarely practical, but as a second browser for specific jobs it can be worth it.
• If it was very specific with no alternative: the use case is probably now covered by a web app or an external service. Searching “[feature] without a Chrome extension” usually turns something up.
• If it worked until recently and suddenly does not: see what to do when a Chrome extension stops working. Sometimes it is not MV3, it is something else.

---

Frequently asked questions

Do Edge, Brave, Opera and Vivaldi require MV3 too?

Yes — every Chromium-based browser follows the same rules: Edge, Brave, Opera, Vivaldi, Arc, ChromeOS. Firefox has its own WebExtensions with somewhat different policies (more flexible for ad blockers, for instance).

Did my extension data get lost in the migration?

It depends. If the extension migrated by publishing a new MV3 version, your local data is usually preserved (same extension ID, same storage). If the extension simply died and you replaced it with a different one, the data does not carry over — they are different apps.

Does Manifest V3 protect against malicious extensions 100 %?

No. It sharply reduces abuse vectors (remote code above all), but an MV3 extension can still be malicious if it passes Google’s review with apparently legitimate code. The basics still hold: install only what you need, read the permissions before installing, check the reviews.

Why did the migration take nearly five years (2020-2025)?

Migrating an ecosystem with tens of millions of installs is hard. Some extensions needed deep redesigns. Google extended the deadline several times. The original date was 2022; it slipped twice before the final switch in March 2025.

Is there any way to keep using an outdated MV2 extension?

Technically yes — Chrome for Enterprise kept the MV2 toggle a while longer, and “load unpacked” in developer mode lets you side-load MV2 extensions by hand. It is not recommended: they get no updates, they are a security vector, and Chrome eventually removes support entirely.

Will the AutoKuak suite stay compatible with future Chrome changes?

By design, yes. The eight extensions follow the official MV3 pattern with no proprietary extras and no deprecated APIs. When Chrome ships minor changes, those are trivial adjustments — not another mass migration. The next big break would be a hypothetical MV4, which has not been announced as of 2026.

---

In short: what you gain and what you lose

As a user, the net balance of Manifest V3 is positive if you value security and performance, and negative if you lean heavily on advanced ad blocking. For creators who depend on AI extensions (Grok, Flow, ChatGPT) and YouTube analysis tools, the change is practically invisible when the extensions are native MV3 — which is exactly the case here. To go deeper on the suite: how to automate Grok, how to batch-generate in Google Flow with Veo, how to bulk-prompt ChatGPT. And if an extension fails you, what to do when a Chrome extension stops working on YouTube covers the diagnosis.