Reading Time Estimator — Words to Minutes at Any WPM

Words per minute is a claim about your reader, not a constant

A reading-time estimate looks like a fact and is actually a division sum with one guessed input. The same article at 180 words a minute takes about 55% longer than at 280 — so the honest way to present the number is with the assumption showing. That is why there are three presets rather than one hidden default, and why a fixed 250 wpm figure sits beside whatever you pick: two numbers make the range visible in a way one never can.

The controls are 180, 220 (the default) and 280, or any figure you type between 50 and 500. Under a minute the result switches to seconds so short pages do not all read "1 min".

Who reads slower, and why it is not a deficiency

The "average adult reads 200-250" note on the field is a population average, and averages hide the readers you most need to think about.

• Reading in a second language. Comprehension is unaffected; the parsing simply costs more time. On a site with substantial traffic from India, Nigeria or the Philippines this is not an edge case, it is a large share of the audience.
• Dense material. Legal, medical and technical prose is read slowly by experts too, because every clause carries weight and skimming loses the meaning.
• Reading to retain. Someone studying for an exam or checking a contract before signing reads at a fraction of skimming speed, and rereads.
• Reading on a phone. Shorter lines, more scrolling, and more interruptions.

An honest correction, since this sits in an SEO section

Reading time is a courtesy to the reader. It is not a ranking factor, and neither is the time anyone spends on the page. Google has said repeatedly that time on page and dwell time are not ranking signals, so anyone selling reading-time chips as an SEO tactic is mistaken.

The real reason to show one is decision-making. A reader landing on a long page is weighing whether to start now, save it, or leave. Telling them what it costs respects that choice, and a reader who chose to start is worth more than one who was surprised into scrolling.

Counting words in any script

The count is Unicode-aware, so Devanagari, Arabic, Cyrillic, Greek, Thai and Hangul text is counted properly rather than coming back as zero words and "0 min".

Chinese and Japanese need a caveat, because they are not written with spaces between words. Each Han character and each kana is counted as one unit, which is the convention word counters follow — but the words-per-minute presets are calibrated on English, and reading speed for those scripts is normally measured in characters per minute instead. Treat the figure as a character count and set your own rate accordingly.

When the estimate is wrong by design

The arithmetic assumes a reader moving in a straight line through prose. Content that breaks that assumption breaks the estimate: code samples that get studied rather than read, tables that get scanned and cross-referenced, and diagrams or charts where the reader stops reading entirely to look. A tutorial that is half code will take considerably longer than the number suggests, and there is no honest way for a word count to know that.

For a plain count of words, characters, sentences and paragraphs without the timing layer, use the word counter.