YouTube Subtitles Not Working? Here's What's Actually Wrong

You press CC. Nothing happens. Or the button turns on and the screen stays empty. Or you get "Error loading captions" and no explanation of what went wrong.

Search for the problem and every page gives you the same list: clear your cache, check your internet, update your browser, restart the app, reinstall it. A few also suggest turning off your browser extensions. One or two suggest a VPN, without saying why that would have anything to do with subtitles.

That advice isn't wrong so much as aimed at one failure out of three. Below is what the three are, how to tell in about ten seconds which one you have, and what can actually be done about each.

Get subtitles on any video — free →

Three different failures, one symptom

A subtitle has to survive three steps to reach your eyes:

1. A caption track has to exist for that video.
2. YouTube has to hand it to your device when the player asks.
3. The player has to draw it on the screen.

Break any one of them and the result looks identical: the CC button does nothing. But the three break for completely unrelated reasons, and the standard advice — cache, restart, reinstall — only ever touches step 3.

That's why the fixes work brilliantly for some people and do nothing at all for everyone else, and why the same video can look broken to you and fine to the person you sent it to.

Failure 1: there is no caption track

This is the most common one, and the most invisible, because YouTube's interface doesn't distinguish "captions failed" from "captions were never made".

Not every video has captions. The creator may not have uploaded any, and YouTube's automatic speech recognition doesn't run on everything — YouTube's own help page lists the cases where it produces nothing: the audio is still processing, the spoken language isn't supported for auto-captioning, the video is too long, the sound quality is poor, there's a long silence at the start, or several people talk over each other. Some creators also switch captions off on their uploads.

How to tell in ten seconds: open the ⋯ menu under the video and look for Show transcript. If there's no transcript entry, there is no track, and nothing you do to your browser will create one. On mobile, tap the CC icon — if the Captions list is empty rather than populated, same conclusion.

If that's your case, the rest of this article won't help you, but the guide to videos with no captions at all will.

Failure 2: the track exists, YouTube just won't give it to you

This is the failure nobody names, and it's the reason "Error loading captions" exists as a distinct message.

Caption text doesn't ship inside the video. When you press CC, your browser makes a separate request to a YouTube endpoint that serves subtitle files. That request can be refused independently of the video, which is why the picture keeps playing perfectly while the subtitles never arrive.

The most common refusal is rate limiting. YouTube throttles that endpoint aggressively, and the limit is applied per IP address, not per account. We can be unusually specific about this because we fetch caption tracks at scale ourselves, and we get throttled too — our own code has a dedicated error type for it and stops retrying the moment it appears, because retrying from the same IP after a refusal is pure waste.

Several things follow from that, and they explain symptoms that otherwise look like nonsense:

• A VPN "fixes" it. That's the tell. Nothing about your browser changed; your IP address did. This is why the tip circulates in forums with no explanation attached — people found that it works without knowing why.
• It comes back by itself. Rate limits expire. If subtitles were dead this morning and fine tonight on the same video, nobody fixed anything and nothing you did helped.
• It hits whole households and offices at once. Shared connections, university networks, mobile carrier NAT and VPN exit nodes pool many people behind one address. Your neighbour's YouTube habits can cost you subtitles.
• Clearing your cache cannot touch it. The refusal happens on YouTube's side, before anything reaches your machine to be cached.

How to tell in ten seconds: the transcript entry exists in the ⋯ menu but opening it fails or hangs, or you see the literal "Error loading captions" text. Try the same video on your phone with Wi-Fi off, on mobile data — a different network path. If subtitles appear there, the track is fine and your connection was the problem.

Failure 3: the captions arrive and the player doesn't draw them

This is the smallest of the three and the one all the standard advice is written for. It's worth knowing the specific cases, because they're much more particular than "clear your cache".

• Fullscreen. By far the most reported version, and it's a rendering bug, not a caption problem: the text is being delivered and the caption layer ends up behind or outside the video surface. Leaving and re-entering fullscreen usually restores it.
• Another extension. Ad blockers, script blockers, privacy extensions and other subtitle tools can block the caption request or fight over the same layer of the page. This is a real cause, and the advice to test with extensions disabled is sound — see the honest note about our own below.
• Playback speed. At unusual speeds some clients drop the caption timing. Setting speed back to 1× and letting the player resync is a genuine fix here.
• A setting that stuck. If you once picked an auto-translated language, the player can keep asking for that translation on every video afterwards. Turning captions off and on again, or reselecting the original track rather than a translated one, clears it.

Why every page tells you to clear your cache

Because it's the advice that's true for failure 3, safe to give, and impossible to disprove from the outside.

