How many minutes is my script? Words-per-minute math for voiceover and podcasts

Every scriptwriter eventually learns this the expensive way: the script that "reads like five minutes" comes out of the recording booth at seven and a half. Silent reading speed and speaking speed are different gears — most people read silently at 200–250 words per minute but speak scripted material somewhere between 110 and 160 — and the gap between them is where videos blow past their target length, podcast segments overrun, and voice actors get handed scripts that can't possibly fit the slot they were written for.

The fix is to size the script in audio minutes before anyone records a take. The math is simple division — words ÷ words per minute — but the words-per-minute number you divide by is a genuine editorial decision, and the small additions around the reading (breaths, pauses, music) matter more than most people expect.

Picking the right words-per-minute

There is no single "correct" speaking rate; there are delivery styles, and each has a characteristic band:

• Slow and dramatic — around 110 WPM. Documentary narration, meditation and sleep content, solemn commercial reads, audiobook passages meant to land with weight. At this pace a 1,000-word script runs just over nine minutes.
• Standard scripted delivery — around 140 WPM. The workhorse rate for explainer videos, corporate narration, and most podcast scripts: brisk enough to hold attention, slow enough to enunciate for an audience that's half-listening. The same 1,000 words now run about seven minutes.
• Fast and energetic — around 160 WPM. YouTube essays, ad reads with a lot to say, upbeat product videos. This is close to natural excited conversation; your 1,000 words are down to about six and a quarter minutes.
• Auctioneer territory — 200 WPM and up. Legal disclaimers, comedy bits, genuine auction chant. Listeners can't sustain comprehension here for long, which is why this rate lives in short bursts.

Notice the spread: the same script varies by nearly fifty percent in runtime across these presets. That's why "how long is a 1,000-word script?" has no answer until you've decided how it will be delivered. The Script Read Time Calculator makes the choice explicit — paste the script (or just type a word count if you're still outlining), pick a pacing preset or set a custom WPM, and it returns the runtime as minutes and seconds.

The overhead nobody budgets: breaths, pauses, and music

Raw division assumes a robot that never inhales. Humans breathe, pause at paragraph breaks, and let important lines sit for a beat — and a good editor deliberately leaves some of that air in. Across a full script this padding reliably adds on the order of five percent to the runtime, which sounds negligible until you're producing a 30-minute episode and it quietly adds a minute and a half.

Fixed-length elements are even easier to forget because they're not in the script at all: the intro music, the outro card, the sponsor sting. If your show opens and closes with about twenty seconds of music and branding, that's twenty seconds of runtime that exists in every episode regardless of word count. The calculator models both — a breaths-and-pauses allowance applied as a percentage, and a flat intro/outro addition — so the number you see is the length of the finished audio, not just the raw read.

Working the math backwards

The more useful direction, once you're comfortable with the numbers, is backwards: start from the runtime you need and derive the word budget. Need a 60-second spot at standard delivery? That's about 140 words — minus your music sting, so realistically 90–110. Producing a ten-minute video essay at an energetic 160 WPM? You have roughly 1,500 words to spend, and knowing that before you write beats cutting a third of a finished draft after the table read.

This is also the honest way to scope client work. Voice actors price and schedule by finished audio minute; podcast editors book studio time by expected runtime. Handing over a script together with a defensible runtime estimate — "4,200 words at conversational pace with pauses, call it 32 minutes" — is the difference between a session that fits the booking and one that doesn't.

Short-form has hard ceilings

Word budgets bite hardest in short-form, where platform limits are absolute. A vertical short that must land under 30 seconds holds only about 60–70 spoken words at standard pace — a single tight paragraph. A 90-second explainer holds about 200. Scripts for these formats fail in the edit, not the write: everything sounds fine until the timeline shows 38 seconds and the platform cap is 30. Checking the script against the ceiling while it's still text is free; discovering the overrun after recording costs a reshoot or a painful speed-up.

Size it before you record it

None of this math is hard, which is exactly why it's worth doing every time: it's the cheapest quality gate in the entire production chain. Paste your next script into the Script Read Time / Voiceover Timer, pick the pacing that matches your delivery, toggle on the breath allowance and your intro/outro overhead, and read the runtime before you hit record. And if what you actually need is the silent reading time of a blog post or article rather than spoken audio, that's a different gear of the same math — the reading time estimator handles that side.