PSA: Manifest V2 deprecation rollout update

[Sebastian Benz]

Hey everyone,

In October, we shared that we were starting to disable Manifest V2 extensions in Chrome stable. The rollout is now reaching 100%. This means, Chrome Extensions using Manifest V2 will be disabled for all users in Chrome. To give users time to find alternatives for these extensions, users have the ability to re-enable Manifest V2 extensions and continue using them for a limited time.

The possibility to re-enable Manifest V2 extensions is only temporary though. In the final phase of the Manifest V2 deprecation, we will remove the ability to re-enable Manifest V2 extensions. We will start rolling out this final change in Chrome pre-stable soon. We expect this rollout to take a few weeks, before we start rolling out this change in Chrome stable.

Enterprises using the ExtensionManifestV2Availability policy will not be affected by this.

Sebastian, on behalf of the Chrome Extensions Team.

[Thomas Beverley]

Thanks Sebastian. Is the timeframe for the enterprise ExtensionManifestV2Availability policy deprecation still June 2025?

[Sebastian Benz]

That's correct. We target M139 for starting the enterprise deprecation in pre-stable. 

[Sebastian Benz]

Hey Grant,

MV2 extensions are currently still supported in development mode. The reason for this is that people working on MV2 extensions for Enterprise still need to be able to make updates to their extensions as MV2 for enterprise has a longer deprecation timeline. 

Also, one general note, the deprecation is rolled out gradually and is not directly tied to Chrome releases (for example the MV2 deprecation hasn't fully rolled out to 100% stable yet). 

Hope that makes it more clear,

Sebastian

On Wed, Jun 25, 2025 at 8:09 PM Grant Thompson <gwthom...@gmail.com> wrote:

Hi Sebastian,

According to your post, as well as https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline, I would expect that I could not use a Manifest V2 extension at all in Chrome 139 and beyond.

However, in my Chrome Canary, version 140.0.7259.0, I am still able to use my Chrome extension with Manifest V2 by loading in the unpacked files in Developer Mode.

Is this expected? Will this deprecation not apply to extensions that are loaded through Developer Mode?

Thank you,

Grant

Dr. Sebastian Benz

Developer Relations Engineer

Google Germany GmbH

Erika-Mann-Straße 33

80636 München

Geschäftsführer: Paul Manicle, Liana Sebastian

Registergericht und -nummer: Hamburg, HRB 86891

Sitz der Gesellschaft: Hamburg

Diese E-Mail ist vertraulich. Falls Sie diese fälschlicherweise erhalten haben sollten, leiten Sie diese bitte nicht an jemand anderes weiter, löschen Sie alle Kopien und Anhänge davon und lassen Sie mich bitte wissen, dass die E-Mail an die falsche Person gesendet wurde. 

     

This e-mail is confidential. If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it has gone to the wrong person.

[Grant Thompson]

Hi Sebastian,

According to your post, as well as https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline, I would expect that I could not use a Manifest V2 extension at all in Chrome 139 and beyond.

However, in my Chrome Canary, version 140.0.7259.0, I am still able to use my Chrome extension with Manifest V2 by loading in the unpacked files in Developer Mode.

Is this expected? Will this deprecation not apply to extensions that are loaded through Developer Mode?

Thank you,

Grant

On Wednesday, March 5, 2025 at 8:15:00 AM UTC-8 Sebastian Benz wrote: