Reading Time, Speaking Time, and the Pace People Actually Use

A time estimate helps a reader choose whether to start an article and helps a speaker fit a talk into the agenda. The arithmetic is simple: divide the word count by an assumed number of words per minute. The judgment lies in choosing a pace that matches the material and remembering that a script is not the entire presentation.

Paste a draft into the utilkit Word Counter to see its word count, estimated reading time, and other text signals. Treat the displayed time as a baseline. A dense policy document, a breezy newsletter, and a technical tutorial with code can contain the same number of words while demanding very different attention.

Estimate reading time with a range

Reading-speed research is a better starting point than an unexplained universal number. Marc Brysbaert’s review and meta-analysis of adult reading rates summarizes evidence across studies, while a page-level estimate still has to account for the audience and material. For planning, calculate more than one pace instead of promising a precise completion time.

• 200 words per minute: 6 minutes. A conservative planning baseline for denser prose.
• 238 words per minute: about 5 minutes. The research midpoint for adult English nonfiction.
• 300 words per minute: 4 minutes. The upper end of the study’s range for most adult English nonfiction readers, not an expectation for every page.

Those rates are scenarios, not reading grades or guarantees. Unfamiliar concepts, tables, footnotes, and instructions that must be followed will slow many readers; a familiar narrative may be faster. Label the assumption behind a displayed estimate so readers understand why their experience can differ.

Count meaningful non-prose work separately. A code sample might take seconds to scroll past or several minutes to understand and run. A chart may replace hundreds of explanatory words but still deserve viewing time. For tutorials, test the steps and report a completion estimate rather than relying only on word count.

Use a slower rate for speaking

Prepared speech is usually slower than silent reading because the audience cannot jump backward at will. The Pocket Guide to Public Speaking from the Parliament of South Africa uses roughly 120 to 150 words per minute as a typical range. At 135 words per minute, a 1,350-word script consumes about ten minutes before questions or demonstrations.

Slides, applause, audience responses, transitions, live demos, and intentional pauses all take time without adding words. Reserve time for them explicitly. If a session is 20 minutes and includes a five-minute demonstration plus three minutes for questions, the spoken portion has 12 minutes—not 20.

Calibrate with your own sample

Read or present a representative 300- to 500-word section aloud and record the elapsed time. Divide words by minutes to find your actual pace. Repeat with a section containing the difficult names, numbers, or transitions that are likely to slow you down. Your measured range is more useful than a generic average.

A practical workflow

1. Count the final words, excluding notes that will not be read.
2. Choose a baseline rate appropriate to reading or speaking.
3. Add time for visuals, tasks, pauses, demos, and questions.
4. Test a representative sample at your natural pace.
5. Rehearse the complete version and cut material if the schedule is tight.

Plan a presentation from its time budget

For a 20-minute talk, do not assign all 20 minutes to spoken words. Reserve time for the opening transition, slide changes, one demonstration, audience reaction, and a clean ending. If those elements need four minutes, the speaking budget is 16 minutes. At an observed pace of 125 words per minute, that supports about 2,000 spoken words—not the 2,500 that a simple 20-minute multiplication would suggest.

Mark the script at major time checkpoints and rehearse with the actual slides. If the five-minute marker consistently arrives halfway through a section that should be complete, revise that section before polishing individual sentences. Also time the slowest operational step: switching to a demo, inviting a participant, or waiting for a video. Those fixed events do not shrink when you speak faster.

For an article, the same principle helps set expectations. A 1,000-word tutorial with code, tables, or decisions may take longer than a 1,000-word narrative because readers pause to inspect or act. Use the displayed estimate as orientation, then organize the page so readers can skim headings and return to the exact step they need. Time estimates work best when paired with honest structure, not false precision.

Do not solve an overlong talk by racing through it. Cut supporting examples before you cut the pauses that make the main idea understandable. A good estimate is not about landing on an exact minute from a word count; it is about making the experience fit the time people actually have.