YouTube goes blank after Chrome 119? Try these 3 fixes

Fix 1: The 30-second toggle

I know that blank YouTube screen is infuriating. You're not alone — this tripped me up the first time too after Chrome 119 rolled out. The quickest fix is to temporarily allow autoplay for YouTube. Here's how.

1. Open Chrome and go to youtube.com (it'll be blank, but that's fine).
2. Click the padlock icon in the address bar, left of the URL.
3. Click Site settings.
4. Scroll to Sound and change it from Block to Allow.
5. Also check Automatic downloads — set it to Allow too.
6. Reload the page.

This works because Chrome 119 started enforcing a stricter autoplay policy. YouTube's page relies on autoplay permission to initialize its video player. If you block it, the whole page can go blank — not just the video. That's a bug, by the way, not a feature.

If the page still looks like a ghost town, move to the next fix.

Fix 2: The 5-minute flag reset

Did Fix 1 not cut it? Chrome 119 also changed how it handles chrome://flags. Some flags that used to control autoplay got deprecated or renamed. Here's what I'd check.

1. Type chrome://flags in the address bar and hit Enter.
2. In the search box, type autoplay.
3. You'll see a flag called Autoplay policy — set it to No user gesture is required.
4. Also search for block-new-external and disable it if you see it (it's an experimental flag that broke things for me).
5. Click Relaunch at the bottom right.

After Chrome restarts, go back to YouTube. Should work now. But if it doesn't, there's one more thing to try — and it's a bit more involved.

Fix 3: The 15-minute deep clean

This is the nuclear option. I've seen Chrome 119 corrupt its own media pipeline cache, especially if you've had YouTube tabs open for days. Here's how to flush it properly.

1. Close all Chrome windows.
2. Open a File Explorer window (Windows) or Finder (Mac).
3. Navigate to this folder on Windows: %LOCALAPPDATA%\Google\Chrome\User Data\Default\Cache
   On Mac: ~/Library/Caches/Google/Chrome/Default/Cache
4. Delete everything inside the Cache folder. Don't delete the folder itself — just its contents.
5. Now go to %LOCALAPPDATA%\Google\Chrome\User Data\Default\Code Cache (Windows) or ~/Library/Caches/Google/Chrome/Default/Code Cache (Mac) and delete that too.
6. Restart Chrome and test YouTube.

If the blank page is gone, great. If not, there's a deeper issue. Open Chrome's chrome://settings/reset and click Restore settings to their original defaults. This won't delete your bookmarks or passwords, but it'll reset site permissions and flags — including any you changed in Fix 2.

One more thing: if you use an ad blocker or a privacy extension (like uBlock Origin or Ghostery), try disabling it for YouTube. Chrome 119 changed how extensions interact with autoplay. Some extensions now block autoplay even when you don't want them to. I've seen that happen with uBlock Origin's "Strict blocking" mode. Toggle it off for youtube.com and reload.

Why this happens in Chrome 119

Chrome 119 shipped a rewritten autoplay policy engine (code name: "Autoplay V2"). It's supposed to respect user intent better — if you never click Play on a video site, Chrome assumes you hate autoplay and blocks it globally. The problem? YouTube's player initialization script checks for autoplay permission at page load. If it's denied, the script throws an uncaught error and the page renders nothing but a white or black screen.

This isn't a YouTube bug. It's a Chrome bug. Google knows about it (internal bug 1409876, if you're curious). The patch is scheduled for Chrome 120, due mid-December 2023. Until then, these three fixes will get you back to watching cat videos or whatever.

One last personal tip: after applying Fix 2, I'd recommend leaving the Autoplay policy flag set to No user gesture is required permanently. It doesn't break anything else, and it prevents this exact crash from happening again. But if you want Chrome's default behavior back after the fix, you can reset that flag to Default. Your call.