Chrome HTTP ERROR 400 Bad Request: How to Fix It


An HTTP ERROR 400 in Chrome means the website’s server rejected the request your browser sent as malformed. It is usually tied to one site, often because of a broken or oversized cookie for that site, a mistyped or mangled URL, or an extension changing the request. The fastest test is to open the same page in an Incognito window, and if it loads there, delete that one site’s cookies.

Prefer to watch? This short video walks through the same checks.

Does this apply to you?

What does HTTP ERROR 400 mean in Chrome?

Every time you open a page, Chrome sends the website a request. That request carries the address, some headers, and any cookies the site saved on your computer earlier. A 400 status code is the server’s way of saying, “I can’t read what you sent me.” It is a client-side error, so the server is not down. Something in the request itself did not make sense to it.

That is useful to know. It means the fix is usually on your side, and usually for just one site. A 500-type error is different. That one means the website itself is broken, and only the site owner can fix it.

Why does this happen? Find your branch

Check which of these matches what you see. Each one has a quick sign.

How do you fix HTTP ERROR 400 in Chrome?

Work through these in order. The first two steps are tests that tell you which branch you are in. They take under a minute.

  1. Open a different website, like google.com. If every site fails, your problem is not a 400 cookie issue. Check your internet connection first.
  2. Reload the failing page with Ctrl + Shift + R on Windows, Linux, or ChromeOS, or Cmd + Shift + R on a Mac. This makes Chrome fetch a fresh copy instead of using cached files.
  3. Look at the address bar. If the link is very long, has odd symbols or spaces, or was copied from an email, trim it back to the site’s main address (for example, example.com) and navigate from there.
  4. Open an Incognito window with Ctrl + Shift + N (or Cmd + Shift + N on a Mac) and paste the same address. If the page loads, the cause is saved cookies or an extension in your normal window. Keep going.
  5. Delete cookies for just that site. Click the three-dot More menu at the top right, then Settings.
  6. Click Privacy and security, then Third-party cookies.
  7. Click See all site data and permissions. This link is near the bottom of the page, so scroll down if you don’t see it.
  8. Type the site’s name in the search box at the top right.
  9. Click the trash can icon next to the site, then click Delete to confirm.
  10. Close the Settings tab and reload the page in a normal window. Sign in again if the site asks.
  11. If the error is still there, open chrome://extensions and turn off your extensions. Reload the page. If it works, turn extensions back on one at a time, reloading after each, until the error comes back. That last one is the cause.

Deleting one site’s cookies only affects that site. Your other logins, saved passwords, and bookmarks stay where they are.

What does not fix this?

Frequently asked questions

Is HTTP ERROR 400 a virus or a sign my computer is hacked?

No. It is a normal status code a server sends when it can’t read a request. It says nothing about malware on your device.

Why does the page work in Incognito but not in a normal window?

Incognito starts with no saved cookies and, by default, no extensions. If the page loads there, one of those two things in your normal window is causing the bad request.

Will deleting a site’s cookies delete my saved password?

No. Saved passwords are stored in Chrome’s password manager, not in cookies. You will be signed out of that one site, but Chrome can still fill in your password.

The page fails on every browser and device. What now?

Then the problem is almost certainly on the website’s side, or on a network filter between you and it, such as a school or work network. Contact the site owner or your IT admin.

Conclusion

An HTTP ERROR 400 means the site could not read what Chrome sent. Test in Incognito first, then delete just that site’s cookies, and check extensions if it still fails. If it fails everywhere, the fix belongs to the website, not to you.

Related guides