The format Chrome kept

Manifest V3 Migration: What Changed, the Manifest V2 Shutdown Date by Date, and What It Means for an Older Extension

Did a Chrome extension your team relies on stop updating this year, or disappear from the store at the end of August? If it was built years ago and nobody has touched it since, the cause has a name. Manifest V2 is finished in Chrome, and Manifest V3 is the only format left.

November 16, 2026 · 10 min read

acmetravelclub.com · manifest v3 migration plan
An old Manifest V2 extension, part by part
The background page is most of the work
Sample
Background page to service workerrewrite
Login token and cache moved to storagemove
Remote script bundled into the packagebundle
Blocking webRequest to declarativeNetRequestconvert
Unused permissions removeddrop two
manifest_version set to 3one line
Illustrative: a sample migration plan for a fictional travel club's extension

The short answer

Manifest V3 is the current Chrome extension platform; Chrome's manifest reference says the only supported manifest_version value is 3. It replaces background pages with service workers that run only when needed, removes remotely hosted code, and replaces blocking webRequest with declarativeNetRequest for many uses. Chrome removed all remaining Manifest V2 extensions from the Chrome Web Store on August 31, 2026.

On this page
  1. Three changes that rewrote how extensions are built
  2. The Manifest V2 phase-out, date by date, as Chrome records it
  3. Service workers, and the thirty seconds that catch old code
  4. Remote code: what the store forbids and what it still allows
  5. GatorCrawl Keywords, built for a background that sleeps
  6. Your older extension: migrate it, rebuild it or let it go
  7. How a migration runs at DataCram

Three changes that rewrote how extensions are built

Google describes Manifest V3, on its What is Manifest V3 page, as "the latest version of the extensions platform" and "the first step in our platform vision to improve the privacy, security, and performance of extensions." Strip away the vision statement and three changes do most of the work. A fourth, promise-based methods, made the code nicer to write without changing what an extension can do.

Manifest V2 against Manifest V3, in Google's words, and what each change means for your code
AreaManifest V2Manifest V3What it means in practice
Background code"a long-lived background page that took up resources, even when an extension wasn't running"Service workers, "which run only when needed"Anything kept in memory can vanish; state goes to storage
Remote codeCode could be fetched and run after install"an extension can only execute JavaScript that is included within its package and subject to review by the Chrome Web Store"Every line the extension runs ships in the package; data can still come from your server
Network requestsThe blocking version of webRequestBlocking webRequest deprecated; declarativeNetRequest "provides a safer alternative for many use cases"Extensions that block or modify requests declare rules instead of intercepting traffic
Manifest versionmanifest_version 2"The only supported value is 3."An old manifest is not accepted for a new upload

Sources: Google's What is Manifest V3 and its manifest reference, read in November 2026. The declarativeNetRequest change matters most to extensions that filter or rewrite traffic. For a typical business extension, a CRM capture button or a data panel on a web page, the background and remote code changes are the ones that bite.

The Manifest V2 phase-out, date by date, as Chrome records it

Google's Manifest V2 support timeline, marked "Last updated 2026-09-09 UTC", lists the shutdown in stages. Here it is in Google's words, without rounding.

  1. 1.January 2022: "Chrome Web Store stopped accepting new Manifest V2 extensions with visibility set to "Public" or "Unlisted"."
  2. 2.June 2022: "Chrome Web Store stopped accepting new Manifest V2 extensions with visibility set to "Private"."
  3. 3.June 3rd 2024: "the Manifest V2 phase-out begins." Warning banners started on the Chrome Beta, Dev and Canary channels, and Manifest V2 extensions with the Featured badge lost it.
  4. 4.October 9th 2024: "We will now begin disabling installed extensions still using Manifest V2 in Chrome stable. This change will be slowly rolled out over the following weeks."
  5. 5.March 31st 2025: "All users on all channels of Chrome now have Manifest V2 extensions disabled by default, but users continue to be able to turn their Manifest V2 extensions back on."
  6. 6.Jul 24th 2025: "Manifest V2 is disabled everywhere." With Chrome 138, users "can no longer turn them back on," and "Chrome 138 is the final version of Chrome to support Manifest V2 extensions (when paired with the ExtensionManifestV2Availability key)."
  7. 7.Aug 31st 2026: "All remaining Manifest V2 extensions removed from the Chrome Web Store." "Existing installs on Chrome 138 or earlier will continue to run, but they can no longer receive updates or be reinstalled if removed."

Service workers, and the thirty seconds that catch old code

Chrome calls the service worker "an extension's central event handler," one that "is loaded when it is needed, and unloaded when it goes dormant." Its lifecycle page lists when Chrome normally ends it: "After 30 seconds of inactivity" (an event or API call resets the timer), "When a single request, such as an event or API call, takes longer than 5 minutes to process," and "When a fetch() response takes more than 30 seconds to arrive."

Bright blue duotone of a stopwatch beside a puzzle piece, with solid circles and triangles floating around them on a plain background
Manifest V3's background code runs on a short clock, so anything worth keeping has to be saved, not held.

The same page gives the rule that breaks most hurried migrations: "Any global variables you set will be lost if the service worker shuts down. Instead of using global variables, save values to storage." A Manifest V2 background page could hold a login token or a cache in a variable all day. Move that code across unchanged and it works in testing, where you click constantly, then fails for a real user who steps away for a minute.

Chrome's storage reference offers the replacements. storage.session "holds data in memory while an extension is loaded," with a 10 MB limit as of November 2026, and Google advises: "If you're working with sensitive user data, instead use storage.session." storage.local holds 10 MB by default. Service workers also lack the DOM; Chrome notes they "don't have access to the DOM, but you can combine it with an offscreen document for this use case."

Remote code: what the store forbids and what it still allows

Chrome's getting started page is blunt: "all logic must be included in the extension package. This means no additional JavaScript code may be downloaded at runtime." Its remote code page defines the term: anything "executed by the browser that is loaded from someplace other than the extension's own files. Things like JavaScript and WASM. It does not include data or things like JSON or CSS."

That distinction saves most business extensions. Calling your own server for data is fine. Google's Manifest V3 requirements policy lists allowed remote calls including "Syncing user account data with a remote server" and "Performing server-side operations with data (such as for the purposes of encryption with a private key)." It also requires that "the full functionality of an extension must be easily discernible from its submitted code." Your server can do the thinking. The extension has to show, in its own code, what it does with the answer.

Get this wrong and the rejection has a name. Google's troubleshooting page calls the remotely hosted code violation "Blue Argon" and lists, among common reasons, "Including a <script> tag that points to a resource that is not within the extension's package." The Chrome Web Store review page covers the other color-and-element codes and how to avoid a resubmission loop.

Your server can do the thinking. The extension has to show, in its own code, what it does with the answer.

GatorCrawl Keywords, built for a background that sleeps

DataCram built GatorCrawl Keywords, a keyword research web app, and its Chrome extension, which shows keyword volume, CPC, difficulty and a 12-month trend on Google's results pages. Its manifest declares "manifest_version": 3. The Chrome Web Store has not accepted new Manifest V2 extensions since 2022, so it could only ever ship as Manifest V3, which makes it a clean picture of how the new rules shape a build.

Service worker that forgets safely

background.js holds the user's extension token and keeps lookup results for an hour in chrome.storage.session, so a reload, or a service worker restart, does not spend credits again.

One call per results page

The content script gathers the query, related searches and People also ask, and the service worker sends them to the web app's API as one batch.

Data in, no code in

The API returns keyword numbers, which are data under Google's definition. Every line of JavaScript the extension runs ships in its package.

A short permission list

Two permissions, storage and contextMenus, one host permission for the GatorCrawl app, and a content script matched to one address pattern: Google's search results.

The content script also renders "inside a shadow root so Google's styles and ours never mix," in the words of its source comments, and the options page connects the account and shows the credits left. None of that is special to Manifest V3. What is special is how little the build had to fight the format, because nothing important was ever kept in memory. The full tour is in how we built the GatorCrawl extension.

Your older extension: migrate it, rebuild it or let it go

If you still depend on a Manifest V2 extension in Chrome, the timeline above settles the facts. It is gone from the store, it cannot be updated, and Chrome 139 and later do not run it. What remains is a decision, and three answers are honest ones.

