en-US chrome computer user

List of URL patterns for which Chrome DevTools are allowed to be opened

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

Google Chrome

Path in the GPO console

Computer Configuration\Administrative Templates\Google\Google Chrome

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~Miscellaneous/DeveloperToolsAvailabilityAllowlist

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

macOS / Linux preference DeveloperToolsAvailabilityAllowlist
Android restriction DeveloperToolsAvailabilityAllowlist
Supported platforms
  • Google Chrome (Linux) — since version 147
  • Google Chrome (Mac) — since version 147
  • Google Chrome (Windows) — since version 147
  • Google ChromeOS (Google ChromeOS) — since version 147
  • Google Chrome (Android) — since version 154

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

Options

List of URL patterns for which Chrome DevTools are allowed to be opened
List (registry values) list list under Software\Policies\Google\Chrome\DeveloperToolsAvailabilityAllowlist

Description

This policy can be used to allow Chrome DevTools on specific URLs. Chrome DevTools availability is evaluated at the target level. URL patterns are matched against the URL of each target being inspected (such as the main frame of a page, an embedded subframe, an extension, or a web application). The resulting behavior depends on whether the DeveloperToolsAvailabilityBlocklist policy is also set. If this policy is set and DeveloperToolsAvailabilityBlocklist is not, a target's URL must match a pattern on this allowlist for Chrome DevTools to be allowed for that target. If a target's URL does not match this allowlist, Chrome DevTools will be blocked for that target (for example, a subframe whose URL is not on the allowlist cannot be inspected, but the main page remains inspectable if its URL is allowlisted). For information on the URL format, see https://support.google.com/chrome/a?p=url_blocklist_filter_format. If both this and the DeveloperToolsAvailabilityBlocklist policies are set, this allowlist takes precedence. If a target's URL matches a pattern on this allowlist, it will be allowed, even if it also matches a pattern in the blocklist. If a target's URL matches a pattern on this blocklist (but not the allowlist), it will be blocked. If a target's URL matches neither, the DeveloperToolsAvailability policy will be used as a fallback. If this policy is not set, the availability of Chrome DevTools is determined by the DeveloperToolsAvailabilityBlocklist and DeveloperToolsAvailability policies. Blanket host wildcards (i.e., "*" or "[*]") are not allowed; use the DeveloperToolsAvailability policy to enable the feature globally. This policy affects Chrome DevTools, direct Chrome DevTools Protocol (CDP) access (for instance, when launched with --remote-debugging-port or --remote-debugging-pipe), and Chrome DevTools Protocol (CDP) access via chrome.debugger APIs. Both this policy and the RemoteDebuggingAllowed policy apply: RemoteDebuggingAllowed controls whether remote debugging can start, while this policy restricts whether individual targets can be inspected even when remote debugging is running. This policy is limited to 1,000 entries. Example value: example.com https://ssl.server.com hosting.com/bad_path https://server:8080/path .exact.hostname.com file://*

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: List of URL patterns for which Chrome DevTools are allowed to be opened
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Windows 7 or later

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

PowerShell

# Exported from gporais.com
# Policy: List of URL patterns for which Chrome DevTools are allowed to be opened
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later

$path = 'HKLM:\Software\Policies\Google\Chrome\DeveloperToolsAvailabilityAllowlist'
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