How quickly can an AI-dubbed video become reviewable?

Observed results

Median time to first playback ranged from 2.4 to 3.2 minutes across the source-length bands in the cohort. About four out of five completed jobs began playing within five minutes.

For sources between 20 and 60 minutes, full dubbing typically took about one third of the source runtime. Clips under two minutes often took longer than real time because fixed setup work—ingest, separation, transcription startup, and model startup—occupies a larger share of a short job.

• A longer source does not require waiting for the full runtime before review begins.
• First playback varied less by source length than full completion did.
• Very short clips are the least flattering case for a pipeline optimized around long-form streaming review.

How to interpret the numbers

The result supports a product-design claim: segment streaming can make a long job reviewable well before it is complete. It does not prove that WaveShift is faster than a named competitor, because this was not a controlled head-to-head test.

The 2.4–3.2 minute range is not a service-level objective. A large upload, poor network, unusually dense dialogue, a cold model, transient retries, or queue pressure can change an individual result. Completion-only sampling also excludes jobs that users cancelled or that failed, so the cohort should not be read as a reliability rate.

Limitations and what we would measure next

This analysis uses one operational snapshot. The mix of YouTube, Bilibili, direct-link, and uploaded sources was not held constant, and source-language attribution is often automatic rather than a clean experimental label. We therefore do not publish language-pair rankings from this cohort.

A stronger follow-up would use repeated snapshots, publish percentile bands, separate upload from URL ingestion, stratify by dialogue density and model cold starts, and report cancelled and failed jobs alongside completions. A competitor comparison would require matched source files, equivalent output settings, a declared review protocol, and repeated trials.

• No randomized assignment or matched competitor arm.
• No claim of universal processing time.
• No inference about audio quality from timing alone.
• No language-pair leaderboard from incomplete source-language labels.

Why publish an operational benchmark

Marketing claims become more useful when their denominator and failure modes are visible. Publishing the sample size, observation date, clock definition, and limitations lets a buyer decide whether the evidence resembles their own workload.

We will update the visible date and methods when the cohort is refreshed. Until then, this page should be cited as an August 4, 2026 operational observation—not as a timeless speed guarantee.