Whether you're writing a blog post, preparing a presentation, setting a reading time estimate in a CMS, or just trying to judge whether a piece of content is the right length for its purpose — word count and reading time are two numbers you find yourself needing constantly, and looking up separately every time.
This guide puts all the reference numbers in one place, with the context needed to use them correctly rather than just citing a single average and leaving you to extrapolate.
How fast does the average person read?
The most commonly cited figure is 200 to 250 words per minute for average adult silent reading. This comes from decades of reading research and is a reliable baseline for most written content in standard prose format. But the number shifts meaningfully depending on what's being read and who's reading it.
Speed-reading techniques can push well above 400 words per minute, but comprehension typically drops sharply past 400 for most readers — so while someone might technically process 600 words per minute, they're not reading in any meaningful sense at that speed. The 200–250 figure is conservative and correct for content you want people to actually understand and retain.
Studies consistently find people read 20 to 30 percent slower on screens than on paper. If your audience is reading a physical book or printed document, adjust your estimates upward slightly. For websites and apps, the 200–250 figure already accounts for the screen factor.
Quick reference: reading time by word count
All figures calculated at 200–250 words per minute. Reading aloud figures use 130 words per minute, which reflects a comfortable, clear speaking pace.
| Word count | Silent reading | Reading aloud | Typical use |
|---|---|---|---|
| 100 words | ~30 seconds | ~45 seconds | Short social post, brief intro paragraph |
| 200 words | ~1 minute | ~1.5 min | Email body, short description, one tight page |
| 300 words | ~1.5 min | ~2.5 min | Short blog intro, press release opening |
| 500 words | ~2–2.5 min | ~4 min | Short article, opinion piece, detailed email |
| 750 words | ~3–4 min | ~6 min | Medium blog post, newsletter feature |
| 1,000 words | ~4–5 min | ~8 min | Standard article, short how-to guide |
| 1,500 words | ~6–7.5 min | ~12 min | Solid blog post, in-depth explainer |
| 2,000 words | ~8–10 min | ~15 min | Long-form article, detailed guide |
| 2,500 words | ~10–12 min | ~19 min | Comprehensive guide, white paper section |
| 3,000 words | ~12–15 min | ~23 min | Full white paper, long-form feature |
| 5,000 words | ~20–25 min | ~38 min | Research report, e-book chapter |
| 10,000 words | ~40–50 min | ~77 min | Short e-book, full research paper |
Paste your text to get an instant word count, character count, and reading time estimate.
Open Word CounterReading time by content format
The same word count can represent very different reading experiences depending on the format. A 1,500-word academic paper takes longer to read than a 1,500-word conversational blog post because the density of information per sentence is higher — technical vocabulary, qualified claims, and dense argument all slow comprehension without adding word count.
| Format | Typical word count | Reading time |
|---|---|---|
| Tweet / X post | 20–50 words | Under 15 seconds |
| LinkedIn post | 150–300 words | 1–1.5 min |
| Email (standard) | 200–500 words | 1–2.5 min |
| Blog post (short) | 600–1,000 words | 3–5 min |
| Blog post (standard) | 1,500–2,500 words | 6–12 min |
| Long-form guide | 2,500–5,000 words | 10–25 min |
| Novel chapter | 3,000–5,000 words | 12–25 min |
| Short story | 1,000–7,500 words | 4–37 min |
| Full novel | 70,000–100,000 words | 5–8 hours |
| Academic paper | 3,000–8,000 words | 20–60 min |
Speech and presentation word counts
Speaking and reading are not the same activity and don't use the same pace. Most people speak at a comfortable, clear pace between 120 and 150 words per minute. Faster than 160 words per minute starts to feel rushed to an audience; slower than 110 words per minute feels laboured.
| Speaking time | Word count (130 wpm) | Word count (150 wpm) | Typical context |
|---|---|---|---|
| 1 minute | ~130 words | ~150 words | Short pitch, elevator introduction |
| 2 minutes | ~260 words | ~300 words | Brief team update, lightning talk |
| 5 minutes | ~650 words | ~750 words | Conference lightning talk, class presentation |
| 10 minutes | ~1,300 words | ~1,500 words | Standard conference talk, detailed briefing |
| 15 minutes | ~1,950 words | ~2,250 words | TED talk (typical length), extended briefing |
| 20 minutes | ~2,600 words | ~3,000 words | Full conference presentation |
| 30 minutes | ~3,900 words | ~4,500 words | Keynote, class lecture, webinar |
| 60 minutes | ~7,800 words | ~9,000 words | Full hour talk, including natural pauses |
A written script rarely runs at exactly the pace you practised at home. Nerves, audience reaction, pauses for questions, slides that take longer to advance than expected — these all slow delivery. A 10-minute slot that requires 1,500 words of script at 150 wpm will run over if you get any interruptions at all. Writing to 1,300 words gives you natural room without feeling rushed.
How long should a blog post actually be?
Word count for blog content is the most asked and least useful question in content marketing, because the right length for a blog post is entirely dependent on what the post is trying to do and who it's for — not on a universal benchmark.
That said, some useful working ranges do exist:
- 300–600 words — appropriate for news-style announcements, short updates, or highly specific informational queries where the answer is genuinely that simple. Forcing more length here just adds filler.
- 1,000–1,500 words — the minimum for most informational how-to content to be genuinely useful. Enough room to cover a topic properly, give concrete examples, and answer the follow-up questions a reader is likely to have. A 4 to 7 minute read.
- 2,000–3,000 words — appropriate for guides, comparisons, and explainers covering a complex topic or competing for competitive search terms where the top results are already thorough.
- 3,000+ words — warranted for comprehensive reference content, pillar pages, or topics that genuinely require that depth to serve the reader fully. This length should never be chosen to look comprehensive rather than to actually be comprehensive.
Google does not use word count as a direct ranking signal — this has been confirmed repeatedly by Google's own search liaison team. What correlates with ranking is thorough coverage of the topic relative to what the top competing pages already cover. In practice, this sometimes means longer content outranks shorter content, but the relationship is through quality, not word count.
Reading time vs finishing time: the gap that matters
Reading time estimates assume the reader starts at the top and reads to the bottom at a consistent pace. Most people on the internet don't do this. Research on online reading behaviour consistently shows that fewer than 20 percent of article readers reach the end of a piece, and average time on page tends to be dramatically lower than the stated reading time would suggest.
This has practical implications for how you structure content rather than how long you make it. A 5-minute read that front-loads its most important information — key answer first, supporting context after — serves its reader better than a 5-minute read that builds to the conclusion at the end. The second structure assumes a finishing rate that rarely occurs in practice.
When you're checking the length of something you've written, count the words and use the table above to estimate reading time — then honestly assess whether a reader who only spends half that time with the piece still gets the main value out of it. If the answer is no, the structure might matter more than the length.