Skip to content
CalcTide logo
Writing & Utility

Reading Time Calculator

A 1,000-word blog post takes about 5 minutes to read at the default 200 words-per-minute pace. This reading time calculator estimates how long a piece of text takes to read by counting the words in your content and dividing that count by a words-per-minute (WPM) reading speed. Paste in a blog post draft, an email newsletter, a script, or any block of text, and the tool returns an estimated reading time in minutes and seconds along with the total word count. The default pace is 200 WPM, a cautious setting a little below the 238 WPM research average for adult silent reading of non-fiction, and you can raise or lower it to match a specific audience, a technical topic, or a script meant to be read aloud. It is a fast way to set reader expectations, plan content length, or check whether a draft fits a target reading window before publishing.

Writing & UtilityBy

Quick answer

Default reading speed is 200 words per minute, a cautious planning pace. A 2019 meta-analysis of 190 studies put average adult silent reading of non-fiction at 238 WPM, so the default leans slightly long.

What this tells you

  • •Default reading speed is 200 words per minute, a cautious planning pace. A 2019 meta-analysis of 190 studies put average adult silent reading of non-fiction at 238 WPM, so the default leans slightly long.
  • •You can adjust words-per-minute for slower readers, technical material, or fast skimmers.
  • •The tool counts words directly from the text you paste, splitting on whitespace, so formatting like extra line breaks does not change the count.
  • •Results show a rounded minutes value plus a minutes-and-seconds display for a more precise, reader-facing estimate.
  • •Reading time is a planning estimate based on word count and pace, not a measurement of how long any single reader will actually take.
  • •Useful for blog posts, newsletters, product descriptions, scripts, and any content where you want to communicate expected reading effort.

How to Use

  1. 1Paste or type your text into the text field. Full drafts, blog posts, emails, and scripts all work.
  2. 2Check the words-per-minute value. It defaults to 200, a cautious pace for adult silent reading of general content. Enter 238 if you want the research average for non-fiction.
  3. 3Adjust words-per-minute if your audience reads faster or slower, or if you are timing a script meant to be read aloud rather than read silently.
  4. 4Click Calculate to see the estimated reading time shown as minutes and seconds.
  5. 5Use the word count shown alongside the result to cross-check your draft against a target length for SEO, newsletters, or scripts.

How It Works

Formula

Reading minutes = word count ÷ words per minute

The tool counts the words in your input by splitting on whitespace, then divides that count by the words-per-minute value you set. For example, 1,450 words at 200 WPM equals 7.25 minutes. That raw value is rounded to two decimal places for the minutes figure shown alongside the result. Separately, the tool converts the raw minutes into a minutes-and-seconds display by multiplying the raw value by 60 and rounding up to the next whole second. Rounding up rather than down means the displayed time never understates how long the content is likely to take, which matters more for planning purposes than shaving off a stray second.

Calculation note: values are processed in the order shown above, using the current input units.

Worked Examples

Standard blog post at default pace

Word Count1000
W P M200
Result5m 0s

A 1,000-word article at the default 200 WPM pace takes exactly 5 minutes to read, since 1,000 divides evenly by 200 with no leftover seconds. This is a common benchmark for a standard-length blog post and a useful sanity check for the tool's default settings.

Long-form article with extra seconds

Word Count1450
W P M200
Result7m 15s

1,450 words divided by 200 WPM equals 7.25 minutes. Converting the fractional 0.25 minute into seconds (0.25 times 60) adds 15 seconds, giving a display of 7 minutes 15 seconds. This minutes-and-seconds format is more useful for a reader-facing estimate than a bare decimal like 7.25.

Technical content at a slower pace

Word Count3200
W P M150
Result21m 20s

Technical or unfamiliar material is usually read more slowly than general content, so this example lowers the pace to 150 WPM. A 3,200-word guide at that speed takes 21 minutes 20 seconds, noticeably longer than the same word count would take at the 200 WPM default.

Script timed for narration

Word Count900
W P M130
Result6m 56s

Scripts read aloud for video or podcast narration move slower than silent reading, so 130 WPM is a more realistic pace for this case. A 900-word script at that speed runs about 6 minutes 56 seconds, close to what a narrator would actually need during a recording.

Short product description at the research average pace

Word Count250
W P M238
Result1m 4s

At 238 WPM, the average adult silent reading rate for non-fiction in Brysbaert's 2019 meta-analysis, a 250-word product description takes about 1 minute 4 seconds to read. At the 200 WPM default the same text shows 1m 15s, so for short-form copy the choice of pace moves the estimate by only about 10 seconds.

Scenario: labeling a 1,840-word newsletter

Word Count1840
W P M200, then 238
Result9m 12s at 200 WPM, 7m 44s at 238 WPM

Lena edits a weekly newsletter for adult subscribers and prints a read-time label under each headline. This issue runs 1,840 words. At the 200 WPM default the tool returns 9m 12s, because 1,840 ÷ 200 = 9.2 minutes. At 238 WPM, the average silent reading rate for adult non-fiction in Brysbaert's 2019 meta-analysis, it returns 7m 44s, since 1,840 ÷ 238 = 7.73 minutes and the tool rounds 463.9 seconds up to 464. She labels the issue a 9-minute read so slower readers are not caught short. If she cuts a 240-word sidebar, the issue drops to 1,600 words and exactly 8m 0s at the default.

Reading time by word count at four reading speeds

What this calculator shows for ten common word counts. 183 WPM is the research average for reading aloud, 200 WPM is the tool's default, and 238 and 260 WPM are the research averages for adult silent reading of non-fiction and fiction.

Words183 WPM (aloud)200 WPM (default)238 WPM (silent non-fiction)260 WPM (silent fiction)
2501m 22s1m 15s1m 4s0m 58s
5002m 44s2m 30s2m 7s1m 56s
7504m 6s3m 45s3m 10s2m 54s
1,0005m 28s5m 0s4m 13s3m 51s
1,5008m 12s7m 30s6m 19s5m 47s
2,00010m 56s10m 0s8m 25s7m 42s
2,50013m 40s12m 30s10m 31s9m 37s
3,00016m 24s15m 0s12m 37s11m 33s
4,00021m 52s20m 0s16m 49s15m 24s
5,00027m 20s25m 0s21m 1s19m 14s

Computed with the formula above: word count ÷ WPM, converted to seconds and rounded up to the next whole second, in the tool's minutes-and-seconds format. The 238 and 260 WPM columns are Brysbaert's 2019 estimates of average adult silent reading speed in English for non-fiction and fiction, from 190 studies with 18,573 participants, and 183 WPM is the same paper's average for reading aloud, from 77 studies with 5,965 participants (Journal of Memory and Language, volume 109, article 104047). They are averages, so a real reader can land well above or below any column.

Where words-per-minute figures come from

Most reading time figures trace back to studies that time people reading a passage and divide the words by the minutes. The largest pooled estimate is Marc Brysbaert's 2019 meta-analysis in the Journal of Memory and Language, which combined 190 studies with 18,573 participants. It put the average adult silent reading rate in English at 238 WPM for non-fiction and 260 WPM for fiction, and found that the gap is predicted by word length, since non-fiction uses longer words. Both averages are lower than the figures often cited in scientific and popular writing, and the paper reviews why the older estimates ran high.

This calculator defaults to 200 WPM, slower than either average, and that is a deliberate lean toward caution. A 1,000-word article shows 5m 0s at the default and 4m 13s at 238 WPM, so the default label runs about 19 percent long for a typical adult reading non-fiction. The same paper reports lower rates for children, older adults, and people reading English as a second language, which is a reason to keep 200 or go lower for those audiences. Text packed with long technical terms is likely to land below the non-fiction average as well, since word length drives the fiction gap. The 150 WPM setting in this page's technical example is a planning choice, not a measured rate.

Reading aloud is slower. Brysbaert's average for oral reading is 183 WPM, from 77 studies with 5,965 participants. A script performed for a recording adds pauses for breath and emphasis that a timed reading task may not, so the narration example on this page uses 130 WPM as a cautious setting. For a number that fits your own voice, read one paragraph of the script aloud at your normal delivery, time it, and divide its words by the minutes.

Speed reading claims measure something else. A 2016 review by Rayner, Schotter, Masson, Potter and Treiman in Psychological Science in the Public Interest found a trade-off between speed and comprehension. Readers who move faster understand less, and the people who look like effective speed readers are mostly skilled skimmers who already know the topic. Paces far above the averages in the table describe skimming, not reading for full understanding, so they make poor defaults for a read-time label.

Screens matter less for speed than many people assume. A 2018 meta-analysis of 17 studies by Kong, Seo and Zhai in Computers & Education found no significant difference in reading speed between screen and paper, though comprehension was better on paper. Delgado and colleagues pooled 54 studies with 171,055 participants in Educational Research Review the same year and also found a paper advantage for comprehension, larger under time limits and for informational text. So a phone audience does not call for a lower WPM. A read-time label is not a target, though, and the screen disadvantage grew when readers were hurried.

Count words, sentences, and paragraphs with the word counter

Common mistakes

  • Using one fixed WPM setting for every audience. Technical documentation and casual blog posts do not read at the same pace, and a single default can mislead readers either way.
  • Counting words from heavily formatted text with headers, captions, and code blocks, which inflates the estimate compared to how a reader actually experiences flowing paragraphs.
  • Ignoring images, embedded video, and interactive elements, all of which add real time to a page that a pure word count cannot capture.
  • Treating the result as precise to the second instead of as a planning range for content length.
  • Forgetting to slow the pace down for scripts meant to be read aloud. Reading aloud averaged 183 WPM in Brysbaert's 2019 meta-analysis, against 238 for silent non-fiction, and a script with pauses for breath and emphasis can need a lower setting still.

Embed this calculator on your site

Paste this code where you want the calculator to appear. It is responsive, mobile-friendly, resizes automatically, and is free to use as long as the credit line stays in place.

<script src="https://calctide.com/embed.js" data-tool="reading-time-calculator" async></script> <p style="font-size:12px;margin:4px 0 0">Reading Time Calculator by <a href="https://calctide.com/writing-utility/reading-time-calculator/">CalcTide</a></p>

Preview the embed at /embed/reading-time-calculator/.

Frequently Asked Questions

It uses 200 WPM by default, a cautious planning pace a little below the 238 WPM average for adult silent reading of non-fiction reported in a 2019 meta-analysis. You can change the words-per-minute field to match a slower or faster audience, or a script meant to be read aloud.
No. It is a practical estimate based on word count and a chosen reading speed, not a measurement of how long any specific reader will take. Actual reading time varies with topic difficulty, formatting, and reader familiarity.
The tool counts the words in your text and divides that number by your chosen words-per-minute value. For example, 1,450 words at 200 WPM works out to 7.25 minutes, which the tool displays as 7 minutes 15 seconds.
Yes, but lower the words-per-minute value first. Reading aloud averaged 183 WPM in Brysbaert's 2019 meta-analysis, well under the silent reading average, and a performed script with pauses can run slower again. A setting of 130 to 160 WPM is a cautious planning range, and timing yourself on one paragraph gives a better number.
The word counter treats every whitespace-separated word the same way, including headings, captions, and labels. Adding more of that structural text increases the total word count even though readers often skim those parts faster than body paragraphs.
A range of 200 to 250 WPM works well for most general blog content aimed at adult readers. Drop closer to 150 WPM for technical or specialized topics where readers need to slow down to follow the material.
No. The calculation is based only on the word count of the text you enter. Pages with heavy image galleries, embedded video, or interactive charts will typically take longer to consume than the word-based estimate suggests.
Yes. It is useful for estimating content length and reader effort before publishing, so you can trim a draft that runs long or confirm a newsletter stays within a reasonable reading window for subscribers.
It estimates reading time calculator outputs using the visible inputs and formula assumptions on this page.

Explore More in Writing & Utility