Calculate the estimated time needed to read any text based on its word count and reading speed.
|
| Calculate the estimated time needed to read any text based on its word count and reading speed. |
Reading Time Calculator
Paste your text and find out roughly how long it'll take someone to read it — or hear it read aloud.
Saw the "6 min read" tag under a Medium post once and got curious enough to actually time myself with the stopwatch on my phone. Felt a little ridiculous doing it, not going to lie. Finished in four minutes flat. So either I read faster than average, or their estimate runs a bit conservative on purpose — turns out it's both, kind of. Medium's formula assumes around 265 words a minute, already on the faster end for adult reading, and then they tack on a few extra seconds per image in the post too. Small detail. But it's what got me actually looking into how these numbers get calculated instead of just trusting the little badge the way everyone else seems to.
The math part is easy. The speed number underneath it? Not so much.
Reading time is just word count divided by speed, times sixty to land on seconds. That's it, that's the whole formula. The hard part is picking a speed that actually means something, because "how fast do people read" doesn't have one clean answer. Depends who's reading. Depends what they're reading. Depends, honestly, on how distracted they are at that exact second, phone buzzing in the background or whatever.
General adult silent reading, casual stuff like a blog post or a news article, tends to land somewhere between 200 and 250 words a minute. Get into denser material — legal writing, academic papers, anything stuffed with terms you have to stop and think about — and that number drops, sometimes down to 100 or 150 wpm, because people are actually pausing to process instead of gliding through. Skimming's the opposite extreme, easily 400, 500 words a minute or more, except at that speed you're not really reading anymore, you're just scanning for whatever looks relevant.
Why the same article takes different people wildly different amounts of time
Kids reading at a grade-school level go a lot slower, often 90 to 150 words a minute depending on the grade. Matters if you're writing for a younger audience and actually want your reading-time estimate to mean something for them instead of quietly assuming everyone reading is a fast adult.
Non-native speakers tend to read slower too when it's not their first language, sometimes a lot slower. Nothing to do with intelligence, obviously — it's just that decoding less familiar vocabulary and sentence patterns takes real mental effort a native speaker skips right past without noticing. Same person, same brain, reading their third language versus their first, and there's a real measurable gap.
People with dyslexia or other reading differences often read more slowly as well, and a single "average" number just doesn't capture that. If accessibility actually matters for whatever you're putting out there, treat any reading-time estimate — this one included — as a rough middle-ground guess, not gospel for every single person who'll land on the page.
Reading time and speaking time aren't the same thing, even though people mix them up
Silent reading beats speech every time because your eyes can jump ahead, double back, take in a whole chunk of text at once — your mouth just can't do that. Average speaking pace for clear, normal conversation sits around 130 to 150 words a minute. Noticeably slower than silent reading.
Comes up more than you'd think, honestly. Podcasters and video creators need to know how long a script actually runs once someone's saying it out loud, not how fast it'd read silently on a page — those two numbers drift apart pretty fast once a script gets long. Same deal for anyone prepping a talk with a hard time limit, timing themselves against a stopwatch instead of just guessing how long ten minutes of slides will take once they're actually up there talking through it live.
A few rough numbers if you want something to eyeball
- 500 words at 200 wpm — about 2 minutes 30 seconds
- 1,000 words at 200 wpm — about 5 minutes
- 1,500 words at 200 wpm — about 7 minutes 30 seconds
- 2,500 words at 200 wpm — about 12 minutes 30 seconds
- 1,000 words spoken aloud at 130 wpm — about 7 minutes 40 seconds
None of it's exact for any one specific reader. Planning numbers, basically — good for setting expectations, not for promising anyone a stopwatch-perfect match.
Why sites even bother showing this little number
Feels like a throwaway detail, doesn't it, but it actually changes how people behave. Knowing something's a 2-minute read versus a 20-minute one shifts whether someone even clicks in the first place, especially on a phone with six other tabs open and notifications going off every thirty seconds. A few platforms have found that showing an honest reading-time estimate correlates with people actually finishing what they started — probably because it sets an expectation upfront that a reader can mentally sign up for before diving in, instead of clicking into something that turns out way longer than they had patience for right then.
There's a flip side worth being honest about too. Padding a thin article with filler just to bump the reading-time number higher is a bad move. Readers notice fluff fast, and search engines have gotten decent at spotting content stretched way past what the topic actually needed. A tight, useful 3-minute read beats a bloated 8-minute one saying the same thing four different ways, every time.
A few things worth knowing before trusting the number blindly
Does it factor in images or video? Not here, no — this is a pure text-based estimate. Some big publishing platforms tack on a flat few seconds per image, on the assumption people pause to look at pictures, but that's a separate adjustment this particular tool skips.
Why does the article feel like it took longer than the estimate said? Dense, jargon-heavy writing, complicated sentences, anything that makes you go back and re-read a paragraph — all of that pushes real reading time well past a plain word-count estimate. This number assumes fairly casual, straightforward prose.
Not sure which speed to pick? 200 words a minute is a safe, reasonable default for general blog content aimed at a broad adult audience. Drop to a slower setting for technical writing, academic stuff, or content aimed at younger or non-native readers.
Is the speaking-time number good for anything besides podcasts? Sure — wedding speeches, conference talks, video voiceovers, even just figuring out how long a toast is going to run before people stop actually listening.
Never did figure out exactly why Medium's number ran ahead of my own real reading speed that day. Maybe I was reading slower than usual. Maybe their formula's just a little generous. Either way, I glance at reading-time badges with a bit less blind trust now, which feels about right for a number that's really just an educated guess wearing a very confident-looking outfit.