Requires internet access and ELEVENLABS_API_KEY. Use the direct API, SDK, or CLI; no connected plugin or browser OAuth is required. If credentials are missing, use API-key setup. Load a chosen .env explicitly when needed; saving it does not automatically configure the process environment.

ElevenLabs Dubbing

Dub audio or video into other languages while preserving the original speakers' voices. Create a project from a file or URL, review and edit the source transcript, add one or more target languages, refine translations per segment, and regenerate outputs.

Important: Use the Dubbing Projects API — elevenlabs.dubbing.project.* in the SDKs, or the /v1/dubbing/project REST endpoints. Do not use the legacy v1 dubbing surface (client.dubbing.create(), client.dubbing.get(), client.dubbing.audio.get(), or bare /v1/dubbing routes) — that is the older dubbing API, now under Legacy in the API reference.

Setup: See Installation Guide. The elevenlabs CLI and the SDKs read ELEVENLABS_API_KEY automatically; REST base URL is https://api.elevenlabs.io with your API key in the xi-api-key header.

Local output and remote cleanup

Default: retain outputs locally and remove this task's remote generations after saving them. This also applies to previews, retries, test clips and streamed output. The examples below show generation only; complete these cleanup steps before reporting success.

1. Capture response headers and returned resource IDs alongside the local output path. Finish the download or stream, then verify the actual audio/video decodes or the transcript parses and contains the expected result. A filename or nonzero size alone is insufficient.
2. After verification and any dependent calls finish, delete only remote resources positively identified as created by this task. Keep IDs needed for cleanup locally until deletion is confirmed. Do not delete on a failed local save, while a dependent generation still needs the resource, or based only on voice, prompt or recency. Never bulk-delete unrelated history or voice profiles.
3. Verify removal using the resource lookup or a fully paginated, appropriately filtered listing. An authentication error or missing item on just the first page is not proof. If cleanup fails, retry once for a transient failure, then report the remaining IDs and reason. Preserve local files.

Do not treat HTTP success with enable_logging=false as proof of zero retention. Our Creator-plan test accepted that parameter but still stored downloadable audio. Use it only where supported and verify the outcome. Report verified API removal, not guaranteed erasure from provider logs or backups. If deletion is unsupported or cannot be verified, report cleanup as incomplete.