How to Fix a 400 Bad Request Error in Chrome

A 400 Bad Request error in Chrome means the server couldn’t understand the request your browser sent—often due to a corrupted URL, a bad cookie, or a browser glitch. This guide walks you through the most effective fixes, from simple refreshes to clearing your cache and resetting network settings, so you can get back to browsing quickly.

What You’ll Need

Access to Chrome’s settings menu
Your computer’s network settings (for a few advanced steps)
About 5–10 minutes of time

Step-by-Step

Refresh the page. Press Ctrl+R (Windows/Linux) or Cmd+R (Mac). Sometimes the request was malformed due to a temporary network hiccup, and a simple reload sends a clean request.
Check the URL for typos. Look for extra characters, spaces, or symbols like % or # in the address bar. A mistyped URL often triggers a 400 error. If you see something odd, edit the address and press Enter.
Clear the specific site’s cookies. Click the padlock icon next to the URL, then select “Cookies and site data” (or “Site settings”). Click the trash icon next to each cookie listed, then reload the page. Corrupted cookies are a common cause of 400 errors.
Clear all browsing data. If the site-specific fix didn’t work, go to Chrome’s menu (three dots) → “More tools” → “Clear browsing data.” Choose “All time” in the time range dropdown, check “Cookies and other site data” and “Cached images and files,” then click “Clear data.” Restart Chrome afterward.
Disable browser extensions. Type chrome://extensions in the address bar. Toggle off all extensions, then reload the page. If the error disappears, re-enable extensions one by one to find the culprit. Ad blockers and privacy tools frequently interfere with requests.
Try incognito mode. Press Ctrl+Shift+N (Windows/Linux) or Cmd+Shift+N (Mac). If the page loads there, the issue is tied to your normal profile’s cache, cookies, or extensions.
Flush DNS and reset network settings. On Windows, open Command Prompt as administrator and run ipconfig /flushdns. On Mac, run sudo dscacheutil -flushcache in Terminal. Then restart your router by unplugging it for 30 seconds and plugging it back in.
Reset Chrome settings. Go to Chrome menu → “Settings” → “Reset settings” → “Restore settings to their original defaults.” This disables extensions, clears temporary data, and resets startup pages without deleting bookmarks or passwords.
Update Chrome. Go to Chrome menu → “Help” → “About Google Chrome.” Chrome will automatically check for updates and install them. Relaunch the browser after updating.
Check the website itself. Visit a different site to see if the error appears everywhere. If only one site gives a 400 error, the problem might be on their server. Try accessing it from your phone or a different browser to confirm.

Common Mistakes

Skipping the URL check. Many 400 errors are simply caused by a pasted link that got truncated or had extra characters added. Always look at the address bar first.
Clearing only cookies, not cache. A corrupted cached file can also cause a 400 error. Clear both cookies and cached images/files together.
Forgetting to restart Chrome. After clearing data or disabling extensions, a full restart (not just closing the tab) is needed for changes to take effect.
Assuming it’s always your fault. A 400 error can be a server-side issue. Don’t spend an hour troubleshooting if the site is down for everyone—check a site like DownDetector first.

Tips

Use a bookmark. If you frequently visit a page that gives a 400 error, save a clean bookmark to avoid retyping a long URL.
Check the date and time. Incorrect system time can cause SSL and request validation failures that manifest as 400 errors. Ensure your computer’s clock is set to automatic.
Try a different browser. If Chrome continues to fail, test the same URL in Edge, Firefox, or Safari. This helps isolate whether the problem is Chrome-specific or network-wide.
Use Chrome’s built-in cleanup tool. Go to Chrome menu → “Settings” → “Reset settings” → “Clean up computer.” This scans for harmful software that might be altering your requests.

Troubleshooting

If the error persists after trying all the steps above, work through these additional checks:

Try a different network. Connect to your phone’s mobile hotspot. If the page loads, your home network’s DNS or router settings are likely the problem. Reset your router to factory defaults if flushing DNS didn’t help.
Check proxy settings. In Windows, go to Settings → Network & Internet → Proxy. Ensure “Use a proxy server” is off unless you know you need it. On Mac, check System Preferences → Network → Advanced → Proxies. A misconfigured proxy can corrupt requests.
Run Chrome’s built-in diagnostic. Type chrome://net-internals in the address bar, go to “DNS,” and click “Clear host cache.” Then go to “Sockets” and click “Flush socket pools.” This clears low-level network state.
Check for malware. Run a full antivirus scan. Some malware modifies browser requests and causes 400 errors on specific sites.
Reinstall Chrome. As a last resort, uninstall Chrome (your bookmarks and passwords will be saved if you’re signed in), then download and install the latest version from Google’s official site.

Frequently Asked Questions

What exactly causes a 400 Bad Request error?

It means the server received a request it couldn’t interpret. Common causes include malformed URLs, corrupted cookies or cache, broken browser extensions, or a misconfigured network connection.

Is a 400 error dangerous?

No. It’s a client-side error, meaning the problem is with the request your browser sent, not a security threat. It doesn’t indicate your computer is infected or your accounts are at risk.

Will clearing my browsing data log me out of websites?

Yes, clearing cookies will sign you out of most sites. You’ll need to log back in after doing so. To avoid this, try clearing only the cookies for the specific site that’s giving the error first.

Why does the error only happen on one website?

That usually points to a site-specific issue—either their server is misconfigured, or a cookie/extension is interfering only with that site’s requests. Try incognito mode or a different browser to confirm.

Can a VPN cause a 400 error?

Yes. Some VPN servers have IP addresses that websites flag, or the VPN’s encryption can alter request headers. Try disconnecting your VPN and reloading the page.

How long does it take for a 400 error to fix itself?

If it’s a server-side issue, it might resolve within minutes to hours. If it’s on your end, the steps above should fix it within 10 minutes. If it persists for days, contact the website’s support team.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →