The Reading Time Calculator estimates how long a piece of text takes to read at the speed you choose, and reports the word count and character counts (with and without spaces) alongside. Paste the text, set words per minute, and the result is given in minutes and seconds, the format content platforms use for their "x min read" labels.
How It Works
The text is split into words on whitespace, the count is divided by your words-per-minute rate, and the decimal remainder is converted to seconds. Character counts come from the raw text length and from the text with all whitespace removed, useful for platforms and forms that meter characters instead of words.
Parameters
| Input | Required | Meaning | |---|---|---| | Text | Yes | The passage to measure | | Words per minute | No | Reading speed, 1 to 2,000; defaults to 200 |
Worked example
A 1,500-word article at the default 200 WPM takes 7 minutes 30 seconds. Read aloud as a presentation script, the same text at a realistic speaking pace of 150 WPM takes exactly 10 minutes, which is the conversion speakers actually need: scripts should be budgeted at 130 to 160 spoken words per minute, not at silent-reading speed. A 10,000-word report chapter at 200 WPM is a 50-minute read, the kind of figure that decides whether it gets read at all.
Choosing the right WPM
Average adult silent reading of non-fiction runs roughly 200 to 250 WPM with full comprehension; skimming doubles or triples that while quietly dropping retention. Technical material, a second language, and dense legal or academic prose pull real speeds toward 125 to 175. Children read far slower by age. If you publish reading-time labels, use 200 to 225 for general audiences: labels that flatter the article ("3 min read" on a 1,200-word page) train readers to distrust every label on the site. For accessibility-sensitive content, offering the estimate at a slower selectable rate is the respectful choice, which is why the rate here is an input, not a constant.
Reading time versus speaking time
Writers reuse this calculation for video scripts, podcast outlines, speeches, and lesson plans, and the only adjustment is the rate: narration and presentation run 130 to 160 WPM, conversational audio slightly faster, and dramatic or technical delivery slower because pauses, emphasis, and screen changes consume time that is not words. A five-minute video segment therefore wants roughly 700 to 750 scripted words, not the 1,000 a silent-reading default suggests.
Limitations
The model assumes a constant pace and average word difficulty; it cannot see formatting, tables, code blocks (read far slower per word), or the re-reading that complex passages demand. Word counting is whitespace-based, so hyphenated compounds and numbers count as single words. Treat the result as a planning estimate with a comfortable margin either way, especially for timed presentations, where a live rehearsal remains the only true measurement.
Frequently Asked Questions
What WPM should I use for a blog audience?
200 to 225 is the common publishing convention for general non-fiction. If your audience is technical or international, 175 gives a more honest label.
Does the calculator count characters for social posts?
Yes, it reports characters with and without spaces. Social platforms count their own way (some count every character including spaces, others weight URLs and emoji), so use the figure as the draft measure and the platform's composer as the final one.
Why does my spoken delivery run longer than the estimate?
Because speaking is slower than silent reading and includes pauses, breaths, and slide changes. Recalculate at 140 to 150 WPM for presentation scripts and the estimate will track reality closely.