Look at who's answering this question. The results are dominated by video-repair software, data-recovery blogs and transcript SaaS pages — businesses whose product has nothing to do with YouTube's caption delivery, writing generic troubleshooting to rank. None of them can tell you whether a track exists for your video, and none of them mentions IP-level rate limiting at all, so the one failure that most needs an explanation is the one that never gets one.

The result is a page that helps a minority and quietly wastes everyone else's afternoon on reinstalling a browser.

What actually works: stop depending on YouTube's caption path

There's a structural point hiding in failure 2. The refusal is aimed at your browser session, from your IP address. It isn't a statement about the video, and it isn't permanent.

That's the gap Linglass fills, and it's worth being precise about how, because it's not magic:

• A different fetch path. When YouTube won't serve captions to your session, Linglass falls back to fetching the track through its own servers instead. Different path, different address — so a track that your browser was refused can still arrive.
• Its own subtitle layer. Linglass draws subtitles in an isolated layer of its own rather than relying on YouTube's caption renderer, including in fullscreen. When the native CC button is dead, that layer still works — we built it that way precisely because we kept meeting videos where YouTube's own caption display had given up.
• Transcription when there's genuinely no track. For failure 1, where no captions were ever made, Linglass can transcribe the audio itself and produce a subtitle line YouTube never generated — including on videos where two languages are spoken, which YouTube names as a case its recognition fails on.
• Two lines at once. Since it's drawing its own layer anyway, it can show the original and your language together, which YouTube can't do at all.

Honest limits

This isn't a universal fix, and the places it doesn't reach are worth stating plainly.

• We can be throttled too. A different path is not an immune one. When YouTube's throttling is wide enough, our servers meet it as well, and then Linglass tells you that's what happened instead of showing you an empty screen.
• Some videos are genuinely closed. Private, members-only, region-blocked and unreleased videos won't produce captions through any route, and no tool should promise otherwise.
• An extension conflict is a real cause, and we're an extension. If subtitles broke right after you installed something, test with it disabled — including us. We'd rather you found the actual cause than kept a tool that's in the way.
• Desktop browsers, plus an iPhone and iPad app. The extension runs in Chrome, Edge and Yandex Browser on desktop. Phones and tablets go through the iOS app; there's no Android app yet, and smart TVs aren't reachable by any extension.

Frequently asked questions

Why are my YouTube subtitles not working?

There are three unrelated causes with the same symptom: the video has no caption track at all, YouTube is refusing to send the track to your device, or the player is failing to draw a track it did receive. Clearing your cache only addresses the third. Check the ⋯ menu for Show transcript first — if it isn't there, no track exists and no browser fix will create one.

What does "Error loading captions" mean on YouTube?

It means the separate request your player makes for the subtitle file failed. Most often YouTube rate-limited that request, which it does per IP address rather than per account, so everyone sharing your connection is affected at once and it clears on its own after a while. It is not a sign that anything on your device is broken or corrupted.

Why do YouTube subtitles disappear in fullscreen?

That's a rendering fault rather than a caption fault — the text is being delivered and the caption layer ends up misplaced relative to the video surface. Leaving and re-entering fullscreen usually brings it back. It's the most reported version of the problem and one of the few that the standard troubleshooting advice genuinely fixes.

Why does a VPN fix YouTube subtitles?

Because it changes your IP address, and YouTube's caption throttling is applied per IP. If a VPN restores subtitles, that confirms the caption track exists and was simply refused to your connection. Waiting also works, since rate limits expire, and neither fact has anything to do with your cache or your browser version.

Can browser extensions stop YouTube subtitles from working?

Yes. Ad blockers, script blockers and other subtitle tools can block the caption request or compete for the same part of the page. Testing with extensions disabled is legitimate advice, including for subtitle extensions like ours — a tool that turns out to be the cause of your problem isn't worth keeping.

Can I get subtitles when YouTube won't load them?

Often, yes. Because the refusal targets your browser session rather than the video, fetching the same track by another route can succeed where your player failed, and audio can be transcribed directly when no track was ever made. A free extension like Linglass does both in the player and draws its own subtitle layer, so it doesn't depend on YouTube's caption display working.

Quick recap

• Three unrelated failures share one symptom: no track exists, the track isn't delivered, or the player doesn't draw it.
• Show transcript in the ⋯ menu is the ten-second test. No transcript means no track, and no amount of browser maintenance will make one.
• "Error loading captions" is usually IP-level rate limiting. That's why a VPN appears to fix it, why it returns on its own, and why your whole household loses subtitles together.
• Fullscreen, extension conflicts, playback speed and a stuck translation setting are the real members of the third category — cache-clearing is a blunt stand-in for these.
• A tool that fetches captions by a different route and draws its own subtitle layer sidesteps two of the three failures, and can transcribe the audio for the third.

The CC button isn't lying to you. It just has no way to tell you which of three very different things went wrong — and once you know which one you have, two of them stop being your problem to fix.