The reading time calculator above converts a word count into an estimated reading time at whichever speed matches the material and the reader. It also gives the spoken duration for scripts and voiceovers, the equivalent length at 1.5× audio playback, and a page estimate — four figures that answer most of the practical questions people have about how long a piece of writing is.
This tool estimates reading time from a word count. It does not measure your typing speed — for that, our typing speed test times you on real input and reports words per minute and accuracy. The two are often confused because both are expressed in words per minute, but one is an estimate from a length and the other is a measurement of a person. Arb Digital publishes both, and this page is the estimator.
What This Reading Time Calculator Does
Enter a word count, or paste the text and let the tool count it, then pick a reading speed. The headline figure is the silent reading time at that speed, adjusted for any images or charts in the piece. The supporting grid shows the word count, the time to read it aloud at a natural presentation pace, the same audio at 1.5× playback speed for anyone who listens fast, and a rough page count at 500 words per page.
The pasted text never leaves your browser. Word counting runs locally in JavaScript with no request to any server, which matters if the text is a draft you would rather not send anywhere. For a fuller breakdown of a document — characters, sentences, paragraphs, keyword frequency — the word counter covers that ground.
How to Use It
- Enter the word count if you already have it, or paste the text into the box and the count fills in automatically.
- Choose the reading speed that matches the material. Dense technical writing is read far slower than a news article, and picking 238 wpm for a specification document will understate the time badly.
- Enter the number of images or charts. Each adds about ten seconds, because a reader who stops to interpret a chart is not reading words during that time.
- Read the headline estimate for silent reading, and the aloud figure if you are writing a script or presentation.
- Press Calculate to refresh, or Reset to return to the defaults.
The Formula: Words Divided by Words Per Minute
The core calculation is reading time = word count ÷ reading speed. A 1,200-word article at 238 words per minute takes 1,200 ÷ 238 = 5.04 minutes, or about 5 minutes 3 seconds. Add three images at ten seconds each and the estimate becomes roughly 5 minutes 33 seconds, which rounds to 6 minutes for display purposes.
Reading it aloud is a different sum, because speaking is much slower than silent reading. At 130 words per minute — a comfortable presentation pace with natural pauses — the same 1,200 words takes 9.2 minutes. That gap between 5 minutes on screen and 9 minutes out loud is the single most useful thing this calculator tells anyone writing a script, and it is consistently underestimated.
The 1.5× audio figure divides the aloud time by 1.5, giving about 6.2 minutes. Podcast and audiobook listeners routinely play at that speed or faster, so it is a realistic figure for how long spoken content actually occupies a listener rather than how long it takes to record.
Where 238 Words Per Minute Comes From
The default speed is not a round number picked for convenience. A 2019 meta-analysis by Marc Brysbaert reviewed reading rate data across a large body of published studies and reported an average silent reading rate for English non-fiction of around 238 words per minute, with fiction read somewhat faster at roughly 260. The paper, published in the Journal of Memory and Language, is the reference most reading-time estimators should be using and few actually cite.
The distribution around that average is wide, which is the more important point. Individual reading speeds vary enormously, and the same person reads at very different rates depending on material, purpose and fatigue. Any single-number reading time is a central estimate for a population, not a prediction for one reader. Treat the output as a length indicator rather than a promise.
Why Material Type Changes the Answer So Much
Reading speed is not a property of the reader alone. It is a property of the reader, the text and the goal together. Someone reading a news article for gist moves quickly. The same person reading a legal clause they will be held to moves slowly and re-reads. Technical material with unfamiliar terminology, formulae or code samples slows reading dramatically, because the eye stops on each unfamiliar token.
Sentence structure matters too. Long sentences with multiple subordinate clauses force the reader to hold more in working memory, which slows comprehension even when every individual word is familiar. That is measurable with readability scoring — our Flesch reading ease calculator and readability checker both score sentence and word complexity, and a piece scoring as difficult should be estimated at a slower reading speed than the default.
The practical rule: pick the speed from the material, not from how fast you would like people to read. A specification, a contract or a technical tutorial belongs at 180 wpm or below. A blog post or newsletter belongs near the default.
Reading Time Labels on Articles
Publishing a "5 min read" label at the top of an article is common, and the reason it works is expectation-setting rather than accuracy. A reader deciding whether to start a piece wants to know if it is a two-minute skim or a twenty-minute commitment. Getting that within a minute or two is enough; precision to the second is meaningless given how much individual speeds vary.
Two conventions are worth following. Round up rather than down, because an estimate that undersells the length is more annoying than one that oversells it. And be consistent across a site, since readers calibrate against your labels rather than against an absolute standard. If your labels consistently run short, readers learn to distrust them.
Reading time also correlates loosely with content depth for SEO purposes, though not in the way that gets claimed. Length is not a ranking factor on its own. What matters is whether the piece answers the question, and a 600-word answer that does is better than a 3,000-word one that circles it. If you are auditing length across a site, the website word count tool gives you the raw numbers to work from.
Scripts, Presentations and Spoken Word
For anything that will be spoken, the aloud figure is the one to use, and it should be treated as a floor rather than an average. 130 words per minute assumes a steady delivery with natural pauses. Add questions from an audience, a slide transition, a demonstration, or any moment where you stop to let a point land, and real elapsed time runs longer still.
A useful planning heuristic: a ten-minute speaking slot fits roughly 1,300 words of script, and most people write far more than that and then rush. If you have a fixed slot, calculate backwards from the time to the word count rather than writing first and timing later. For the arithmetic on the slot itself, the time duration calculator handles start and end times.
Accessibility and Reading Speed
Not every reader reads at typical speeds, and content that assumes they do excludes people. Screen reader users, readers with dyslexia, and people reading in a second language all move through text differently, and time-limited content is a recognised accessibility barrier. The W3C guidance on reading level under WCAG addresses the related question of text complexity and recommends supplementary material where content requires advanced reading ability.
The practical implication for reading time labels is that they should never be used to impose a limit — a timed quiz, an auto-advancing carousel, a session that expires. Use them to inform, never to constrain.
Arb Digital plans and writes content around the question a reader actually came with, at whatever length answers it — not a word count picked to hit a target.
Content Marketing Services Talk to Arb DigitalCommon Mistakes to Avoid
- Using silent reading speed for a spoken script — speaking runs at roughly half the pace, so a script timed silently will overrun badly.
- Applying the default speed to technical material — dense or unfamiliar content is read far slower, and the default understates it substantially.
- Ignoring images, charts and code blocks — a reader stops to interpret them, and that time does not appear in any word count.
- Presenting the estimate as precise — individual reading speeds vary widely, so a figure to the second implies accuracy the method cannot support.
- Confusing reading speed with typing speed — both are quoted in words per minute, but one is estimated from a length and the other is measured from a person.
Related Free Tools From Arb Digital
Get an exact count with the word counter, convert to printed length with the words per page calculator, check how hard the text is with the readability checker, plan study sessions with the study time planner, and measure typing rather than reading with the typing speed test. Browse the full free online tools hub for more.
Frequently Asked Questions
At the average silent reading speed of 238 words per minute it takes about 4 minutes 12 seconds. At a careful technical reading pace of 180 words per minute it takes around 5 minutes 34 seconds, and read aloud at 130 words per minute it takes roughly 7 minutes 42 seconds.
A 2019 meta-analysis by Marc Brysbaert reported an average silent reading rate of about 238 words per minute for English non-fiction and around 260 for fiction. Individual variation around those averages is very wide.
Roughly 1,300 words at a natural speaking pace of 130 words per minute. Treat that as an upper bound, because pauses, questions and slide transitions all add real time that the word count does not capture.
Silent reading is limited by comprehension speed, while speaking is limited by articulation — the physical rate at which words can be formed clearly. Speaking also requires pauses for breath and emphasis that silent reading does not.
Yes. A reader who stops to interpret a chart is not reading words during that time, and the word count does not capture it. Around ten seconds per image is a reasonable allowance for most content.
It has no direct effect on rankings. Its value is in setting reader expectations, which can reduce the number of people who start a piece and leave immediately because it was longer than they expected.
No. This tool estimates how long text takes to read from its word count. A typing speed test measures how fast you personally type by timing you on real input. Both use words per minute, but they measure completely different things.
