Automatic and editable dubbing may sound like two speeds of one product, but ElevenLabs currently documents separate production paths: Dubbing v2 is an automated alpha, while clip-level editing, regeneration and track export remain in the legacy Dubbing Studio, now in maintenance mode. The real decision is not new versus old, but where the production needs control.
Two paths imply two control models
ElevenLabs documents Dubbing v2 as an automated alpha path. Dubbing Studio provides clip-level editing, regeneration and track exports, but uses a legacy model in maintenance mode. A single 'supports dubbing' checkbox hides this difference.
The automatic route can quickly test language coverage and overall intelligibility. A final master that is accountable line by line needs confirmed tools for locating errors, replacing dialogue, preserving character voice and exporting the stems required for downstream mixing.
Automation saves first-pass operation, not all QC
Short drama is dialogue-dense and turn-heavy. A mistranslated name or relationship can repeat across dozens of episodes. Automatic dubbing can reduce transcription, translation and first-pass voicing work, but it does not create a glossary, character-voice bible or approval workflow.
A robust path uses the automated version to reveal the distribution of problems, then routes high-risk languages, characters and emotional scenes into editable work. Human time is concentrated where needed instead of assuming either full automation or complete line-by-line reconstruction.
Evaluation should record whether transcription, translation and pronunciation can be edited; whether one clip can be regenerated; whether source dialogue, music and effects remain separable; whether external mixing is possible; and how project data and voice rights are managed.
If a tool does not provide the revision rights the project requires, a fast first generation remains a preview path—not an approvable mastering path.
What remains unknown: This story establishes product paths from official documentation; it does not rank naturalness, emotion or error rates. Quality conclusions require blind tests with fixed assets, languages, characters and reviewers.