Reading Time Calculator

How the estimate is made

Both figures in the panel come from one division. The engine counts the words in your text and divides by a rate: 238 words per minute for silent reading, 150 for speech. Nothing else enters the calculation — not sentence length, not vocabulary, not paragraph structure — so two texts with the same word count always show the same times, whatever they say. Each word costs 0.25 seconds of reading and 0.4 seconds of speech, and the relationship is linear: double the words and both times double.

The two rates are the engine's only timing constants, and the same two are used wherever this site shows a time, so a text measured here matches the reading time on the word counter. The silent-reading rate is the average for adults reading non-fiction silently in Brysbaert's 2019 meta-analysis of reading-rate studies — a pooled estimate across many separate studies, used because it is a single defensible published figure, not because anyone reads at exactly that speed. The speaking rate is a common prepared-delivery pace. Both are population averages, and the rates behind them spread widely, so each result is an estimate of the middle of a range. The guide to reading time and words per minute goes through the rate, its source, and its limits in more depth than a tool page can; the guides index lists the rest.

The word count the division starts from follows the site's word convention: an unbroken run of letters, digits, apostrophes, and hyphens. "It's" and "state-of-the-art" are one word each, "2026" is a word, and "3.14" is two because the period splits it. That convention passes straight through to the time, and the figures example below shows what it does to a line full of numbers. The methodology page states every counting rule in full.

Planning to a time budget

The tool answers "how long will this take?", but while writing, the question usually runs the other way: "how many words fit the slot?" Invert the division and the answer is words = minutes × rate. A "3-minute read" is about 714 words, a 10-minute conference talk about 1,500 spoken words, and a 30-second radio spot roughly 75. Draft, paste, and trim until the live figure hits your slot — the counter updates as you cut. The table gives the budget for common slots in both directions.

Each budget was checked by building a text of exactly that many words and feeding it back through the engine, and every one displays exactly its slot: 714 words show "3 min", and 1,500 spoken words show "10 min". The round trip is exact only because each budget was built from the rate itself; a word count chosen at random usually lands between whole minutes and shows seconds as well. Two cautions apply to every row. A budget is a ceiling on words read or spoken continuously, and a talk is never continuous: a slide change, a demo, a question from the floor, a pause for a laugh — none of these are words, and all of them consume the slot, so subtract them before you look up the budget and script to what is left. And a reading budget describes a typical adult reading straight through; a reader who skims, or who stops to work through a table, is exactly the reader the average does not describe.

Worked examples, and where the estimate bends

Every number in this section was computed at build time by the engine that runs the panel above, on the text shown. Paste any of the examples in and the panel will agree.

A short notice, timed both ways

The engine finds 48 words. Divided by 238 and multiplied by sixty, that is 12.1 seconds of silent reading, rounded to 12 and displayed as "12 sec". Divided by 150 instead, it is 19.2 seconds aloud, displayed as "19 sec". The 3 sentences played no part; the word count alone did.

Article lengths

The same arithmetic at the lengths people usually ask about: 500 words read in 2 min 6 sec, 750 in 3 min 9 sec, 1,000 in 4 min 12 sec, and 1,500 in 6 min 18 sec. Spoken at 150 wpm, 750 words fills exactly 5 min — a handy anchor when a call for talks gives you a time slot instead of a word limit — while the 1,000-word article takes 6 min 40 sec to read aloud.

Sentences do not enter

The methodology page's example paragraph makes the point in the smallest possible space: "Dr. Smith arrived at 9 a.m. She left early." The engine reports 10 words and 3 sentences, one more than a reader would count, because the period after "Dr" triggers the sentence rule — a documented over-count. The time is untouched by it: 10 words come to 2.5 seconds of reading, displayed as "under 5 sec", and the phantom sentence changes nothing.

Figures and links inflate the count

A person reads one logistics line; the engine finds 30 words, because "1,250" splits at its comma into 2 tokens, "2.5" splits at its period into 2, and the address breaks at every colon, slash, and dot into a run of short tokens. Each fragment is charged the same 0.25 seconds as "jars" or "left". For ordinary prose the effect is negligible. For a changelog full of links, a table of prices, or a page of code, the word count — and so the minutes — runs ahead of what a reader experiences, and the honest correction is to round down mentally or to paste only the running text.

A longer passage

At 149 words the two figures separate clearly: 38 sec to read and 1 min to say, 22 seconds apart. The gap is not a property of this passage; it is the ratio of the two rates, and it opens at the same pace on every text.

