If your dub looks frozen, the most likely answer is that it's still working in the background. Dubs run through several stages in sequence and each takes time. This article helps you tell still working, waiting for you, and actually stuck apart — and what to do.
Does reloading help?
Sometimes the status just looks frozen because your browser has a stale view. A page refresh often shows the dub has already moved on, so reload once if the status seems stuck in a normal stage. But if you see one of the three error signals below, reloading won't change anything.
What happens during processing
A dub has two time-intensive phases — Dubbing (≈ 2× your video length) and, if enabled, Lip Sync afterwards (≈ 4× your video length). These are rough guidelines, not guarantees, and there's no countdown — watch the live status. Within Dubbing, the status bar moves through these stages in order:
Stage | What's happening |
Downloading | Your video is fetched (from URL or YouTube) or uploaded. |
Processing video | The video is prepared and the spoken audio is separated from the background. |
Transcribing | Speech is converted to text with timestamps. |
Assign Voices | (Only for Replace Voice mode with multiple speakers) Waits for you to assign a voice to each speaker. |
Voice cloning | The original speaker's voice is recreated. |
Speech syncing | Each translated line is synthesized, timed, and aligned. |
Rendering | The final video is assembled. |
As long as the stage keeps changing and you see no error signal, the dub is working — even if it's slow.
"Assign Voices" is not stuck — it's waiting for you
If your dub shows a yellow warning badge saying Assign Voices, it isn't frozen. Dubly detected multiple speakers and needs you to pick which voice belongs to which speaker.
Open the dub, pick a voice for each speaker, and click Confirm. Processing resumes immediately.
"Assign Voices" doesn't appear when I expect it. This step only applies to Replace Voice mode. With Original or Studio-Like, each speaker is recreated automatically.
The button isn't clickable. It's only active once the dub has finished transcription and moved into the Assign Voices state (yellow badge). While the dub is still processing, the button appears but is inactive.
The three signals that mean something is really wrong
A dub is only really stuck — and only then is action needed — if you see one of these:
Red "Input Error" / "Error" badge — the problem is your source file, and you can fix it yourself. Common causes: no audio track, no video track, no detectable speech, the upload didn't complete, or not enough minutes. There's no retry button — fix the source and create a new dub. See Input error.
"Processing… takes longer than expected" (or "Updating… takes longer than expected" after edits) — despite the wording, this is an internal error only our team can fix. → Contact support (below).
"Lip Sync failed" on the Lip-Sync card — the dubbed audio is ready; only the lip movements failed. See Lip-sync error.
There is no fixed time limit that decides whether a dub is stuck — ignore any "wait X minutes/hours" rule of thumb and go by these signals.
Contacting support
For the "takes longer than expected" case (an internal error), ask Dubby in the chat (bottom right) and include:
The dub link (copy from the address bar)
The stage shown on the tile
Roughly when you created the dub
A screenshot of the dub tile, if you have one
Our team can investigate and re-run the dub if needed. If it failed on our side, we'll restore the credits.
Credits on failed dubs
Credits are charged when the dub is created, before processing starts. Failed dubs aren't refunded automatically — if a dub fails for a reason outside your control, ask Dubby in the chat (bottom right) with the dub link and we'll review it.