How long does it take to read 1,000 words?

The answer, and the range it lives in

For 1,000 words: about four and a half minutes silently, six to eight minutes read aloud, and under two minutes for someone scanning to find one specific thing. Those three numbers describe three different activities that all get called reading.

The useful form of the answer is a range with its assumption attached — four to five minutes at 200 to 250 words per minute. Quoting 4:27 implies a precision the underlying rate has never had, and the rate is the whole estimate.

For scale, 1,000 words is roughly two single-spaced pages in a standard 12-point serif face, or about four pages double-spaced. It is a long blog post, a short book chapter, or the introduction and methods of a student paper.

Reading time by word count

Three paces cover most readers of general prose, and they are the three the calculator on this site offers: 130 words per minute for careful or technical reading, 200 for ordinary prose, and 280 for fast reading of familiar material. Skimming proper is faster still, and sits above the top of this table. Times are minutes and seconds.

Silent reading, reading aloud and skimming are three speeds

Silent reading is the quickest of the three because nothing has to be pronounced. The eye runs ahead, passes over short function words without fixing on them, and jumps back only when a sentence refuses to resolve. Those backward jumps are where careful readers spend their extra minutes.

Reading aloud is limited by the mouth rather than the eye, so it lands where speech lands — commonly 130 to 160 words per minute. That puts 1,000 words at six to eight minutes spoken. It is why a piece that reads in four minutes turns into a seven-minute recording, and why podcast scripts feel so much shorter on the page than they sound.

Skimming is not reading done faster; it is a different task with a different goal. The skimmer wants a name, a number or the one paragraph that matters, and leaves most of the page unread on purpose. Sustained rates much above 400 words per minute almost always mean skimming, and recall of detail falls as the rate climbs. It is the right tool for triage and the wrong one for an argument you have to follow.

What makes the same 1,000 words take longer

Word count is usually the only input an estimator has, and it is the weakest of the factors that actually decide the time.

• Unfamiliar vocabulary. Contract clauses, a methods section, a medical letter — each unresolved term stalls the sentence it sits in. A competent reader can drop to 100 to 150 words per minute on material like this without any loss of skill.
• Reading in a second language. Expect a real slowdown even at high fluency, and a further one on idiom, humour and anything culturally specific. This is the single largest factor for most international audiences.
• Small screens. A phone shows fewer words at once and demands constant scrolling. Neither cost shows up in the word count, and both grow with the length of the piece.
• Poor typography. Lines running far past about 75 characters, cramped line spacing, weak contrast and very small type all raise the chance of losing your place and re-reading the line you just finished.
• Dense layout. Unbroken walls of text with no subheadings give the eye nowhere to rest. Readers slow down, and some of them stop.
• Purpose. Reading to remember is slower than reading for the gist, and proofreading is slower than both — which is why your own draft always takes longer to get through than it should.

Why two sites label the same article differently

Publishing platforms hardcode a words-per-minute rate, and they do not agree on which one. Figures anywhere from 200 to 275 are in use. That alone is enough to turn a 1,000-word post into a four-minute read on one site and a five-minute read on another, and to spread a 5,000-word feature across eighteen to twenty-five minutes.

The rest of the disagreement is structural. Some estimators count the words inside code blocks; others strip them out first. Some add a fixed allowance for every image, some ignore images completely. Some round to the nearest minute, some always round up, and a few round down — which is how a sixty-word note ends up advertised as a zero-minute read.

None of those choices is indefensible by itself. They are simply never stated, so two careful tools can report different labels for identical text without either of them being broken. If a number surprises you, compare the word counts first: when those match, the gap is entirely in the assumed rate.

What a word count cannot see

A word count measures words. Everything else on the page is invisible to it, and a fair amount of the reader's time goes to things that are not words at all.

A diagram that carries part of the argument is not glanced at, it is studied; twenty to thirty seconds each is unremarkable. A table gets read down one column, then across a row, then read again. Code is taken line by line and often mentally executed, which is far slower than prose. Footnotes break the thread twice — once leaving the sentence, once finding it again — and a page with many of them reads much longer than its text suggests.

The adjustment is manual and approximate, and that is fine. Count the elements that genuinely demand attention, allow something like fifteen seconds for each simple figure and a minute or more for each substantial table or code listing, then add that to the text estimate. An openly rough allowance is more honest than a precise-looking number that ignores half the page.

If you publish a reading time, publish the assumption

A reading-time label is a claim on somebody else's next ten minutes, which is a good reason to be conservative with it. A reader who finishes early feels quick. A reader still going at twice the advertised time feels lied to, and stops trusting every other label on the site.

• Say which pace the figure assumes, or quote the slow one and let readers beat it.
• Round up rather than down. Nobody has ever complained that a page was shorter than promised.
• Add your own allowance for figures, tables and code before publishing the number.
• Drop the rate for technical documentation or an audience reading in a second language. Somewhere near 130 to 150 words per minute is more honest than 250 for either.
• Re-check after a substantial edit. Reading times get set once and then quietly go stale as the article grows.

Getting the number for your own text

Paste the text into the reading time calculator, set a rate you can justify to the person reading, and treat the output as a range rather than a stopwatch reading. Change the rate to see how much of the estimate was the assumption rather than the writing.

The calculator measures the text you already wrote. It does not write, expand, shorten or rewrite anything — that judgement needs to know what you are trying to say, and it stays with you.