Google has been working on a new standard for developing Chrome extensions for several years. With Chrome 88, Manifest v3 became accessible earlier this year. The firm was aware of how significant the privacy-preserving features are when it launched, and today revealed the transition away from Manifest v2.
Google intends to phase down support for Chrome extensions created in accordance with the previous standard. The Chrome Web Store will stop accepting new browser extensions developed using the previous method on January 17, 2022. It is still possible to contribute updates to existing ones.
Chrome will no longer support Manifest v2 extensions a year later, in January 2023, with updates no longer feasible.
As 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. 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.
Google integrated community feedback into Manifest v3, including modifications to benefit ad blockers, in the run-up to Chrome 88’s debut in January. Given how much browser and activity access extensions have traditionally had, the objective is to make them more safe as well as performant.
Additional methods for the Scripting API, support for multiple static rulesets in the Declarative Net Request API, tab ID-based filtering, and session-scoped rules have all been added in the last few months.
These changes were crafted with community feedback in mind, and we will continue to build more powerful extension API functionality as developers share more information about their migration challenges and business needs.
Chrome will allow dynamically changeable content scripts, in-memory storage choices, and other “new features” in the future.
If you have feedback on Manifest V3 or are encountering unique challenges with the migration process, please post to the chromium-extensions Google Group. The earlier issues are raised and the earlier feedback is given, the more options the team has to address them prior to MV2 phase-out.