en-US chrome computer user

Configure allowed app/extension types

Verified with Google Chrome — updated on July 10, 2026 Supported on: Microsoft Windows 7 or later

Google Chrome

Path in the GPO console

Computer Configuration\Administrative Templates\Google\Google Chrome\Extensions

Registry

HKLM Software\Policies\Google\Chrome
HKCU Software\Policies\Google\Chrome

Other deployment channels

Intune (ADMX ingestion)
./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Extensions/ExtensionAllowedTypes

OMA-URI published by Google. It requires the Chrome ADMX templates (chrome.admx, google.admx) to be imported in Intune first.

macOS / Linux preference ExtensionAllowedTypes
Android restriction ExtensionAllowedTypes
Supported platforms
  • Google Chrome (Linux) — since version 25
  • Google Chrome (Mac) — since version 25
  • Google Chrome (Windows) — since version 25
  • Google ChromeOS (Google ChromeOS) — since version 25
  • Google Chrome (Android) — since version 146

Source: official Chrome policy list, version 157.0.8103.79 Chrome Enterprise policy page

Options

Types of extensions/apps that are allowed to be installed
List (registry values) list list under Software\Policies\Google\Chrome\ExtensionAllowedTypes

Description

Setting the policy controls which apps and extensions may be installed in Google Chrome, which hosts they can interact with, and limits runtime access. Leaving the policy unset results in no restrictions on the acceptable extension and app types. Extensions and apps which have a type that's not on the list won't be installed. Each value should be one of these strings: * "extension" * "theme" * "user_script" * "hosted_app" * "legacy_packaged_app" * "platform_app" See the Google Chrome extensions documentation for more information on these types. Versions earlier than 75 that use multiple comma separated extension IDs aren't supported and are skipped. The rest of the policy applies. Note: This policy also affects extensions and apps to be force-installed using ExtensionInstallForcelist. Note: This policy only applies to platforms that support extensions. Example value: hosted_app

Export Builder

BETA

Configure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.

These exports write the registry — this is not a managed GPO. ⓘ

Scope

.reg file

Windows Registry Editor Version 5.00

; Exported from gporais.com
; Policy: Configure allowed app/extension types
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Windows 7 or later

[HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\ExtensionAllowedTypes]
; List values: enter one value per line in the builder UI.
More formats (PowerShell, Intune, SCCM)

PowerShell

# Exported from gporais.com
# Policy: Configure allowed app/extension types
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later

$path = 'HKLM:\Software\Policies\Google\Chrome\ExtensionAllowedTypes'
New-Item -Path $path -Force | Out-Null
# List values: enter one value per line in the builder UI.

Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.

Open the Builder

Embed this policy on your site

What to embed
Theme

Adds one script line: the theme follows your site’s appearance and the height fits the content. If your site blocks scripts, the embed follows the visitor’s system theme.

Preview