Control where Chrome DevTools can be used

Setting the policy to 0 (the default) means you can access Chrome DevTools and the JavaScript console, but not in the context of extensions installed by enterprise policy or, since version 114 and if this is a managed user, extensions built into the browser. Setting the policy to 1 means you can access Chrome DevTools and the JavaScript console in all contexts, including that of extensions installed by enterprise policy. Setting the policy to 2 means you can't access Chrome DevTools, and you can't inspect website elements.

This setting also turns off keyboard shortcuts and menu or context menu entries to open Chrome DevTools or the JavaScript console.

As of Google Chrome version 99, this setting also controls entry points for the 'View page source' feature. If you set this policy to 'DeveloperToolsDisallowed' (value 2), users cannot access source viewing via keyboard shortcut or the context menu. To fully block source viewing, you must also add 'view-source:*' to the URLBlocklist policy.

As of Google Chrome version 119, this setting also controls whether developer mode for Isolated Web Apps can be activated and used.

As of Google Chrome version 128, this setting will not control developer mode on extensions page if ExtensionDeveloperModeSettings policy is set.

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.

The DeveloperToolsAvailabilityAllowlist and DeveloperToolsAvailabilityBlocklist policies take precedence over this policy. The availability of Chrome DevTools is determined in the following order of precedence:

1. If a URL matches a pattern in the DeveloperToolsAvailabilityAllowlist policy, Chrome DevTools are allowed.
2. If the DeveloperToolsAvailabilityAllowlist is set and the DeveloperToolsAvailabilityBlocklist is not, any URL not on the allowlist is blocked.
3. If a URL matches a pattern in the DeveloperToolsAvailabilityBlocklist policy, Chrome DevTools are blocked.
4. If neither policy is set, or if a URL matches neither list, this policy (DeveloperToolsAvailability) is used as the fallback mechanism.