Skip to main content

ExtensionManifestV2Availability

Control Manifest v2 extension availability - ExtensionManifestV2Availability​

Control if Manifest v2 extensions can be used by browser.

Manifest v2 extensions support will be deprecated and all extensions need to be migrated to v3 in the future. More information and timeline of the migration can be found at https://developer.chrome.com/docs/extensions/mv3/mv2-sunset/.

If the policy is set to Default (0) or not set, v2 extensions loading are decided by browser, following the timeline above. If the policy is set to Disable (1), v2 extensions installation are blocked, existing ones are disabled. The option is going to be treated the same as if the policy is not set after v2 support is turned off by default. If the policy is set to Enable (2), v2 extensions are allowed. The option is going to be treated the same as if the policy is not set before v2 support is turned off by default. If the policy is set to EnableForForcedExtensions (3), force installed v2 extensions are allowed. This includes extensions that are listed by ExtensionInstallForcelist or ExtensionSettings with installation_mode "force_installed" or "normal_installed". All other v2 extensions are disabled. The option is always available regardless of the migration state.

Extensions availability are still controlled by other policies.

0 = Default browser behavior 1 = Manifest v2 is disabled 2 = Manifest v2 is enabled 3 = Manifest v2 is enabled for forced extensions only

Data Type:

Integer

Supported features:

  • Dynamic Policy Refresh: True
  • Per Profile: True

Example value

2