Manifest V3 migration checklist
Keep track of your migration progress
Published on
The checklists below are here to help you keep track of your migration work. They define tasks that must be completed with links to instructions. Migration work is broadly divided into five categories as described in the Migration summary.
Update the manifest
Update the manifest
The manifest.json file requires a slightly different format for Manoifest V3 than for Manifest V2. This page describes changes that only affect the manifest.json file. But many of the changes to scripts and pages also require changes to the manifest. Those changes are covered with the migration tasks that require them.
Migrate to a service worker
Migrate to a service worker
A service worker replaces the extension's background or event page to ensure that background code stays off the main thread. This enables extensions to run only when needed, saving resources.
Before beginning, read about the differences between background scripts and extension service workers.
Update API calls
Update API calls
Some features need to be replaced with Manifest V3 equivalents. Others need to be removed entirely.
Replace blocking web request listeners
Replace blocking web request listeners
Instead of programmatically reading network requests and altering them (as you did in Manifest V2), your extension specifies rules that describe actions to perform when a given set of conditions is met.
After completing the items above, you may want to review a few common use cases:
Improve extension security
Improve extension security
Changes are required to improve the security of extensions. This includes removing remotely hosted code, which is no longer supported.
Updated on • Improve article