How Long Does It Take to Read 1,000 Words?

A reader deciding whether to open your article gives that decision about a second, and a "4 min read" label is often the only input they have. Getting the number right matters more than it looks — and it is simple arithmetic once you pick the right words-per-minute figure for the material.

1,000 words takes about 4 minutes to read silently and about 7 minutes to read aloud. Everything below explains how to adjust that for your actual content. For the broader picture of how word counts, character counts, and text statistics fit together, see The Complete Guide to Counting Words and Characters.

The Only Formula You Need

minutes = word count ÷ words per minute

The arithmetic is trivial. Choosing the WPM constant is the entire skill.

Large-scale research on adult English readers puts silent reading of non-fiction at roughly 238 words per minute and fiction at about 260. Reading aloud is dramatically slower — around 183 WPM in controlled conditions, and 130 to 150 in real delivery once you add pauses and emphasis.

Publishing platforms almost all round downward. Medium uses 265 WPM, but most WordPress plugins default to 200, and 225 is a common compromise. Rounding down is deliberate: it is better to promise 8 minutes and deliver 6 than the reverse.

Reading Time Chart

Calculated at 240 WPM for silent reading, 150 WPM for reading aloud, and 130 WPM for dense technical material.

Words	Silent read	Read aloud	Technical / dense
100	25 sec	40 sec	45 sec
250	1 min	1 min 40 sec	2 min
500	2 min	3 min 20 sec	4 min
750	3 min	5 min	6 min
1,000	4 min	6 min 40 sec	8 min
1,500	6 min	10 min	11 min 30 sec
2,000	8 min	13 min 20 sec	15 min
3,000	12 min	20 min	23 min
5,000	21 min	33 min	38 min
10,000	42 min	67 min	77 min
50,000 (short novel)	3 hr 30 min	5 hr 33 min	—
90,000 (novel)	6 hr 15 min	10 hr	—

Working backwards is just as common — you have a duration and need a length:

Target duration	Words to write (spoken)	Words to write (silent read)
30-second video script	~70	~120
1-minute pitch	~140	~240
3-minute talk	~420	~720
5-minute speech	~730	~1,200
10-minute presentation	~1,450	~2,400
20-minute conference talk	~2,900	~4,800
45-minute keynote	~6,500	—

The spoken column is the one that matters for anything performed. A speaker who writes a 20-minute talk using a silent-reading estimate arrives with 4,800 words and runs 13 minutes over.

Adjusting for What You Actually Wrote

Three factors move the real number away from the chart.

Sentence and word complexity. A page of short declarative sentences reads faster than a page of subordinate clauses at the same word count. This is measurable: the same inputs that drive readability scoring — average sentence length and syllables per word — are the best available proxy for reading speed. If your text scores at a college reading level, shade your estimate 20 to 30 percent slower. Understanding Readability Scores: Flesch-Kincaid Explained covers how to get that number.

Non-prose elements. Code blocks, tables, equations, and data figures break the WPM model completely. Readers either skip them entirely — costing zero seconds — or study them for far longer than their word count implies. A common convention for images is to add 12 seconds for the first, 11 for the second, decreasing to a floor of 3 seconds each. For code blocks, counting them at roughly half speed is a reasonable adjustment.

Reading purpose. Skimming for a specific fact runs at 400 to 700 WPM with comprehension dropping accordingly. Studying for retention runs at 100 to 200. Reference documentation is almost never read linearly, which makes a reading-time label on an API reference close to meaningless.

Where the Estimate Earns Its Keep

Reading time is not a precision instrument and does not need to be. It does three useful jobs.

Setting reader expectations. The difference between "2 min read" and "14 min read" tells someone whether this is a coffee-break item or something to bookmark. Accuracy to the minute is irrelevant; the order of magnitude is what communicates.

Timing spoken content. Here precision does matter, because a hard slot is a hard slot. Draft the script, run the word count, divide by 140, and then rehearse aloud with a timer — your personal rate may be 120 or 165, and knowing it turns every future script into a solved problem.

Diagnosing structure. A 25-minute estimate on something meant to be a quick update is a signal to split it. This is the same instinct as checking average sentence length before publishing.

Getting the Number

Paste your draft into the Reading Time Estimator and it returns the estimate directly, with the WPM assumption exposed so you can adjust it for technical material or spoken delivery rather than accepting a fixed constant.

If you would rather work from the raw count, the Word Counter gives you the number to divide, and the Readability Score (Flesch-Kincaid) tells you whether to use the fast lane or the slow one. All three run entirely in the browser, so an unpublished manuscript or an embargoed announcement never leaves your machine.

Rules of Thumb Worth Memorising

• 1,000 words ≈ 4 minutes silent, 7 minutes aloud
• A minute of speech ≈ 140 words
• A minute of silent reading ≈ 240 words
• Halve your speed for technical, legal, or code-heavy text
• Double or triple it for skimming

Two of those — 140 for speaking and 240 for reading — cover almost every situation you will meet. Everything else is a correction on top.