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.
Does this apply to you?
- Browser: Google Chrome. Not version-specific.
- Devices: Windows, Mac, Linux, and Chromebook. The steps below use the desktop Settings page.
- Error text: a gray page that says This page isn’t working with HTTP ERROR 400 under it, or a plain white page that says 400 Bad Request.
- You need: nothing special. Deleting a site’s cookies may sign you out of that site, so have its password handy.
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.
- A bad or bloated cookie for one site. Sign: only one website fails, and it works fine in an Incognito window. Some servers say it directly, with a message like “Request Header Or Cookie Too Large”.
- A broken link or URL. Sign: the error only shows up when you click one specific link or paste one specific address, but the site’s home page loads fine.
- An extension changing your requests. Sign: the page works in Incognito, but still fails after you delete the site’s cookies. Extensions are off in Incognito by default, so they are the next suspect.
- A problem on the site or your network. Sign: the page fails everywhere, including Incognito, a different browser, and a different device. That points away from Chrome entirely.
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.
- Open a different website, like google.com. If every site fails, your problem is not a 400 cookie issue. Check your internet connection first.
- 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.
- 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. - 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.
- Delete cookies for just that site. Click the three-dot More menu at the top right, then Settings.
- Click Privacy and security, then Third-party cookies.
- 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.
- Type the site’s name in the search box at the top right.
- Click the trash can icon next to the site, then click Delete to confirm.
- Close the Settings tab and reload the page in a normal window. Sign in again if the site asks.
- If the error is still there, open
chrome://extensionsand 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?
- Restarting your router. A 400 means the server got your request and refused it. Your connection worked fine. Rebooting the router changes nothing about what Chrome sends.
- Clearing only cached images and files. Cookies are stored separately from the cache, and cookies are what ride along in the request. If you clear the cache but leave the cookies, the same bad cookie goes out again.
- Reinstalling Chrome. Your profile, including cookies, usually lives outside the app folder. A reinstall can bring you back to the exact same cookie and the exact same error.
- Waiting it out. If the bad cookie or bad link is on your side, the server will reject it tomorrow just like today. Only a site-side problem goes away on its own.
- Clearing all browsing data for all time. It often works, but it signs you out of every site to fix one. Delete just the one site’s cookies first.
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.
Leave a Reply