Open in the explorer

List of URL patterns for which Chrome DevTools are blocked

Type
Computer and user
GPO path
Computer Configuration › Policies › Administrative Templates › Google › Google Chrome User Configuration › Policies › Administrative Templates › Google › Google Chrome
Supported on
Microsoft Windows 7 or later
ADMX file
chrome.admx
Internal name
chrome/DeveloperToolsAvailabilityBlocklist

Explanation

This policy can be used to block Chrome DevTools on specific URLs. For information on the URL format, see https://support.google.com/chrome/a?p=url_blocklist_filter_format.

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 DeveloperToolsAvailabilityAllowlist policy is also set.

If this policy is set and DeveloperToolsAvailabilityAllowlist is not, a target's URL matching a pattern on this blocklist will block Chrome DevTools for that target (for example, a subframe whose URL matches this blocklist cannot be inspected, but the main page remains inspectable if its URL is not blocklisted). If a target's URL does not match any pattern, the availability is determined by the DeveloperToolsAvailability policy.

If both this and the DeveloperToolsAvailabilityAllowlist policies are set, the allowlist takes precedence. If a target's URL matches a pattern on the allowlist, it will be allowed, even if it also matches a pattern in this 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 DeveloperToolsAvailabilityAllowlist and DeveloperToolsAvailability policies.

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:

https://example.com
example.com
https://ssl.server.com
hosting.com/bad_path
https://server:8080/path
.exact.hostname.com
*
file://*

Registry

HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome
HKEY_CURRENT_USER\Software\Policies\Google\Chrome
Value name
not defined in the ADMX

Enable / disable values: not defined in the ADMX (see the options below).

PowerShell

PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.

Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.

Computer (HKLM)

Enable

# Enable: chrome/DeveloperToolsAvailabilityBlocklist
$k = 'HKLM:\Software\Policies\Google\Chrome\DeveloperToolsAvailabilityBlocklist'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# List of URL patterns for which Chrome DevTools are blocked
# Non-additive list: existing values of the key are cleared first
if (Test-Path -Path $k) { (Get-Item -Path $k).Property | ForEach-Object { Remove-ItemProperty -Path $k -Name ([WildcardPattern]::Escape($_)) -ErrorAction SilentlyContinue } }
$values = @('<value1>', '<value2>')  # Replace the values with your own
$i = 1
foreach ($v in $values) { Set-ItemProperty -Path $k -Name ('' + $i) -Value $v -Type String; $i++ }

Disable

# Disable: chrome/DeveloperToolsAvailabilityBlocklist
# No value is written in the "Disabled" state (nothing defined in the ADMX)

Revert to "Not configured"

# Revert to "Not configured": chrome/DeveloperToolsAvailabilityBlocklist
$k = 'HKLM:\Software\Policies\Google\Chrome\DeveloperToolsAvailabilityBlocklist'
Remove-Item -Path $k -Recurse -Force -ErrorAction SilentlyContinue

User (HKCU)

Enable

Disable

Revert to "Not configured"

Options (1)

LabelControlRegistry valueREG typeConstraints / details
List of URL patterns for which Chrome DevTools are blockedDeveloperToolsAvailabilityBlocklistDescList (table)listSoftware\Policies\Google\Chrome\DeveloperToolsAvailabilityBlocklistValues named “” + numberREG_SZ (values under the key)

Application

Google Chrome (Google) — November 2026 templates

Official templates downloaded on November 12, 2026.