Open in the explorer

Control where developer tools can be used

Type
Computer and user
GPO path
Computer Configuration › Policies › Administrative Templates › Microsoft Edge User Configuration › Policies › Administrative Templates › Microsoft Edge
Supported on
Microsoft Edge version 77, Windows 7 or later
ADMX file
msedge.admx
Internal name
msedge/DeveloperToolsAvailability

Explanation

Controls whether users can access developer tools in Microsoft Edge.

This policy also applies to direct Chrome DevTools Protocol (CDP) connections (for example, connections that use --remote-debugging-port or --remote-debugging-pipe) and CDP connections through the chrome.debugger extension API. The 'RemoteDebuggingAllowed' (Allow remote debugging) policy controls whether users can use remote debugging. When remote debugging is allowed, this policy still controls which targets can be inspected.

If you set this policy to 'DeveloperToolsDisallowedForForceInstalledExtensions' (default), users can access developer tools and the JavaScript console, except in the context of extensions installed by enterprise policy.

If you set this policy to 'DeveloperToolsAllowed', users can access developer tools and the JavaScript console in all contexts, including extensions installed by enterprise policy.

If you set this policy to 'DeveloperToolsDisallowed', users cannot access developer tools or inspect website elements. Keyboard shortcuts, menu options, and context menu entries that open developer tools or the JavaScript console are disabled.

As of version 99, this policy also controls access to the 'View page source' feature. If you set this policy to 'DeveloperToolsDisallowed', users cannot view page source through keyboard shortcuts or the context menu. To fully block source viewing, add 'view-source:*' to the 'URLBlocklist' (Block access to a list of URLs) policy.

As of version 119, this policy also controls whether developer mode for Isolated Web Apps can be enabled.

As of version 128, this policy does not control developer mode on the extensions page if the 'ExtensionDeveloperModeSettings' (Control the availability of developer mode on extensions page) policy is configured.

The 'DeveloperToolsAvailabilityAllowlist' (List of URL patterns where developer tools are allowed) and 'DeveloperToolsAvailabilityBlocklist' (List of URL patterns for which developer tools are blocked) policies take precedence over this policy. Developer tools availability is determined by the first applicable rule below:

1. If a URL matches a pattern in 'DeveloperToolsAvailabilityAllowlist', developer tools are allowed.
2. If the allowlist is configured and the blocklist is not, URLs not on the allowlist are blocked.
3. If a URL matches a pattern in 'DeveloperToolsAvailabilityBlocklist', developer tools are blocked.
4. Otherwise, if neither URL-list policy is configured, or if a URL matches neither list, this policy ('DeveloperToolsAvailability' (Control where developer tools can be used)) applies as the fallback.

On Android, this policy controls inspection of targets through remote debugging. It does not enable on-device developer tools.

Policy options mapping:

* DeveloperToolsDisallowedForForceInstalledExtensions (0) = Block Edge DevTools on extensions installed by enterprise policy, allow in other contexts

* DeveloperToolsAllowed (1) = Allow using Edge DevTools

* DeveloperToolsDisallowed (2) = Don't allow using Edge DevTools

Use the preceding information when configuring this policy.

Registry

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge
HKEY_CURRENT_USER\Software\Policies\Microsoft\Edge
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: msedge/DeveloperToolsAvailability
$k = 'HKLM:\Software\Policies\Microsoft\Edge'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Control where developer tools can be used
# Possible options:
#   Block Edge DevTools on extensions installed by enterprise policy, allow in other contexts = 0
#   Allow using Edge DevTools = 1
#   Don't allow using Edge DevTools = 2
Set-ItemProperty -Path $k -Name 'DeveloperToolsAvailability' -Value 0 -Type DWord

Disable

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

Revert to "Not configured"

# Revert to "Not configured": msedge/DeveloperToolsAvailability
$k = 'HKLM:\Software\Policies\Microsoft\Edge'
Remove-ItemProperty -Path $k -Name 'DeveloperToolsAvailability' -ErrorAction SilentlyContinue

User (HKCU)

Enable

Disable

Revert to "Not configured"

Options (1)

LabelControlRegistry valueREG typeConstraints / details
Control where developer tools can be usedDeveloperToolsAvailabilityDrop-down listenumDeveloperToolsAvailabilityREG_DWORD
LabelValue
Block Edge DevTools on extensions installed by enterprise policy, allow in other contextsREG_DWORD = 0
Allow using Edge DevToolsREG_DWORD = 1
Don't allow using Edge DevToolsREG_DWORD = 2

Application

Microsoft Edge (+ Edge Update, WebView2) (Microsoft) — November 2026 templates

Official templates downloaded on November 12, 2026.