Reading Aloud vs Reading Silently: Why Pace Changes Everything
Ask most people how fast they read, and they picture the pace of their eyes moving down a page — but that number has almost nothing to do with how long the same words take when spoken aloud. The gap between silent reading speed and spoken delivery speed is large, consistent, and worth understanding deliberately if you write or perform stories meant to be heard rather than only read.
The research behind the numbers
A widely cited 2019 meta-analysis of reading-speed studies, led by the psycholinguist Marc Brysbaert, put average adult silent-reading speed at roughly 238 words per minute for English prose — a figure pulled together from a large body of prior research rather than one single study. That's the pace of eyes moving across a page, unconstrained by breath, articulation, or the need to be understood by a listener.
Spoken delivery is a different physical act entirely, and it moves noticeably slower — commonly cited figures for comfortable read-aloud speech sit closer to 130–160 words per minute, and deliberately paced storytelling, especially for younger listeners or a performance built around suspense, often runs slower still. The gap isn't a rounding error; it's close to double, which means a piece that reads in five minutes silently can easily take eight or nine minutes read aloud with any real expression.
Where the extra time actually goes
The difference isn't just "talking is slower than reading" as an abstract fact — it's built out of specific, purposeful additions that silent reading skips entirely. Breath itself takes time. Emphasis on a key word takes time. A pause before a reveal, held a beat longer than grammar strictly requires, takes real seconds that no punctuation mark accounts for. A character voice, however brief, adds a texture that plain narration doesn't. None of this is inefficiency — it's the actual mechanism by which spoken delivery creates meaning and feeling that silent reading generates through different means entirely (font, punctuation, the reader's own internal voice).
This is precisely why a "dramatic, pause-heavy" storytelling pace can run as slow as 100 words per minute while still feeling brisk to a listener in the room — the pauses aren't dead air, they're doing narrative work that a faster pace would simply skip past.
Why this matters for writers
A piece written with silent reading in mind — dense, information-packed, syntactically complex — often performs badly out loud, not because the ideas are wrong but because the sentence structures don't leave room for a speaker to breathe, and a listener has no way to re-read a sentence that went by too fast to parse the first time. Writing meant to be read aloud generally benefits from shorter clauses, more repetition than would feel necessary on the page, and deliberate pauses built into the structure rather than left to chance.
The reverse is true too: prose written explicitly for a listening audience, when read silently instead, can feel oddly padded or repetitive — techniques that earn their keep in real time, spoken, can read as unnecessary when the eye can just glide past them. Matching the writing to the intended mode of consumption isn't a minor stylistic choice; it changes what "well-written" even means for that particular piece.
Practical pacing
The practical takeaway for anyone timing a piece for performance — a bedtime story, a spoken-word set, a podcast script — is to never estimate spoken length using a silent-reading word count. A script that reads in three minutes on the page needs a genuinely different estimate for how long it will fill a room, and that estimate depends heavily on how much pause, emphasis, and character work the delivery actually calls for. Timing a read-through out loud, at the pace you actually intend to use, is far more reliable than any word-count shortcut — though a pace-specific estimate is a solid starting point before that rehearsal.