Short answer: a “400 Bad Request” error on YouTube means your Chromebook sent a request the video server could not read, almost always because of a corrupted or oversized cookie tied to your Google account, or a browser extension quietly rewriting the request. It is not a YouTube outage. Clearing the site data for YouTube and Google, then testing in Guest mode, fixes it for most people in under two minutes.
What does “400 Bad Request” mean on YouTube?
A 400 error is Chrome telling you, on the server’s behalf, that the request it sent was malformed. YouTube’s servers could not make sense of it, so they refused to answer. That is different from a 500-series error, which means the server itself is having trouble. A 400 almost always traces back to something Chrome sent, not something YouTube broke.
On real Chromebook reports, the two most common culprits are a stale or oversized cookie for a Google domain, and a browser extension that modifies outgoing requests before Chrome sends them. One Chromebook user, in a Chromebook Community thread, described the underlying mechanism plainly after hitting the same “Bad Request” wall on a different Google-connected page: “Bad Request. Your browser sent a request that this server could not understand. Size of a request header field exceeds server limit.” That is a cookie or header problem, not a broken video or a dead server. In the same thread, another reader reported the exact YouTube version of it: “I tried to get onto YouTube, and it said error 400 server not found, but that’s a very popular site so idk why it wouldn’t be working.”
A separate Chromebook Community thread has a nearly identical report: a Chromebook owner who could not watch any YouTube video and had already tried clearing the cache without success before asking for help.
Why this happens: find your branch first
Before you start changing settings, figure out which pattern matches what you are seeing. That tells you which fix to try first instead of working through all of them.
- Only YouTube fails; every other site is fine. This points to a cookie problem scoped to google.com or youtube.com specifically. Start with the site-data fix below.
- The error disappears in Guest mode or Incognito. That isolates the cause to an extension or a custom theme, since both are disabled in Guest sessions by default.
- It only happens on this Chromebook, not on your phone or another computer signed into the same account. This rules out your account or YouTube itself. The problem is local: a corrupted cookie, cache entry, or extension living only on this device’s Chrome profile.
- You are on a school or work Chromebook. Managed devices sometimes route traffic through a network filter that rewrites or blocks requests in a way Chrome reports back as a 400. If that matches, this is a network policy question for your IT admin, not something you can fix from Chrome’s settings.
How to fix YouTube error 400 on a Chromebook
Work through these in order. Most people are fixed by the first two.
- Clear site data for YouTube and Google specifically, not your whole history. Open a new tab and go to chrome://settings/content/all. Search for youtube.com, tap it, and choose Clear data. Repeat for google.com and accounts.google.com. Clearing just these sites avoids wiping saved logins for everything else you use.
- Test in Guest mode. Sign out, or open a Guest session from the Chromebook sign-in screen, and try the same YouTube video. If it plays, an extension or theme in your normal profile is the cause. Sign back in, open chrome://extensions, and disable your extensions one at a time, reloading YouTube after each, until you find the one responsible.
- Reset Chrome settings to their defaults. Go to Settings, then Reset settings, then Restore settings to their original defaults. This clears corrupted site permissions and startup settings without touching your bookmarks or saved passwords, and it has fixed this for multiple people in real reports even after a plain cache clear did not.
- Restart the Chromebook. This will not fix the underlying cookie or header problem by itself, but it clears any half-loaded state and confirms the fix from the earlier steps has fully taken effect.
A safety note before you touch device-wide settings: skip Powerwash for this. It erases everything on the device and signs you out of every app to fix what is normally a two-minute cookie problem, and see the section below on why it often does not even address the real cause.
What does not fix this
- Waiting it out. A 400 is not a server outage, so there is nothing on YouTube’s side to recover. If the request Chrome sends is still malformed tomorrow, you will see the same error tomorrow.
- Clearing cache and cookies for “all sites, all time” without staying signed out. Several people report the error coming right back within minutes of doing a full clear. If you stayed signed in to your Google account while clearing, a synced copy of the same corrupted cookie can be pulled back down automatically. Sign out first, clear the site data for the Google domains, then sign back in.
- Powerwash. It wipes the device, but if the bad cookie is tied to your Google account and gets re-synced on first sign-in, the error can return on a freshly wiped Chromebook. It is also a lot of disruption for a browser-level fix.
- Restarting the router or switching Wi-Fi networks. This helps with connection errors, not malformed-request errors. If the same account fails on this Chromebook but works fine over the same network on a phone or laptop, your network is not the problem.
Frequently asked questions
Is YouTube error 400 a problem with YouTube’s servers?
No. A 400 status means the server rejected the request as malformed before it even tried to process it. The fault is in what your Chromebook sent, typically a cookie or a request header, not in YouTube’s availability.
Will clearing site data delete my saved passwords?
No, as long as you clear data for specific sites (youtube.com, google.com) rather than choosing “Clear browsing data” with every category checked. Site-specific clearing removes cookies and cached files for that site only and leaves your saved passwords in Chrome’s password manager untouched.
Why does this only happen on my Chromebook and not my phone?
Because the corrupted cookie or interfering extension lives in this device’s Chrome profile, not in your Google account. Your account is fine, which is why the same login works everywhere else. The fix has to happen locally, on this Chromebook.
I’m on a school Chromebook and none of this works. What now?
If Guest mode and site-data clearing don’t help, the request is likely being altered by your school or organization’s network filtering before it reaches YouTube. That’s a network policy issue, and only your school or work IT administrator can adjust it.
Still stuck?
If you have worked through the branch that matches your situation and the error persists, the cause is most likely on the network or account-policy side rather than something fixable from Chrome’s own settings. At that point, a Chromebook-specific report to Google’s Chromebook Help Community, with your exact error text and whether Guest mode fixes it, is the fastest path to an answer specific to your setup.
