Reading Time vs Speaking Time: How to Size a Talk From Your Script

You have a script, a time slot, and a nagging question: will this fit? The trap is estimating with reading time — the number a "5 min read" badge shows — when what you need is speaking time. The two differ by a wide margin, and guessing wrong means racing through your last slides or standing there with four empty minutes. This guide shows how to turn a word count into an honest estimate of talk length.

#TL;DR

• Reading time and speaking time are different numbers — don't confuse them.
• Silent reading is ~238 wpm; reading aloud drops to ~183 wpm.
• A rehearsed talk with pauses runs slower, around 120–140 wpm.
• Rule of thumb: divide word count by 130 for presentation minutes.
• Always rehearse aloud once — pauses and slides add real time.

#How long will my speech be?

The honest answer is that a word count gives you a starting estimate, not a stopwatch. But a good estimate is enough to plan a talk, and it beats the two common failure modes: writing a 3,000-word script for a 10-minute slot, or padding a 6-minute talk until it sags.

#The one formula you actually need

Take your word count and divide by your speaking rate in words per minute:

minutes = words / speaking_rate_wpm

At a typical presentation pace of 130 words per minute, a 1,000-word script lands at about 7.7 minutes. That single division does most of the work. The only real decision is which rate to plug in, and that depends on the kind of talk — covered below.

A worked example: say you have a 6-minute lightning-talk slot. Multiply your slot by your rate — 6 minutes times 130 wpm — and you get a 780-word target. If your draft is 1,050 words, you are roughly four minutes over before you have said a word out loud, and you now know to cut about 270 words rather than discovering the overrun on stage. Working backward from the slot is often more useful than estimating forward from a finished draft.

#Why the "read time" badge misleads you

The "X min read" label on articles is built on silent reading speed, which is fast. Per Marc Brysbaert's 2019 meta-analysis of 190 studies, adults read English non-fiction silently at roughly 238 words per minute. If you size a talk with that number, you will under-estimate by 40% or more, because nobody delivers a speech at silent-reading speed. The mouth is the bottleneck, not the eyes.

#Why is speaking time longer than reading time?

Three things slow you down the moment you open your mouth, and none of them exist when you read silently.

#The mouth is slower than the eye

Your eyes can jump across a line and skip filler words. Your articulators — tongue, lips, jaw — cannot. The same meta-analysis that puts silent reading near 238 wpm puts reading aloud at about 183 wpm. That is the cost of physically producing every syllable, and it is before you add any of a talk's deliberate slowness.

#Pauses are a feature, not lost time

A good talk breathes. You pause after a key point so it lands, you pause before a punchline, you pause when a slide changes. Those pauses are where meaning gets absorbed, so you should never optimise them away — but they do lower your effective rate. This is why a rehearsed presentation runs slower than plain reading aloud, often around 120–140 wpm.

The effect compounds over a long talk. A single two-second pause is nothing, but a 20-minute talk with a deliberate pause every couple of sentences can easily give up two or three minutes to silence alone. That is time you planned for on purpose, which is exactly why sizing a script by silent-reading speed leaves you stranded: it counts zero seconds for the pauses that make the talk work.

#Slides, demos, and applause

Every slide transition, live demo, prop, or burst of laughter stops your word delivery cold. Andrew Dlugan's analysis of nine TED talks found an average of 163 wpm, but those are tightly rehearsed talks with minimal dead air. Add a Q&A pause or a demo that hangs for ten seconds and your real-world rate falls further. Budget for it.

#How many words per minute do people speak?

There is no single number, but the ranges are well established and stable. According to the National Center for Voice and Speech, conversational English for a US adult sits around 150 words per minute. Formal delivery is slower.

#Speaking rates by situation

Pick the row that matches your talk rather than a global average:

The VirtualSpeech speaking-rate breakdown lands in the same territory: formal presentations run slower than casual conversation because the stakes, and the pauses, are higher.

#How many minutes is a 1,000-word speech?

Here is the same word count converted three ways, so you can see how much the "which rate?" choice matters. Minutes are rounded to one decimal.

Silent read uses 238 wpm, read aloud 183 wpm, and presented 130 wpm. Notice that a 2,000-word script is an 8-minute read but a 15-minute talk — nearly double.

#When to speak faster or slower

A few adjustments to your base rate:

• Dense or technical content → slow down toward 120 wpm so ideas land.
• Storytelling or emotional beats → slow further, 100–120 wpm, with longer pauses.
• Familiar, high-energy material → you can push toward 160 wpm without losing people.
• Non-native audience → drop 10–20 wpm and enunciate; comprehension beats coverage.

Below roughly 100 wpm a talk drags; above about 180 wpm comprehension starts to fall off. Anywhere in the 130–160 band is safe for most rooms.

#How to estimate talk length from a script

Turn the theory into a repeatable checklist you can run on any draft.

#Step 1: Get an accurate word count

Paste your script into a live counter and read the number off. Do this before you trust any estimate, because a "roughly 1,200 words" guess can be off by hundreds. The iKit Word & Character Counter counts as you type, entirely in your browser, so a keynote or a sensitive script never leaves your machine. If you draft in Markdown, the iKit Markdown Editor gives you a live preview while you write and a clean word count to feed the formula.

#Step 2: Do the math in code

If you are scripting slides or a teleprompter, wire the estimate straight into your tooling:

// Estimate spoken minutes from a script
function speechMinutes(words, wpm = 130) {
  return words / wpm;
}

speechMinutes(1000);      // 7.69 minutes
speechMinutes(1000, 160); // 6.25 minutes

For a friendlier label, convert the decimal minutes into a clock string:

function toClock(minutes) {
  const total = Math.round(minutes * 60);
  const m = Math.floor(total / 60);
  const s = String(total % 60).padStart(2, "0");
  return `${m}:${s}`;
}

toClock(7.69); // "7:41"

#Step 3: Rehearse aloud and time it

No formula beats a stopwatch. Read the whole thing out loud at your real delivery pace — pauses, slide clicks, and all — and time it. The iKit Stopwatch & Timer runs in a browser tab with lap support, so you can mark each section and find the one that overruns. Compare the measured time to your estimate: if they are close, trust the formula for future edits; if the real time is much longer, your pauses are heavier than 130 wpm assumes, so recalibrate your personal rate and use it next time.

#References

• How many words do we read per minute? A review and meta-analysis of reading rate — Brysbaert (2019); source for silent-reading (~238 wpm) and reading-aloud (~183 wpm) rates.
• What is the Average Speaking Rate? — Andrew Dlugan's analysis of nine TED talks; 163 wpm average, 133–188 wpm range.
• National Center for Voice and Speech — cited for the ~150 wpm conversational rate for US English adults.
• Average Speaking Rate and Words per Minute — used for the by-situation rate breakdown (formal vs conversational vs podcast).

#Related on iKit

• Reading speed is the other half of this equation — the real 2026 numbers for silent reading, and why 300 wpm is a myth.
• Count the words before you estimate anything — how the live word and character counter works, entirely in your browser.
• Counting words breaks differently in Chinese, Japanese, and Korean — if your script is CJK, "words" per minute needs a different definition.
• Sizing text to a hard limit, SEO edition — the same count-then-fit discipline applied to titles and meta descriptions.
• Fitting a message into 280 characters — when the constraint is characters, not minutes.
• Why 160 characters is the line that costs you money in SMS — another place where an exact count changes the outcome.