What reading speed does the estimate assume?

220 words per minute for silent reading and 130 words per minute for speaking aloud. Both are editable in the page, and the result recalculates immediately when you change them.

Why do different sites give different reading times for the same article?

Because they assume different rates, and many do not say which. This tool shows the rate it used and lets you change it, so the number can be reproduced or challenged.

Does the estimate account for headings, images or tables?

No. It is words divided by rate. Texts with many visual breaks read more slowly than the arithmetic suggests, which the page states rather than hiding.

Is speaking time the same as reading time?

No. Speaking is slower: the default is 130 words per minute against 220 for silent reading. A five-minute read becomes roughly eight minutes delivered aloud.

Is my text uploaded to calculate this?

No. The word count and the arithmetic both happen in your browser and nothing is transmitted or stored.

Reading Time Estimator

Your text

Paste or type text

Reading speed (words per minute)default 220Speaking speed (words per minute)default 130

Estimated time

Start typing above — the results update as you write.

Estimate how long a text takes to read silently or to deliver aloud, using your own reading and speaking rates rather than a hidden assumption.

What is Reading Time Estimator?

Reading time is arithmetic: the word count divided by a rate. The variables are how many words are in the text and how fast the reader moves, and the only honest way to present the result is to show both. The Reading Time Estimator does exactly that, and it lets you change the rates instead of locking you to a default.

The default silent reading rate is 220 words per minute, the figure most publishing style guides use for adult prose. The default speaking rate is 130 words per minute, which is a comfortable delivery pace for a script read aloud. Both are editable numbers in the page, and the result recalculates as you change them. If your audience is reading in a second language or the material is dense technical prose, entering 150 instead of 220 is more truthful than pretending the text is shorter.

The tool also shows the same text at three reference rates — 150, 220 and 300 words per minute — because the useful question is often a range rather than a point. A five-minute result at 220 can be over seven minutes at 150, and knowing the range is what stops an overrun during recording or presenting.

Reading time is used in places where the number is a promise. Estimated reading times on articles tell a visitor whether they have time to commit. Podcast and video scripts use speaking time to plan segments. Teachers and students use it to judge whether a passage fits a lesson. Conference organisers use it to keep a session inside its slot. In each case an error of a minute or two changes the decision, which is why the rate is visible and adjustable rather than buried.

Under the headline figure you get the inputs the estimate rests on: words, sentences, paragraphs and characters, all from the same counting engine used elsewhere in this domain. That means the number is reproducible: the reading time equals the words divided by the rate you chose, not a blend of estimates.

Two limits are worth stating. Silent reading speed varies enormously between people and between texts, so treat any single number as a convention rather than a measurement. And pauses — headings, figures, tables — are not modelled; a text with many of them takes longer than the arithmetic suggests. The tool says both on the page, because an estimate that oversells its precision is worse than no estimate. For counting the words themselves, the {{word-count-tool|Word Count Tool}} reports the same figure alongside frequency data, and the {{character-count-tool|Character Count Tool}} covers limits expressed in characters.

Two refinements make the estimate more useful in practice. A short note read by a slow reader is not the same as a dense technical paper read by a fast one, which is why the rate is editable rather than fixed: lower it for technical material, raise it for light prose, and the same word count produces a different and more honest answer. And when only part of a document is finished, pasting that part rather than the whole outline keeps the estimate tied to text that actually exists. Both habits keep the number a planning figure rather than a promise.

How to use Reading Time Estimator

Paste the text you want to time — an article, a script, a speech or a chapter.
Leave the rates at 220 and 130 words per minute, or enter your own if you know how fast you read or speak.
Read the headline reading time and the speaking time row beneath it.
Check the reference table to see how the same text behaves at a slow, average and fast reading pace.
Copy times to keep the estimate with the document.

When to use Reading Time Estimator vs related tools

Use the reading time estimator when time is the constraint: planning a script, promising a reading time on an article, or fitting a passage into a lesson or a session. When the constraint is a word or character limit, the Word Count Tool and Character Count Tool answer that question directly.

If you are planning a writing session rather than a reading session, the Writing Sprint Timer measures how many words you actually produce in a timed block, which is the writing-side counterpart to this estimate.

Privacy & Security

This tool runs entirely in your browser — no data ever leaves your device. There is no server round-trip, no upload, no logging, and no account required. Your input is processed locally using client-side JavaScript and is never stored, transmitted, or accessible to anyone else. When you close the tab, everything disappears.