YouTube Auto-Translate Subtitles Not Working? Here's Why

You open a video, hit the CC button, go looking for Auto-translate — and it isn't there. Or it's there, you pick your language, and nothing changes on screen.

Search for the problem and you get the same five steps everywhere: refresh the page, clear your cache, update your browser, check your internet, toggle the setting off and on. Those steps fix a rendering glitch. What you have is almost certainly not a rendering glitch.

Here is the actual mechanism, taken from YouTube's own documentation — and what to do in the case the documentation admits it can't handle.

Get a translated subtitle line on any video — free →

Auto-translate translates captions. It doesn't create them.

This one sentence explains most of the failures.

YouTube's auto-translate works on a caption track that already exists — either one the creator uploaded, or one YouTube generated by speech recognition. It takes that text and machine-translates it. It is a translation layer, not a transcription layer.

So when the Auto-translate submenu is missing entirely, it is usually not hiding. There is nothing under it, because the video has no caption track to translate. The menu correctly reflects an empty input.

That reframes the question. You don't have a translation problem. You have a captions problem, and it's worth knowing exactly why the captions aren't there.

The six reasons YouTube gives for no automatic captions

From YouTube's own help page on automatic captioning, automatic captions may not be generated because:

1. The captions aren't available yet, because the video's audio is still being processed.
2. Automatic captions don't support the language spoken in the video.
3. The video is too long.
4. The video has poor sound quality, or YouTube doesn't recognise the speech.
5. There's a long period of silence at the beginning of the video.
6. There are multiple speakers whose speech overlaps, or multiple languages at the same time.

Read that list again with the cache advice in mind. Not one of these six is anything you can fix from your side of the screen. Refreshing helps with exactly one of them — the first — and only by waiting.

The creator can also switch captions off for a video entirely, which produces the same empty menu.

Which one is yours? How to tell in ten seconds

Open the CC menu and read what's in it, not what's missing:

• No CC button at all, or a dead one. No track. You're in the list above — most often reason 2, 4 or 6.
• CC works, one language, no Auto-translate option. Unusual, and normally the creator's captions are marked in a way that blocks translation, or you're on a client that doesn't expose the submenu. Try desktop web.
• CC works, Auto-translate is there, your language isn't in it. Rare — the target list is long. Check you're in the second-level menu (Subtitles → Auto-translate) and not the first.
• Auto-translate runs, but the text is nonsense. The source track is a bad machine transcription. Translating a bad transcription twice does not improve it; this is reason 4 or 6 wearing a disguise.

That last case is the one people never diagnose, because something does appear on screen. A poor auto-caption translated into your language is worse than no subtitles, because it reads as confident and it's wrong.

"It works on my laptop but not on my phone"

This is the single most common follow-up, in every language we looked at. The short answer: auto-translate does exist on the mobile apps — it's just buried and it fails silently.

On iOS and Android, the path is the CC icon → Captions → Auto-translate → your language. Three levels down, and if the video has no caption track the option is simply absent, with no explanation. On desktop the same absence is easier to read as "this video has no captions"; on a phone it reads as "the app is broken".

So if it works on your laptop and not on your phone for the same video, check the menu path first. If it fails on both, you're back to the six reasons — the video, not the device.

Browser extensions are a desktop thing, so the fix below runs in a desktop browser; on iPhone and iPad, YouTube is covered by our app instead. The full platform matrix is in dual subtitles on phone and tablet.

What actually works: don't wait for YouTube's captions

If the problem is that there's no track to translate, the fix is to produce one.

Linglass is a free browser extension that does the two things auto-translate can't:

It transcribes the audio when there are no captions. Speech recognition runs on the video's own sound, so a video YouTube never captioned gets a subtitle line anyway — including the cases in reasons 2, 4, 5 and 6. See no captions available for this video for that path in detail.

It translates on its own, not through YouTube's list. The translated line is produced independently, into any of the 22 languages the extension supports, so it doesn't depend on YouTube offering that pair.

And because it owns both lines, you get them at the same time: the original language on one line and your own underneath, which is the thing auto-translate can't do at all — YouTube shows one caption track, translated or not, never both. That's dual subtitles, and it's the reason most people keep it after the problem that brought them is solved.

Setup, once:

1. Install the extension (Chrome, Edge, Brave, Opera and other Chromium browsers) and create a free account.
2. Pick two languages: the one you're learning, and your native one.
3. Open any video. If it has captions, both lines appear. If it doesn't, transcription starts and you'll see its progress in the player.

