How to Re-Enable Developer Tools in Chrome

If Chrome’s Developer Tools (DevTools) have disappeared or the Inspect command is disabled, start with chrome://policy. Look for Chrome’s Developer tools availability policy and check whether it is enforced. On an unmanaged browser, Google documents the default as “Always allow use of built-in developer tools.” If a workplace, school, or device administrator enforces a blocking value, only that administrator can change it.

1. Check whether a Chrome policy is blocking DevTools

Open Chrome.
Enter chrome://policy in the address bar.
Review the policies listed on the page and their source. Google says this page shows which policies apply to the device and whether they came from platform or cloud management. View a device’s current Chrome policies.
Reload the policies if the page offers a reload control, then filter for the Developer tools availability policy.

The relevant setting controls whether Chrome’s built-in Developer Tools can be opened. Google documents three practical states: allow use, disallow use, and a setting that leaves the policy unconfigured. URL restrictions can also limit where DevTools may open, so inspect those policies if the general availability setting allows tools but a particular site still blocks them.

2. If Chrome is managed, ask the administrator to allow DevTools

A managed browser can receive policy from an organization’s cloud administration, an enrolled browser or device, or local management tools on a managed PC. Open chrome://policy and record the policy name and source before contacting the administrator.

What the administrator should change

Find the Developer tools availability policy in the organization’s Chrome policy system.
Change it to the allow option, documented by Google as Always allow use of built-in developer tools.
Check URL restrictions if DevTools must work only on certain pages or currently fails on one site.
Apply the change through the system that supplied the policy: the Admin console for managed users or enrolled browsers, or the local management method used for managed PCs. See Google’s policy configuration guide and managed-PC policy guide.

Policy updates usually take effect in minutes, but Google says they can take up to 24 hours to apply to everyone. Close and reopen Chrome after the administrator confirms the change, then revisit chrome://policy to verify the new value.

3. If Chrome is not managed

If chrome://policy shows no restrictive Developer tools availability policy and Chrome is not managed, the official documentation does not define one universal user-side repair for every possible cause. Avoid deleting registry entries or changing machine policies without knowing who controls the device. If the computer belongs to an organization, send the policy-page details to its administrator even if the browser does not obviously display a management message.

4. Troubleshooting checklist

Symptom	Likely cause	Action
Inspect or DevTools cannot be opened anywhere	Developer tools availability is set to never allow	Check `chrome://policy`; ask the policy owner to select the allow option.
DevTools works on some pages but not others	A URL restriction applies	Have the administrator review URL allow/block restrictions alongside the general DevTools policy.
The policy value changed but DevTools is still disabled	Policy propagation or an old browser session	Reload policies, restart Chrome, and allow several minutes; organization-wide propagation may take up to 24 hours.
The policy lists a platform or cloud source you do not control	Device or organization management	Contact the administrator responsible for that source; a local user change will not override an enforced policy.
No restrictive policy appears	Cause is not identified by the reviewed official documentation	Share the `chrome://policy` output and device ownership with your support team instead of changing system policy blindly.

5. Reliability and timing considerations

Verify the source: The same policy name can be supplied by cloud administration or local/platform management. The source shown at chrome://policy tells you whom to contact.
Check scope: Policies may apply to a user, an enrolled browser, or the whole device. A change for one scope may not affect another.
Allow for propagation: Google’s guidance is minutes in normal cases and up to 24 hours for everyone.
Recheck after updates: After the administrator changes the setting, reload the policy page and restart Chrome before escalating.

Or skip the browser setup

If your goal is to capture a page for documentation, QA, or an automated workflow, ScreenshotNeo returns a screenshot or PDF through one GET request, so a local DevTools session is not required. See the ScreenshotNeo API documentation for all options.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

Node.js

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing result. It also provides an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Create a free ScreenshotNeo account.

FAQ

What is the first thing to check when Inspect is disabled?

Open chrome://policy and inspect the Developer tools availability policy and its source.

Can I override a workplace DevTools policy myself?

No. When the policy is enforced by cloud, device, or local management, the administrator who controls that policy must change it.

How long does an administrator change take?

Google says changes usually apply in minutes but can take up to 24 hours for everyone.

Why might DevTools fail only on one website?

A URL restriction may independently control where Developer Tools can open. Ask the administrator to review those restrictions.

Does ScreenshotNeo require Chrome DevTools?

No. Its API captures the target URL directly, and its MCP server lets supported AI agents request screenshots without a local browser setup.