Skip to content

Guide

Reading time vs speaking time for scripts

Why a script takes longer to say than to read, the words-per-minute figures that matter, and how to pace a talk to fit a fixed time slot.

6 min read · updated

A script that reads in six minutes will not be spoken in six minutes. Speaking is far slower than silent reading, and the gap is large enough to blow a talk past its slot or leave it ending awkwardly early. If you have ever finished a rehearsal on time in your head and then run over on stage, this is why. Knowing the two speeds, and which one applies to your situation, is the difference between fitting a slot and being cut off mid-conclusion.

The two speeds, and the gap between them

Silent reading runs at roughly 200 to 250 words per minute for an average adult reading general prose. Speaking aloud is much slower: a clear, well-paced delivery sits around 130 to 150 words per minute. That means the same script takes something like 40 to 60 per cent longer to say than to read silently — a 1,500-word script reads in about six or seven minutes but takes ten or eleven to deliver.

The gap exists because speaking is a physical act with constraints reading does not have. You breathe. You pause at the ends of sentences and between ideas. You slow down for emphasis and for anything the audience needs a moment to absorb. All of that time is real and none of it exists when you read silently, which is why estimating a talk from your reading speed always comes out short.

Reading TimeSet the pace to a speaking speed rather than a reading speed to see how long a script actually takes to deliver aloud.

Which speed to use

Match the words-per-minute figure to how the text will be consumed. For a blog post or an article, use a silent-reading pace, because that is what a reader does. For anything performed — a conference talk, a keynote, a podcast segment, a voiceover, a wedding speech — use a speaking pace. The single most common timing mistake is estimating a spoken piece at a reading speed and being surprised on the day.

  • Silent reading, general prose: about 200–250 words per minute.
  • Conversational speaking: about 130–150 words per minute.
  • Deliberate, formal delivery — a keynote or a solemn occasion: nearer 120 words per minute.
  • Fast, energetic delivery — an experienced presenter with simple material: up to 160, but rarely sustainable for long.

Your own pace is the figure that matters most, and it may not match the average. The way to find it is to record yourself reading a passage of known length at your natural delivery, then divide the words by the minutes. Once you know your real words-per-minute, every estimate afterward is far more accurate than one built on a generic average.

Pacing to a fixed slot

The usual constraint is a slot: you have twenty minutes, or five, or an hour. Working backwards from the time to a word budget is straightforward once you have a pace. At 140 words per minute, a twenty-minute slot is about 2,800 words — but do not fill the whole slot. Leave a margin for the things that eat time live: a slow start, questions, a demo that lags, a laugh you pause for, the fact that nerves usually speed people up but occasions can slow them down.

A sensible target is to write for about 90 per cent of the slot. A twenty-minute talk is safer at eighteen minutes of script, leaving room to breathe and to recover if something runs long. Finishing a little early is professional; being told to wrap up while you still have three slides is not. It is far easier to stretch a talk that came in short than to compress one that ran long.

Word CounterCheck the script against the word budget your slot allows, so you can trim or expand before the room does it for you.

Writing to be spoken, not read

Timing is only half of it — a script also has to be sayable. Sentences that read fine on a page can be impossible to deliver in one breath, and long, clause-heavy sentences are the usual culprit. When you write for the ear, shorter sentences are not a stylistic preference but a practical necessity: they give you natural places to breathe and give the audience natural places to keep up.

Checking the sentence lengths in a script surfaces the ones that will trip you on stage. A sentence that runs 40 words with three subordinate clauses is a sentence you will stumble over and the audience will lose. Splitting the longest sentences makes a script both easier to deliver and easier to follow, and it does not change the timing much — the words are the same, just punctuated for breath.

Sentence CounterFind the longest sentences in a script and split the ones that are too long to say comfortably in a single breath.

A quick rehearsal check

Estimates get you close; a rehearsal confirms it. Read the script aloud at your real delivery pace, out loud rather than in your head, and time it. Compare that against the estimate and against your slot, then trim or expand where needed — cut a tangent, or add an example, rather than speeding up or slowing down unnaturally to fit. Adjusting the content is always better than adjusting your pace to hit a number, because a rushed or dragged delivery is worse than one that is slightly off time.

All of the estimating happens in your browser, so an unpublished keynote, a sensitive announcement, or a personal speech is not uploaded anywhere to be timed. You can paste the script, set your own pace, and get the figure without the text leaving the page.

Tools in this guide

Search NeatKit

Jump to a tool, a page, or change the theme.