⚡Utilvy
2026-11-16

How Long Does It Take to Read 1,000 Words? (All Speeds)

At the average silent-reading speed of 238 words per minute, 1,000 words takes about 4 minutes and 12 seconds. Reading aloud drops to roughly 183 wpm, or about 5 minutes 28 seconds, while skimmers at 400 wpm finish in under 3. The full conversion table below covers every speed from proofreading to speed-reading.

Reading Time in Numbers: The Full Conversion Table

The most reliable benchmark comes from Marc Brysbaert's 2019 meta-analysis, which pooled data from 190 studies covering tens of thousands of readers. Silent reading averaged 238 wpm. Reading aloud averaged 183 wpm. Proofreading sits between the two at about 200 wpm, because you are checking as you go rather than absorbing the story.

Those three anchor points, plus a fast-reader and a skimming estimate, produce this table:

| Reading mode | Speed (wpm) | 500 words | 1,000 words | 2,000 words | 5,000 words | |---|---|---|---|---|---| | Reading aloud | 183 | 2 min 44 s | 5 min 28 s | 10 min 56 s | 27 min 19 s | | Proofreading | 200 | 2 min 30 s | 5 min 0 s | 10 min 0 s | 25 min 0 s | | Average silent reading | 238 | 2 min 6 s | 4 min 12 s | 8 min 24 s | 21 min 0 s | | Fast silent reading | 300 | 1 min 40 s | 3 min 20 s | 6 min 40 s | 16 min 40 s | | Skimming / speed reading | 400 | 1 min 15 s | 2 min 30 s | 5 min 0 s | 12 min 30 s |

Why do you see 200 wpm everywhere else? Many publishing platforms and plugins hardcode a single default. Medium's famous reading-time badge assumes 265 wpm; countless WordPress plugins assume 200 wpm. A fixed default is fine as a rough badge, but it silently overestimates time for fast readers and underestimates it for read-aloud content like scripts and speeches. That is exactly why a 1,000-word article might show "5 min read" on one site and "3 min read" on another.

How to Calculate Reading Time, Step by Step

Step 1: Count the actual words. Estimates based on paragraph count or character length are unreliable. Paste the text into a word counter and take the real number. For a typical blog post, prose words are what matter — headers and image captions add little.

Step 2: Pick the speed that matches the context. Use 238 wpm for someone silently reading an article, 183 wpm for anything read aloud, and about 150 wpm for a formal speech or presentation where the speaker pauses. For dense academic or legal text that people proofread, use 200 wpm.

Step 3: Divide words by speed. A 1,730-word blog post read silently: 1,730 ÷ 238 = 7.27 minutes.

Step 4: Convert the decimal into seconds. Multiply only the decimal part by 60: 0.27 × 60 ≈ 16 seconds. So the post takes about 7 minutes 16 seconds — round to "7 min read" for display.

Step 5: Add a buffer for non-prose elements. Headings, images, tables, and code blocks cost extra time that the word count does not capture. A common rule of thumb is to add about 12 seconds per image and 10 to 15 percent on top for posts with many tables or figures. A text-heavy 1,730-word article needs no buffer; an illustrated tutorial might deserve "8 min read" instead of 7.

Frequently Asked Questions

Does reading aloud use the same speed?

No. Aloud reading averages 183 wpm versus 238 wpm silently — roughly 23 percent slower, because your mouth cannot keep up with your eyes. Formal speech runs slower still, around 130 to 150 wpm, since speakers pause for emphasis and let points land. This is why a 1,000-word script is a 5-minute casual read but a 7-to-8-minute speech. Always match the speed to the medium before quoting a duration.

How accurate are the reading-time badges on blogs?

They are directionally useful, nothing more. A badge assumes one fixed speed, applies it to raw word count, and ignores images, formatting, and the reader's actual ability. For an average reader on a text-heavy article, a 238 wpm estimate lands within a minute of reality. For image-heavy listicles or technical documentation with code, the badge can be off by 50 percent or more. Treat the badge as a courtesy estimate, not a measurement.

How do I measure my own reading speed?

Run a simple timed test. Choose a section of about 1,000 words you have not read, read it at your normal pace, and time yourself with a stopwatch. Divide the words by the minutes — for example, 1,000 words in 4 minutes equals 250 wpm. Repeat once and average the two runs, and resist the urge to skim, which inflates the number without real comprehension. If you want a quick low-effort version, read for exactly 60 seconds, count the lines you covered, multiply by the average words per line, and you have a decent one-minute estimate.

Make It Automatic

Reading-time math only works when the input is right: a solid word count, the correct speed for the medium, and one clean division. Before you attach an estimate to your next post, your newsletter, or your speech notes, paste the text into Utilvy's free Word Counter — it gives you the exact word and character totals in seconds, so your "7 min read" label is built on the real number instead of a guess.

Try these tools