YouTube Comment Translate Button Missing? Here's Why and How to Fix It

The short answer: your Google account decides, not YouTube

YouTube shows the Translate link under a comment only when it thinks you cannot already read that language. That decision comes from the languages on your Google account — and Google adds languages there automatically, based on what you search for and watch. Once English (or any other language) lands in that list, comments in it stop offering translation, and nothing on the YouTube page tells you why.

The same setting explains the other half of the complaints: comments that translate into a language you never asked for. If your account carries three languages, the translation can land in the wrong one.

So the first fix is free, takes two minutes, and involves no downloads. Everything after that is a fallback for when the setting change does not bring the link back.

One disclosure before we go further: this is the Summarizer.tube blog, and we publish one of the extensions compared below. That is exactly why the free fix comes first and why our own tool's limits are spelled out rather than buried.

Fix 1: clear out the languages Google added for you

Open your Google Account → Personal info → General preferences for the web → Language. You will see a preferred language and, under it, Other languages.

Remove every language you do not actually read, using the trash icon. Then turn off Automatically add languages — this is the setting that quietly repopulates the list based on your searches. Without turning it off, the languages come back and the problem returns weeks later, which is why so many people report the fix "stopped working".

Reload YouTube afterwards. If the Translate link was hidden because the account claimed you read that language, it comes back here.

Fix 2: separate an account problem from a browser problem

If the setting change alone does nothing, find out which side is at fault before installing anything.

Open the same video in an incognito window, or on a second device signed into the same account. If the Translate link appears there, the problem is local: cached page data or another extension interfering. Clear the cache and disable extensions one at a time.

If the link is missing everywhere, the account or YouTube's own rollout is the cause, and the fallbacks below are the practical answer.

Fix 3: watch history counts as evidence too

People who watch a lot of content in one language report the Translate link disappearing for that language, and coming back after clearing watch history. It is the same logic as the account setting: YouTube infers comprehension from behaviour.

Before you clear history, weigh the cost. Watch history also drives your recommendations, and losing it degrades them for weeks. For most people the fallbacks in the next section are a smaller sacrifice than resetting what YouTube knows about their taste.

On phones, the options are narrower

In the YouTube mobile app the translate behaviour depends on both the device language and the account language, and it fails in its own ways — some language pairs simply never offer translation in the app.

Browser extensions are not an option on mobile: none of the tools compared below run in the YouTube app, ours included. On a phone, two things actually work — fixing the account languages as described above, or opening the same video in a mobile browser instead of the app, where the site behaves like the desktop version.

The fallbacks, with the limits each one has

If the native link is gone for good, here is every practical option and what it costs you.

Copy and paste into a translator. Zero setup, works everywhere including phones, and handles slang about as well as anything else. The cost is friction: fine for one comment, unusable for reading a thread.

The DeepL extension. Adds a *Translate with DeepL* button under comments. Two limits from DeepL's own documentation: the button only appears on comments whose language differs from your browser language, and it does not work on short comments or community posts. Comment sections are mostly short comments, so this bites more often than it sounds. Text is translated on DeepL's servers.

Google-Translate-based extensions. The largest ones in this category work by sending comment text to the Google Translate API — their own store listings say so. You get 100+ languages; you also send other people's conversations to a third-party server.

Whole-page browser translation. Chrome's built-in *Translate to English* converts the entire page, comments included. It is free and instant, but it also translates the interface, the video title and the sidebar, which makes the page harder to navigate than it was before.

On-device extensions. Chrome 138 and later ships a translator that runs locally, and extensions can use it. Nothing leaves the browser; the trade-off is a narrower language list and desktop-only support.

What our extension does — and where it stops

Ours falls in that last category, so here it is with the same honesty applied to everyone else.

It puts a Translate button back under each comment, in the position YouTube used to use. The translation appears beside the original, not instead of it, so you can check a name or a joke against the source text — press again and the translation hides. Turn on auto-translate and comments loaded while you scroll get translated as they appear. It works on short comments, which is where DeepL's button does not appear.

The translation runs inside Chrome's built-in translator, so comment text never leaves your browser. No account, no analytics, nothing stored.

Where it stops: desktop Chrome 138+ only, so no phones and no older browsers. 38 languages rather than 100+. The first time you use a new language pair, Chrome downloads a language pack once — after that it works offline. We traded breadth for keeping other people's conversations off servers, and that trade is not right for everyone.

If you are a creator answering foreign comments

Reading is only half the job — replying is the other half, and it has a different failure mode. Machine translation of your reply can land somewhere between formal and comical, and your audience sees the result under your own name.

Two habits help. Keep replies short and literal: idioms are what translation breaks first. And when a comment matters — a correction, a complaint, a business enquiry — translate it back into your own language before answering, so you are certain what you are replying to.

If a video draws comments in many languages, an extension that translates in place beats copying each one out, simply because you will actually do it.

Reading comments is one problem; finding them is another

The complaint that arrives right after "I cannot read these comments" is usually "I cannot find that one comment again". YouTube gives you a sort menu and no search box, so a comment sitting 400 rows down is only reachable by scrolling until it appears.

That is a different job, so we keep it in a different free extension: it loads the whole comment section including replies, searches it by word or author, filters to comments containing timestamps, and jumps the player when you click one. On a stream archive with thousands of comments it is the difference between finding the answer and giving up.

Neither tool needs the other. If translation is all you need, the translation extension is enough on its own.