Reading Time for a Performer vs a Silent Reader: The Same Script, Two Different Clocks
A writer prepping a piece for two very different outings — a blog post someone will read silently at their desk, and the same material adapted into a five-minute spoken-word set — is really solving two different timing problems that happen to share a word count. Treating them as one problem, using a single reading-speed assumption for both, is one of the most common ways a live performance runs badly over or under its slot.
Two readers, two clocks
A silent reader's eyes move at roughly 238 words per minute on average for adult English prose — a figure drawn from a widely cited 2019 meta-analysis of reading-speed research. Nothing about that pace involves breath, articulation, or being understood by anyone else; it's purely how fast a practiced eye can move down a page while comprehending what it's reading. A performer reading the same words aloud is doing something categorically different: producing sound, at a pace a listener's ear can actually follow, with room left over for emphasis and pause. That's why the read-aloud preset on the site's Reading Time Estimator sits at 150 words per minute — nowhere close to half of silent-reading speed, but a large, consistent gap that holds up across most spoken-word and performance contexts.
Worked example: a 900-word piece, four ways
Run a 900-word piece through all four of the estimator's presets and the spread is stark. Silently, at 238 wpm, it reads in about 3 minutes 47 seconds. Read aloud to an adult listener, at 150 wpm, it takes 6 minutes flat — 58% longer. Told as a children's story, deliberately slowed to 120 wpm for clarity, it takes 7 minutes 30 seconds. Narrated for an audiobook, at a professional 155 wpm, it lands at 5 minutes 48 seconds, close to the general read-aloud figure but not identical to it, because trained narrators pace slightly faster than an average adult reading aloud casually while still leaving room for character voices and emphasis.
For a performer booked into a five-minute slot, this table is the difference between walking on stage prepared and walking on stage guessing. A 900-word piece silently "reads short" at well under four minutes, which might tempt a performer into thinking they have room to add material. Read aloud at a natural performance pace, that same piece already fills the entire five-minute slot with nothing to spare — the estimator would have caught the mismatch before it became a problem in front of an audience.
Why the gap isn't a rounding error
It's tempting to treat the difference between silent and spoken pace as a small adjustment — knock ten or fifteen percent off the silent-reading estimate and call it close enough. The real gap is much larger than that, because reading aloud isn't reading silently with a soundtrack added; it's a different physical and communicative act with its own genuine time costs. Breath takes measurable time. A held pause before a reveal, timed deliberately rather than left to the length of a comma, takes real seconds that no punctuation mark accounts for. A distinct voice for a second character, even briefly, adds texture a silent reader's internal voice supplies instantly and for free. None of that shows up in a word count, which is exactly why estimating spoken length from a silent-reading pace consistently under-predicts — often by close to half.
Building your own pace into the estimate
The four presets are solid defaults, not a guarantee for any specific performer's actual delivery. A performer who tends to speak faster than average, or who plans a piece with minimal pausing, will genuinely run faster than 150 words per minute; one building in a lot of dramatic silence will run well under 100. The reliable fix is the same one that applies to any pacing estimate: time an actual read-through, at the pace and with the pauses you intend to use, and use that measured rate — not a generic preset — for any piece with a genuinely hard time limit, like a festival slot or a radio segment with a fixed clock to hit.
When silent-reading time is the number that actually matters
None of this means the silent-reading estimate is useless — it's exactly the right number for a piece that will only ever be read on a page or a screen, like a blog post or a printed program note, where a reader's own pace, not a performer's, sets the clock. The mistake isn't using the silent-reading figure; it's using it for material that's actually headed for a stage, a podcast mic, or a bedtime-story slot, where an entirely different clock is the one that counts. Matching the pace preset to the piece's actual destination, before doing any time math at all, is the single highest-leverage step in the whole process.
Quick reference: common lengths at each pace
A short table is worth keeping on hand for quick estimates without opening the tool every time. At 300 words — roughly a long paragraph or a short news brief — silent reading takes about 1 minute 15 seconds, read-aloud about 2 minutes. At 600 words, a typical short blog post, silent reading takes about 2 minutes 30 seconds, read-aloud about 4 minutes. At 1,200 words, roughly this article's length, silent reading takes about 5 minutes, read-aloud about 8 minutes. At 2,500 words — a substantial short story — silent reading takes a little over 10 minutes, read-aloud close to 17. The read-aloud figure is consistently 60 to 65% longer than the silent figure at every length, which is worth remembering as a rough rule of thumb even without running the exact numbers: whatever a piece's silent reading time is, a spoken delivery of the same material is probably going to run closer to double.
Why material difficulty moves the number too
Pace presets assume roughly average prose difficulty, and that assumption breaks down at both extremes. A passage dense with unfamiliar proper nouns — an invented fantasy world with several new character and place names in the first paragraph — slows both silent and spoken reading well below the preset figures, because a reader or listener has to work harder to parse and retain each new name the first few times it appears. Simple, punchy dialogue-heavy prose, by contrast, can genuinely run faster than the presets in both modes, since short sentences and familiar words require less processing per word. A performer estimating a passage introducing an unusually large cast of invented names is better served knocking 15 to 20% off the standard read-aloud preset for that section specifically, rather than applying one flat pace to a piece whose difficulty actually varies scene to scene.
A worked example for a classroom read-aloud
Teachers and librarians reading a picture book or short story aloud to a class face a version of this problem with an added wrinkle: reading aloud to a group of children calls for a noticeably slower pace than reading aloud to an adult, both because clarity matters more and because pausing for reactions, questions, and page turns (for a picture book) adds real time the estimator's word-count math doesn't capture on its own. Running a 1,000-word picture-book text through the children's-storytelling preset (120 wpm) gives a baseline of 8 minutes 20 seconds — and a realistic read-aloud session, once actual page turns and a few pauses for questions are added, commonly runs a third longer than that baseline. Budgeting a read-aloud slot using the raw estimate alone, with no allowance for those interruptions, is one of the most common ways a "quick story before nap time" runs well past its intended slot.