# Manifest V2 phase-out begins

DevFeed: [Manifest V2 phase-out begins](<https://devfeed.tech/articles/manifest-v2-phase-out-begins-4184.md>)

Original publisher: [Read original article](<https://blog.chromium.org/2024/05/manifest-v2-phase-out-begins.html>)

Author: Chromium Blog (noreply@blogger.com)

Published: 2024-05-30T16:45:00Z

Content type: article

Language: en

Sources: [Chromium Blog](<https://devfeed.tech/sources/chromium-blog.md>)

Topics: [Extension](<https://devfeed.tech/topics/extension.md>), [Chrome](<https://devfeed.tech/topics/chrome.md>), [migration](<https://devfeed.tech/topics/migration.md>), [Security](<https://devfeed.tech/topics/security.md>), [Security & Privacy](<https://devfeed.tech/topics/security-privacy.md>), [Document Object Model (DOM)](<https://devfeed.tech/topics/dom.md>), [uBlock Origin Filters](<https://devfeed.tech/topics/ublock-origin-filters.md>)

Tags: [chrome](<https://devfeed.tech/tags/chrome.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [community](<https://devfeed.tech/tags/community.md>), [extension](<https://devfeed.tech/tags/extension.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [feature](<https://devfeed.tech/tags/feature.md>), [manifest](<https://devfeed.tech/tags/manifest.md>), [migration](<https://devfeed.tech/tags/migration.md>), [none](<https://devfeed.tech/tags/none.md>), [performance](<https://devfeed.tech/tags/performance.md>), [security](<https://devfeed.tech/tags/security.md>), [security-privacy](<https://devfeed.tech/tags/security-privacy.md>), [update](<https://devfeed.tech/tags/update.md>)

## AI overview

Chrome has begun disabling extensions that still use Manifest V2. The article describes the transition to Manifest V3, which is intended to improve extension security, privacy, performance, and trustworthiness while preserving existing functionality. It highlights community-driven improvements, including user scripts, offscreen documents for DOM APIs, larger declarativeNetRequest rulesets, faster review of safe rule updates, and version rollback. More than 85% of actively maintained Chrome Web Store extensions were reported to use Manifest V3.

## Source excerpt

Update (10/10/2024): We've started disabling extensions still using Manifest V2 in Chrome stable. Read more details in the MV2 support timeline documentation. In November 2023, we shared a timeline for the phasing out of Manifest V2 extensions in Chrome. Based on the progress and feedback we've seen from the community, we're now ready to roll out these changes as scheduled. We've always been clear that the goal of Manifest V3 is to protect existing functionality while improving the security, privacy, performance and trustworthiness of the extension ecosystem as a whole. We appreciate the collaboration and feedback from the community that has allowed us - and continues to allow us - to constantly improve the extensions platform. Addressing community feedback We understand migrations of this magnitude can be challenging, which is why we've listened to developer feedback and spent years refining Manifest V3 to support the innovation happening across the extensions community. This included adding support for user scripts and introducing offscreen documents to allow extensions to use DOM APIs from a background context. Based on input from the extension community, we also increased the number of rulesets for declarativeNetRequest, allowing extensions to bundle up to 330,000 static rules and dynamically add a further 30,000. You can find more detail in our content filtering guide. This month, we made the transition even easier for extensions using declarativeNetRequest with the launch of review skipping for safe rule updates. If the only changes are for safe modifications to an extension's static rule list for declarativeNetRequest, Chrome will approve the update in minutes. Coupled with the launch of version roll back last month, developers now have greater control over how their updates are deployed. Ecosystem progress After we addressed the top issues and feature gaps blocking migration last year, we saw an acceleration of extensions migrating successfully to Manifest V