Lovable Labs PlatformWhat is the Voiceover Script Timer?
| What it answers | Script runtime, TTS cost and studio time. |
|---|---|
| How the answer is produced | Spoken duration depends on word count and delivery pace, and pace varies more than most writers expect. |
| What you need to enter | Paste the final script including any words that will actually be read aloud. |
| Where it stops being reliable | Individual speakers vary by 20% or more from average pace. |
| Cost and sign-up | Free, runs in your browser, no account and no stored inputs. |
How is script timing calculated?
Spoken duration depends on word count and delivery pace, and pace varies more than most writers expect. Conversational narration runs around 150 words per minute, explainer and corporate voiceover around 130-140, audiobook narration around 150-160, and fast advertising reads can exceed 180.
The timer converts word count at your chosen pace, then adds pause allowance. Pauses are the reason scripts overrun: a natural breath between sentences, a beat before a key point, and the silence around visual transitions can add 10-15% to the raw reading time.
It reports total duration, duration per section, and how many words you need to cut or add to hit a target length exactly — which is the number that matters when the slot is fixed.
How do you use the Voiceover Script Timer?
- 1.Paste the final script including any words that will actually be read aloud.
- 2.Choose the pace that matches the delivery style, not the fastest one.
- 3.Add pause allowance for visual beats and transitions.
- 4.Read it aloud once with a stopwatch to calibrate the estimate against your own pace.
What can this tool not tell you?
- Individual speakers vary by 20% or more from average pace.
- Numbers, acronyms and technical terms take longer to say than their word count suggests.
- Music beds, sound effects and edit points are not included.
Why word-count timing alone always underestimates the real read?
A words-per-minute conversion treats speech as a continuous stream, but real delivery is punctuated by pauses that carry no words yet consume real time: the breath at the end of a sentence, the deliberate beat before a key statistic, and the silence a director leaves around a visual transition or a cut in the edit. None of these show up in a word count, which is why a script that times out perfectly on paper routinely runs long in the booth — the gap isn't a miscalculation, it's a category of time the raw formula doesn't account for.
Pace also isn't a single number per speaker; it shifts with content density. A sentence full of technical terms, acronyms or numbers takes measurably longer to say than a sentence with the same word count in plain conversational language, because each unfamiliar or multi-syllable term forces a slight deceleration that a generic 150-words-per-minute average doesn't capture. Scripts heavy with specifications or figures should be timed with a lower assumed pace than narrative scripts of the same length.
Because both pause allowance and individual speaker variation move the estimate in the same direction — longer than the raw calculation suggests — the practical use of a timing tool is as a first pass that gets corrected by an actual read-aloud test, not as a final number. Treating the tool's output as a ceiling to trim toward, then confirming with a stopwatch, catches the gap between calculated and actual duration before it becomes a studio-time problem.
Multi-speaker scripts introduce a timing variable the simple words-per-minute model doesn't capture at all: the gap between one speaker finishing and the next starting. In a two-host podcast intro or a dialogue-driven explainer, these handoff pauses — even short, natural ones — accumulate across a script the same way sentence-end pauses do, and a script with frequent speaker changes will run noticeably longer per word than a single-narrator script timed at the same words-per-minute rate. Scripts with more than one voice should budget a higher pause allowance than the standard 10-15%, closer to 20% once handoffs are frequent.
What do worked examples look like?
Fitting a script to a fixed 60-second ad slot
A draft script runs 165 words, timed at a 150 words-per-minute conversational pace — theoretically 66 seconds. Adding a 12% pause allowance for two natural breaths and a brand-mention beat pushes the estimate to roughly 74 seconds, over the slot. Cutting to 140 words brings it back under 60 seconds including pauses, which the raw word count alone wouldn't have flagged as necessary.
Timing a technical explainer with dense terminology
A software explainer script contains phrases like 'end-to-end encrypted API integration' and several version numbers. Timed at a standard 140 words-per-minute explainer pace, the estimate reads as 90 seconds, but a read-aloud test comes in closer to 100 seconds because the technical terms slow delivery. Recalculating at a reduced 125 words-per-minute pace for this script brings the estimate in line with the actual read.
Budgeting a two-host podcast open against a hard intro-music cutoff
A podcast's intro music fades out at exactly 45 seconds, and the dialogue needs to land its final line right on that mark. A single-narrator calculation at 150 words per minute suggests 112 words fits comfortably, but the actual script alternates between two hosts nine times in that stretch. Each handoff adds a small pause that a single-speaker estimate doesn't include, and a read-through comes in five seconds over. Trimming to around 95 words, and combining two of the shorter back-and-forth exchanges into single lines to reduce the handoff count, brings the segment back under the music cutoff.
What do people ask most about this tool?
How many words is a one-minute voiceover?
About 150 words at a natural conversational pace, or 130 for a measured explainer read.
How long is a 30-second ad script?
Typically 70-80 words, leaving room for a pause and the brand mention at the end.
Why does my recording run longer than the estimate?
Pauses, retakes and emphasis. Most scripts land 10-15% longer than raw word-count timing predicts.
Which related tools should you try next?
Written and reviewed by Jim Vernon, Editor, AI Intelligence International. Published by AI Answer Engine, a service of AI Intelligence International, and checked against our editorial standards.