Any word on either line is clickable for a translation in context, its pronunciation, and one-tap saving into spaced-repetition review.

The case YouTube specifically says it fails: two languages at once

Reason 6 on that list — "multiple languages at the same time" — deserves its own note, because it's common in exactly the content language learners watch. Interviews with a translator. Vlogs by bilingual creators. Any video where a speaker code-switches mid-sentence.

YouTube's speech recognition assumes one language per video. Feed it two and it either refuses or, worse, transcribes the whole thing as the dominant language and mangles the rest.

We built specifically for this. Transcription runs in chunks, each chunk's language is detected on its own, and the result is verified against the writing system it came out in — so a Mandarin passage inside an English interview is transcribed as Mandarin rather than being forced into English-looking nonsense. It's the one failure on YouTube's list that we treat as a first-class case rather than an edge case.

Honest limits

• Very long videos. Transcription has an upper length limit. Feature-length material is fine; a ten-hour stream is not.
• The free plan has a monthly transcription allowance. Translating existing captions is unlimited on the free plan; generating captions from audio is metered, because it costs real money per minute of audio.
• Music, and near-silence. If YouTube's recognition failed because there is barely any speech, ours will find barely any speech too. No tool invents dialogue that isn't there.
• Desktop browsers for the extension. Phones and tablets go through the app; smart TVs aren't reachable by anything.
• Accuracy is transcription, not a script. It's usually noticeably better than YouTube's auto-captions, especially on accents and on the multi-language case. It is not a human transcript.

Frequently asked questions

Why is YouTube auto-translate not working?

Almost always because the video has no caption track for it to translate. Auto-translate is a translation layer on top of existing captions — creator-uploaded or auto-generated — so if speech recognition never ran, there is nothing to translate and the option is missing rather than broken. YouTube lists six reasons captions may not generate: audio still processing, an unsupported spoken language, the video being too long, poor sound quality, a long silence at the start, and overlapping speakers or multiple languages at once.

Why is there no Auto-translate option in my subtitle menu?

Because the menu is accurately reporting an empty input. Auto-translate only appears when a caption track exists, so a video without captions — or one whose creator turned captions off — shows the subtitle menu without the auto-translate submenu. Clearing your cache or reinstalling the browser cannot add a track that was never made.

Does YouTube auto-translate work in the mobile app?

Yes, but it's three levels deep and fails quietly. Tap the CC icon, then Captions, then Auto-translate, then your language. If the video has no caption track, the Auto-translate entry simply isn't there and the app gives no reason — which is why the same video can look "broken on mobile, fine on desktop" when the actual cause is the video.

Why can't I auto-translate into my language?

The list of target languages is long, so this is rarely the real problem — check that you're in the second-level Subtitles then Auto-translate menu rather than the first list. What is genuinely limited is the set of spoken languages YouTube can auto-caption in the first place; if the video's own language isn't supported, no track is generated and there is nothing to translate into anything.

Can I get subtitles on a YouTube video that has no captions at all?

Yes, but not from YouTube. A tool that transcribes the video's audio can produce a subtitle line where YouTube produced none, and then translate it. A free browser extension like Linglass does this in the player, and it covers the cases YouTube's own recognition gives up on, including unsupported languages and poor audio.

Why do YouTube's automatic captions fail on videos with two languages?

Because its speech recognition assumes one language per video, which YouTube states outright as a reason captions may not generate. A code-switching speaker either produces no captions or a transcript forced entirely into the dominant language. Transcribing in chunks and detecting the language of each chunk separately handles it — that's how Linglass approaches bilingual interviews and vlogs.

Quick recap

• Auto-translate translates existing captions. It never creates them, so a missing Auto-translate menu almost always means a missing caption track.
• YouTube names six reasons captions don't generate — unsupported spoken language, poor audio, length, opening silence, overlapping speakers or two languages, and processing delay. Only the last one is fixed by waiting, and none by clearing your cache.
• Auto-translate does work in the mobile apps, at CC → Captions → Auto-translate. It disappears without warning when there's no track, which is why it reads as a phone bug.
• Translated gibberish is a bad source transcription, not a translation problem. Translating it again won't help.
• A free extension can transcribe the audio itself and translate independently of YouTube's pairs — and show both lines at once, which auto-translate cannot do at all.

The setting isn't broken. It's being honest about having nothing to work with — and that's a gap you can fill from outside.