How To Disable Chrome Security In Windows

To disable Chrome’s Safe Browsing protection in Windows, open Settings, select Privacy and security, then Security, and choose No protection. If you mean disabling web security for development, use a separate test profile with the --disable-web-security command-line switch. These changes affect different protections; neither is.

Choose the setting that matches the problem

Before changing anything, identify what Chrome is blocking. A dangerous-site warning, a broken extension and a cross-origin request error have different causes. Changing several settings together makes it harder to find the cause and restore your original configuration.

• For phishing or malware warnings, review Safe Browsing settings.
• For cross-origin errors in an application you are developing, investigate the server’s cross-origin resource sharing (CORS) configuration.
• For a page that behaves incorrectly, test extensions and individual site permissions first.
• For certificate or connection errors, investigate the connection and certificate rather than assuming Safe Browsing is responsible.

Chrome settings are separate from Windows security controls. If you were looking for Control Panel instead, see where System and Security is in Windows 10. Changing Windows antivirus or firewall settings is not part of the Chrome procedures below.

Turn off Safe Browsing temporarily

Safe Browsing helps identify dangerous sites, downloads and extensions. Turning it off removes those protections; it does not make a flagged site trustworthy. Google’s unsafe-site warning instructions place this control in Chrome Settings.

1. Open Chrome and select the three-dot menu at the top right.
2. Select Settings, then Privacy and security.
3. Open Security.
4. Under Safe Browsing, select No protection (not recommended). Confirm the change if prompted.
5. Complete only the specific check that required the change.
6. Return to the same screen and restore your previous protection level.

You can also reach the security page by entering chrome://settings/security in the address bar. You do not need to find an “Enable phishing and malware protection” experiment in chrome://flags.

If you only want to move away from Enhanced protection, Standard protection remains an available Safe Browsing level. Selecting it keeps protection against identified threats instead of switching protection off completely.

On a work or school computer, an administrator may enforce this setting. Ask the administrator to review the blocked resource if the control is unavailable.

Disable web security for a separate development session

The --disable-web-security switch relaxes same-origin policy enforcement for development testing. It is different from Safe Browsing and does not fix the server configuration that causes a CORS error. Treat a successful request in this session as a diagnostic result, not evidence that the application will work in a normal browser.

Chromium’s switch documentation change specifies that this flag requires a custom user data directory. Use a dedicated, disposable directory rather than your everyday Chrome profile.

Create a dedicated Windows shortcut

1. Save your work and exit Chrome.
2. Copy a Chrome desktop shortcut and rename the copy “Chrome development test”. Keep your ordinary shortcut for daily browsing.
3. Right-click the copied shortcut, select Properties and open the Shortcut tab.
4. In Target, keep the existing path to chrome.exe. After its closing quotation mark, add a space followed by --disable-web-security --user-data-dir="%TEMP%\chrome-web-security-test".
5. Select Apply, then OK, and launch Chrome using the copied shortcut.
6. Open chrome://version and inspect the Command Line entry to check that the switches were passed to this instance.

For example, if Chrome is installed at the following location, the complete Target would be:

"C:\Program Files\Google\Chrome\Application\chrome.exe" --disable-web-security --user-data-dir="%TEMP%\chrome-web-security-test"

Keep your shortcut’s actual executable path if it differs. Chromium’s Windows launch instructions explain shortcut switches and checking chrome://version. Command-line switches and experiments on chrome://flags are separate mechanisms, and development switches can change or disappear.

Use this session only for your own test application. Leave it signed out and avoid email, banking and unrelated browsing. The separate directory keeps test browser data apart from your normal profile; it does not isolate the browser from the rest of Windows.

When finished, close the test browser and delete the copied shortcut. Reopen Chrome through your ordinary shortcut and check that its Command Line entry no longer includes --disable-web-security. Correct the application’s CORS configuration before testing again with normal browser protections.

Troubleshoot extensions and JavaScript without broad changes

Test extensions individually

For layout problems, redirects or missing page features, an extension may be involved. Follow Google’s extension management instructions to test one at a time.

1. Open the three-dot menu, select Extensions, then Manage extensions.
2. Turn off one suspected extension.
3. Reload the affected page and repeat the action that failed.
4. If nothing changes, restore that extension before testing another.

If an extension causes the problem, leave it disabled while you investigate or remove it if you no longer need it. Record any security-related extension you temporarily turn off so you can restore its protection.

Change JavaScript for the affected site

Blocking JavaScript can help diagnose script-related behaviour, but forms and interactive features may stop working. Use Chrome’s site permission controls to limit the change to the page you are testing.

1. Open the affected website.
2. Select the site information icon to the left of its address, then Site settings.
3. Change JavaScript to Block and reload the page.
4. After testing, return JavaScript to its previous setting and reload again.

Keep sandboxing and updates in place

Disabling the sandbox with --no-sandbox removes a protection boundary between web content and your system. It is not a routine fix for a website that will not load. Safe Browsing, sandboxing and site isolation serve different purposes, as described in Google’s Chrome security overview.

Keep automatic updates working while troubleshooting. To check for an update, select the three-dot menu, Help, then About Google Chrome. Apply any available update and relaunch when prompted, following Google’s update instructions.

For broader operating-system questions, browse the Windows security guides. A separate guide explains the Windows Security button on a Lenovo ThinkPad if that is the control you meant.

Start by recording the exact warning or error, then change only the matching setting above and retest with your original protections restored.