How the display rounds

The division returns a fraction of a minute; the display turns it into a label by convention, in four steps. The total is first rounded to the nearest whole second. A total of zero — an empty box — shows "0 sec". The smallest total the display states as seconds is 5, on either rate; a positive total that rounds below it shows "under 5 sec" rather than a figure with false precision. Under a minute the label is seconds only; at an exact number of minutes it is minutes only; otherwise it is minutes and seconds. The table walks the boundaries with texts of exactly the stated length.

Three effects follow. First, a threshold: 17 words come to 4.29 seconds and read as "under 5 sec", while 18 words come to 4.54, round up, and read as "5 sec" — one added word moves the label. Speech crosses the same line earlier, because each spoken word is worth more seconds: 11 words show "under 5 sec" and 12 show "5 sec". Second, a stray second on long texts: 5,000 words come to 1260.504 seconds, which rounds to 1261 and displays as "21 min 1 sec", 1 second past 21 whole minutes. That second is the remainder of a division, not a measurement of anything. Third, a plateau: because neighbouring word counts round to the same second, a label covers a band of counts rather than a point. 1,000 words show "4 min 12 sec", and so does every count up to 1,001; the label first moves at 1,002 words, to "4 min 13 sec". While editing, a cut of one word may or may not move the panel; a cut of ten words is worth 2.5 seconds of reading and moves it every time.

Reading time versus speaking time

The panel shows two times because the engine carries two constants, and the choice between them is about the audience, not the text. Use the reading figure for anything a person will read to themselves — an article, a report, a newsletter, a page of documentation. Use the speaking figure for anything delivered aloud — a talk, a toast, a voiceover, a video script. Because both are linear in the same word count, their ratio is fixed: silent reading runs 1.59 times as fast as prepared speech, on every text. A draft written to a reading budget and then delivered as a speech runs long by that factor — a "3 min read" of 714 words becomes 4 min 46 sec at the podium.

Speech also has a way of running long that reading does not. The counter counts typed tokens, and figures are voiced in more words than they are typed: "1,250" is 2 tokens to the counter, but said aloud as "one thousand two hundred and fifty" it is 6 words, and a currency symbol is no token at all yet becomes a spoken word. A script dense with prices and dates therefore takes longer to deliver than its word count suggests, and the correction is to paste a spoken-out version or to time a read-through. Pauses cut the same way: slides, demos, and audience reaction add time the formula cannot see, which is why rehearsing with a timer still beats any calculator for a talk that matters. The guide to speaking time and speech length covers the spoken side in depth; the reading-time guide covers the silent side.

Limits worth knowing

The reader is not average. Someone skimming for a name, or working slowly through technical material, is exactly the reader a population average does not describe, and the estimate cannot know which one it is serving.

The text is not running prose. Everything pasted counts — headings, captions, bylines, footnotes, a reference list, the boilerplate at the bottom of an email. Trim to what a reader will actually read before estimating, or accept that the figure covers the whole document.

Difficulty is invisible. A dense passage and a plain one of equal length receive the same estimate, because sentence length and vocabulary never enter the division. If difficulty is what you are managing, the sentence counter's words-per-sentence average is the nearest gauge on this site; nothing from it feeds back into the timing.

Very short text collapses. Below 18 words the reading display is "under 5 sec" or "0 sec", and around a single sentence one added word moves the label. Reading time is a figure for passages and documents, not headlines.

Other tools disagree. Two tools differ for two reasons, sometimes both: a different rate, or a different counting rule at the margins — hyphenated compounds, numbers, URLs, headings. Differences of a few seconds on long texts are normal. Where an exact figure is contractual, the recipient's counter is the only one that matters.

Which way to round. The panel states the estimate to the second; what to do with it follows from the mechanism above. Round down when the text is dense with figures, addresses, or code, because tokenization charges reading time for fragments a reader takes in at a glance: the figures line is 30 tokens for 23 items, so its display runs 2 seconds over on a single line and proportionally further on a long changelog. Round down, too, when the paste carries headings, captions, or boilerplate nobody reads through. Round up when the reader must do something between the words — study a table, follow a step, check a figure against another page — because each costs time and adds no tokens. When the text will be read aloud, do not round at all: switch to the speaking figure, which exists for that case. The reading-time guide sets the rule out in full under when to round down, and when to round up.

Frequently asked questions

Estimates assume average pace and ordinary prose; your audience will vary. Everything is processed locally in your browser and never transmitted. See the methodology page.