Migrate when

  • The code is readable and someone still understands it
  • State lives in a few clear places that can move to storage
  • It does not depend on blocking webRequest, or declarativeNetRequest covers what it does
  • It loads no code from outside its package, or that code can be bundled

Rebuild when

  • Nobody has the source, only the installed copy
  • The background page holds everything in memory and was never designed to stop
  • The extension fetches and runs scripts from a server
  • It asks for far more access than its job needs, and a fresh permission plan is cheaper than defending the old one

The third answer is to retire it. If the job it did now lives in your web app, or a built-in browser feature does it, removing the extension costs nothing and reduces risk, for reasons the browser extension security page sets out. Our extension maintenance page covers keeping a migrated extension healthy afterward.

Other browsers run on different clocks. Mozilla said in March 2024 that Firefox has "no plans to deprecate MV2," which our Firefox extensions page covers. Microsoft's Edge timeline shows Manifest V2 warnings to some users from mid-September 2026 and enterprise deprecation "expected to begin" in early 2027, with the date for refusing updates still "TBD". A cross-browser Manifest V3 build covers all of them from one codebase.

How a migration runs at DataCram

  1. 1

    Read what you have

    The manifest, the background page, the permission list and anything loaded from outside the package. If the source is missing, we say so before quoting.

  2. 2

    Re-plan the permissions

    Chrome's policy asks for "the narrowest permissions necessary." A migration is the cheapest moment to drop the ones nobody uses.

  3. 3

    Move the background to a service worker

    Every value that must survive goes to storage, and long-running work is split into events.

  4. 4

    Bundle or replace remote code

    Scripts fetched at runtime become part of the package, or the logic moves to your server and returns data.

  5. 5

    Test the sleeping cases

    Leave the browser idle, come back, and confirm the extension still knows who the user is.

  6. 6

    Submit under your account

    With the privacy disclosures and permission justifications rewritten for the new build.

Custom browser extensions from DataCram start at $1,500 to build, depending on complexity, and a migration is quoted the same way: a fixed written estimate after we read the code. Store submission, privacy disclosures and the permission plan are part of the work, and we promise no review time; how long an extension takes explains which stages you control. The rewritten disclosures follow our permissions and privacy guide. See custom Chrome extension development, the extension pricing page, and the rest of the custom browser extensions section. Connections to your own systems go live the same day through API integrations. DataCram is a web studio in San Antonio, Texas, building for the web since 1999; see our work or call (210) 346-0848.

Questions owners ask about custom browser extensions

In stages. Google's timeline says Chrome began disabling Manifest V2 extensions in stable on October 9th 2024, disabled them for everyone with no way to turn them back on on July 24th 2025 with Chrome 138, and removed all remaining Manifest V2 extensions from the Chrome Web Store on August 31st 2026.

Only on old browsers. Google says existing installs on Chrome 138 or earlier continue to run but cannot receive updates or be reinstalled if removed, and that Manifest V2 extensions cease to function for any user upgrading to Chrome 139 and later. In practice, it is time to migrate, rebuild or retire it.

Yes. Google's remote code rules cover executable code such as JavaScript and WASM, not data like JSON. Its policy lists syncing user account data with a remote server among allowed remote calls. What the extension cannot do is download and run new JavaScript after it is installed.

Usually because the token lived in a global variable. Chrome ends an idle extension service worker after 30 seconds of inactivity, and Google says global variables are lost when it shuts down. Save values to chrome.storage instead; Google recommends storage.session for sensitive data.

No. Mozilla said in March 2024 that Firefox has no plans to deprecate Manifest V2 and will support it for the foreseeable future. Firefox has supported Manifest V3 since Firefox 109, though it runs background scripts rather than service workers.

It depends on the code. We read the extension first, then give a fixed written estimate. New extensions from DataCram start at $1,500, depending on complexity, and a migration that turns into a rebuild is priced the same way.

Keep reading

Free · No obligation

Find out what your old extension needs

Send the extension or describe what it does. Someone at DataCram replies with whether it should be migrated, rebuilt or retired, and a fixed written estimate.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote