Recent months have seen additional mechanisms for the Scripting API, support for multiple static rulesets in the Declarative Net Request API, tab ID-based filtering, and session-scoped rules. The goal is to make extensions more secure, as well as performant, given how much browser and activity access they have traditionally possessed. In the lead-up to Chrome 88’s launch this January, Google incorporated community feedback into Manifest v3, including changes to benefit ad blockers. Refer to this page for more granular timeline information, which will be kept up to date as more exact dates and milestone details are available. Updates to existing ones can still be submitted.Ī year later, in January of 2023, Chrome will no longer support Manifest v2 extensions with updates no longer possible.Īs these dates draw closer, we will share more details around the Chrome version targeted for the change, as well as more information on how both extension developers and users may be affected.

On January 17, 2022, the Chrome Web Store will no longer accept new browser extensions built using the old approach. Google has a plan to phase out support for Chrome extensions built using the preceding specification. In launching, the company has been conscious of how big a shift the privacy-preserving aspects are, and today detailed the transition away from Manifest v2.

Manifest v3 became available earlier this year with Chrome 88.

For the past few years, Google has been working on a new specification for building Chrome extensions.

Google chrome extension developer