YouTube No Translation
Auto-translation behavior and lack of control
- Many users were unaware YouTube now auto-translates titles and even dubs audio.
- On desktop, audio tracks can sometimes be switched at runtime; on mobile and TV this is often impossible.
- Language is inferred from account, browser, device, location, etc., but there is no global “never translate” toggle.
- Behavior is inconsistent: some videos are translated, others not; some get “auto-dubbed” pills, others only translated titles.
Impact on multilingual and language-learning users
- Bilingual/multilingual users report severe frustration: they consume content in multiple languages and don’t want any of them auto-translated.
- Auto-translated titles make it hard to identify the original language, breaking use cases like:
- Seeking local content (e.g., Polish content about Poland).
- Using YouTube to learn or practice languages (e.g., wanting German originals, not English→German dubs).
- Several say translations are low quality, clickbait-y, or contextually wrong, forcing “reverse engineering” of titles.
User experience and product intent
- Many believe the core idea—opening cross-language content—is good but the UX is “botched” by lack of controls and poor signaling.
- Speculated drivers include: engagement metrics, “AI feature” pressure, and monolingual assumptions in product design.
- Some worry this discourages language learning and narrows exposure to other cultures.
Workarounds and alternative tools
- The discussed “YouTube No Translation” and similar “untranslate” extensions:
- Restore original titles and audio while leaving recommendations intact.
- For some, this makes foreign-language discovery much better than YouTube’s default.
- Users mention alternative/front-end clients (e.g., open-source apps) that let them choose language and subtitle behavior.
Wider ecosystem complaints
- Similar grievances are raised about Google Search, Reddit, and developer docs auto-translating by default.
- Overall sentiment: auto-translation should exist, but must be clearly indicated, opt-in or easily disabled, and respect multilingual users.