Sometimes a dub doesn't finish. The good news: almost every error is one of three cases, and each has a clear signal on the dub and a clear next step.
Step 1 — Read the signal on the dub
The dub tile and the status panel tell you which case you're in. Note the exact wording — you'll need it if you contact support.
Step 2 — Match it to one of the three cases
1. Red "Input Error" / "Error" badge — your source file. The source can't be processed: no audio track, no video track, no detectable speech, the upload didn't complete, or not enough minutes. You can fix this yourself — there's no retry button, so correct the file/situation and create a new dub. See Input error.
2. "Processing… takes longer than expected" (or "Updating… takes longer than expected") — an internal error. Despite the wording, this isn't a slow dub; it's a processing error that only our team can fix. Don't keep waiting and don't start a duplicate — contact support (Step 3). More detail: Processing is taking longer than expected.
3. "Lip Sync failed" — only the lip movements. The dubbed audio is finished and watchable; only the on-screen mouth movements couldn't be generated. See Lip-sync error.
Note: If the dub finished but the audio sounds off, that's not an error — see My voiceover sounds inconsistent or distorted.
Reloading the page doesn't fix any of these three — it only helps when the status looked frozen in a normal stage.
Step 3 — Contact support (cases 2 and 3)
For an internal error or a lip-sync failure, ask Dubby in the chat (bottom right) and include:
The dub URL
The exact wording shown on the dub
A short description of what's in the video (for lip-sync issues, whether a face is clearly visible)
We can see internal details that aren't shown in the UI, so we can tell you what happened and re-run it if needed.
Important: Please don't re-trigger a failed dub or lip sync yourself — without changing anything, it almost always fails the same way.