Workflow guide · Research edition
YouTube Automatic Dubbing Controls and Review Checklist
Separate channel settings from per-video dub controls, use a language review card, and decide when to publish, hold or unpublish a YouTube automatic dub.
An automatic dub is another version of your programme. The practical question is who can approve that version, not simply whether a translated audio track exists. A creator who cannot review a language needs a different publication decision from a team with a named language reviewer.
YouTube enables automatic dubbing by default for eligible creators and documents a manual-review option. Our recommendation is to assign responsibility before letting another language version represent the channel. The worksheet here helps make that decision; it does not certify a translation or measure YouTube's accuracy.
Separate the three decisions
Keep a channel's generation setting, a particular dub's publication status and a viewer's audio preference in different rows. They answer different questions. A reviewer confirming one should not accidentally sign off the other two.
| Decision | Your operational question | Evidence to retain |
|---|---|---|
| Generate | Is automatic dubbing enabled for this channel? | Setting observed, date and responsible operator |
| Publish | Is this particular language version ready for viewers? | Video, language, reviewer and decision |
| Deliver | Can the intended viewer find the intended version? | A separate viewer-side check in the relevant context |
YouTube documents preferred languages and per-video audio switching for viewers. These are not instructions for setting a creator-controlled universal default audio track. Do not promise that every viewer will hear the version you happen to hear in your own session [1].
Use the control path for the device you actually have
The computer guide places channel controls under Studio Settings → Channel → Advanced settings, including the automatic-dubbing checkbox and manual review before publishing. The Android guide instead uses the Studio app's profile picture → Settings → Content → Automatic dubbing, with Publish manually. Per-video preview, transcript review and publication management require a computer. These are documented paths, not screenshots from an account we inspected. [1], [2].
Make the device part of the handoff. “Review it in Studio” is an incomplete assignment if the person has only a phone and the task requires desktop controls. Specify who opens the video, which language is being assessed and who is allowed to change its publication status.
If the control is absent, record that absence. Do not interpret a help article, a colleague's screenshot or a rollout announcement as proof of access for your channel. The current Languages page for a video is the place YouTube identifies for its available and experimental languages.
Choose a publication policy you can support
This is our editorial decision framework, not an extra YouTube eligibility rule:
| Situation | Sensible policy to evaluate | Reason |
|---|---|---|
| A named reviewer can assess the target language and the programme's terminology | Manual review, with a recorded decision per dub | Someone can connect the translated meaning to the original promise |
| The team cannot assess the target language | Hold that version until competent review is available, or turn the feature off | Generation is not approval |
| The programme depends on precise names, quantities, negation or nuanced humour | Require review of those passages in context | A small wording change can alter what the speaker appears to say |
| An already published version is disputed | Consider unpublishing while the issue is investigated | A reversible hold is different from permanent removal |
Avoid an automatic equation between “low stakes” and “no review needed”. Instead, name the consequence of a mistaken line. A wrong product name might make a tutorial impossible to follow; a reversed negative might invert a recommendation. This is a reason to inspect particular passages, not a claim that either error happened in a YouTube dub.
Copy one language review card per video
Use a separate card for each language. An approval of one dub is not a blanket approval of every generated track, and an updated original may require a new decision.
| Field | Reviewer fills in |
|---|---|
| Identity | Video URL, original language and target language |
| Responsibility | Language reviewer, subject reviewer and publishing operator |
| Reference | The original passage and its intended meaning |
| Names and quantities | Names, model numbers, dates, amounts and units that must remain correct |
| Meaning | Negation, conditions, exceptions and who is doing what |
| Context | Humour, quotations and wording that changes meaning when isolated |
| Decision | Publish, hold, investigate or unpublish; reason and date |
| Follow-up | Who checks a regenerated dub or a changed original |
Review the passage around a disputed word, not just a list of translated terms. A correct number can still be attached to the wrong object. Ask the reviewer to describe the instruction in their own words and compare that meaning with the original programme.
Where a language reviewer and a subject specialist are different people, give each a specific job. The specialist can identify the important model number or qualification; the language reviewer can judge whether the dub conveys it. Neither role should silently stand in for the other.
Distinguish correction from removal
YouTube says automatic dubs cannot be edited. Correcting an incorrectly set original-video language can regenerate them; this is not a general sentence-by-sentence repair tool. Unpublishing preserves a route to republishing, while deletion removes that route [1].
If the source-language setting is already correct, do not change it to an incorrect value just to force another attempt. Record the problem, keep the disputed version off publication when appropriate, and decide how to obtain a version that can actually be reviewed. Regeneration is a new review candidate, not evidence that the earlier concern disappeared.
Before deleting, distinguish an unwanted version from an unreviewed version. Our default operational preference for an unresolved concern is a reversible hold when that control fits the situation. This is workflow guidance; it does not change YouTube's controls or confer permission to alter somebody else's channel.
Know what the checklist cannot establish
YouTube lists exclusions including videos over 120 minutes and language or speech limitations. It warns about errors in generated dubs and identifies experimental lip sync for selected channels. The checklist cannot establish account eligibility, quality for a language, copyright clearance or a viewer's default track. Check those questions in their own context rather than treating a completed worksheet as approval by YouTube [1].
Live auto dubbing is a separate announcement: YouTube's September 23 post describes a pilot starting in early 2027. It is not the current ordinary-upload workflow above. Do not plan a live broadcast around an announced pilot [3].
If a translated clip will be cut from a longer programme, carry the language review record into the repurposing workflow. The fact that a passage was acceptable in the full video does not settle whether the shorter edit preserves its conditions and context.
Sources and verification
Primary references checked on October 22, 2026. Numbered citations in the text link to this list. Documentation and availability can change; verify the current controls before changing a production workflow.
Frequently asked questions
Can I edit an automatic dub sentence by sentence?
YouTube says automatic dubs cannot be edited. Correcting an incorrectly set source language can regenerate them; this is not a general repair method.
Does the checklist prove my channel has the feature?
No. Check the channel's actual controls and current eligibility; a help page is not an account inspection.