Reading Time & Word Count Calculator
Paste text to calculate reading and speaking time, word count, and character count in real time with customizable reading speeds. 100% private in your browser.
How reading time is calculated
The formula is unglamorous: words ÷ reading speed. The interesting part is which speed you divide by. This tool uses 238 words per minute, the average adult silent-reading rate for non-fiction English established by Marc Brysbaert's 2019 meta-analysis, which pooled measurements from nearly 200 reading studies. It is the most defensible single number available — most "average person reads 200–250 wpm" claims trace back to far thinner evidence. Speaking time uses 150 wpm, a comfortable pace for presentations and voiceover; conversational speech runs faster, but scripts read aloud shouldn't.
Why the average hides a wide range
238 wpm describes typical adults reading typical prose for comprehension. Real reading speed swings with purpose and material: skimming for the gist can triple the rate, while working through a dense methods section or legal clause can halve it. Fiction reads a bit faster than non-fiction (around 260 wpm in the same meta-analysis) because narrative vocabulary is more predictable. Second-language readers, and anyone reading on a cramped phone screen in a moving train, come in below average. So a "12 min read" label is a planning estimate, not a promise.
Why article estimates vary between sites
Paste the same article here and into three publishing platforms and you may get four answers. Platforms disagree on the assumed speed (anywhere from 180 to 300 wpm), on what counts as a word (headings, captions, code blocks), and on adjustments for non-text content — Medium adds 12 seconds for the first image and scales down from there. None of them are wrong; they are just measuring slightly different things. This tool stays simple on purpose: whitespace-separated words, one well-sourced speed, no image fudge factors.
How to use the calculator
- Paste an article, essay, script, or chapter into the box — the four counters update live as you type. There is no button to press.
- Check the word count first. If it looks off, you probably pasted menus, captions, or code along with the prose; trim the text and the numbers recalculate instantly.
- Read the default estimate at 238 wpm, then adjust for your actual reader with the speed table below — the arithmetic is just words ÷ speed.
- Planning a course or a queue? Run each piece and add the minutes up; the rough planning speeds below are good enough for batching.
Reference: which reading speed to assume
| Reader or mode | Assumed speed | Where the number comes from |
|---|---|---|
| Adult silent reading, English non-fiction | 238 wpm | This tool's default; the 2019 Brysbaert meta-analysis cited above. |
| English fiction | around 260 wpm | Same meta-analysis; narrative vocabulary is more predictable. |
| Other read-time widgets | 180–300 wpm | The spread of published platform defaults — the reason estimates disagree between sites. |
| Narration and presentations | 150 wpm | This page's speaking timer; a comfortable read-aloud pace. |
| Studying dense material | roughly half the default (~120 wpm) | Rule-of-thumb planning figure, not a measured rate. |
| Skimming for the gist | up to about 3× the default | Rule-of-thumb planning figure; reading research measures comprehension-based reading. |
Worked example: an 1,800-word essay is 1,800 ÷ 238 ≈ 7.6 minutes of silent reading — the page renders it as “7 min 34 sec” — and 1,800 ÷ 150 = 12 minutes exactly if you read it aloud as a script.
What counts as a word
The counter splits your text at whitespace and counts every resulting chunk, so a URL, a code token, or a long hyphenated string each counts as one word. Anything you paste is measured: headings, captions, cookie banners. Publishing platforms often treat non-prose content differently, which is why their labels can differ even when they use a similar speed. The character count is raw length — spaces and line breaks included — so you can sanity-check the word count against it. For an article label, paste just the body prose.
Privacy and limits
Counting happens inside your browser as you type: no network request, no account, nothing stored, nothing left after you close the tab — paste unpublished drafts freely. Two honest limits. First, every result is an average-based estimate, not a stopwatch: real reading speed swings with material and purpose, as above. Second, word-based counting only makes sense for scripts that separate words with spaces. Chinese, Japanese, and Thai text will undercount words badly — the character count still works, but the minute estimate does not.
When the reading pile outgrows the reading time
Knowing an article is an 18-minute read is useful; having forty of them queued is the real problem. That's the case for a read-it-later workflow — covered in our roundup of thebest read-it-later apps and on theread-it-later page. Marqly's angle: AI summarizes every saved article, so you can triage the pile in minutes and spend your actual reading time on the pieces that deserve it.
Related tools and guides
Counting is one step in a larger reading workflow. Clean a messy page into plain prose with theHTML to Markdown converter before you time it; for video, the YouTube transcript viewer gets you the text behind it — at the two rates on this page, reading a transcript takes notably less time than listening to the same words aloud. Marqly's web highlighter keeps your annotations attached to the saved page, the YouTube summarizer condenses video before you commit to it, and thesecond-brain guide — alongside the longerhow to build a second brain walkthrough — covers what to do with everything you have time for.
Frequently asked questions
How is reading time calculated?
Word count divided by reading speed. This tool counts words by splitting on whitespace, then divides by 238 words per minute — the average adult silent-reading rate for non-fiction English found in a large 2019 meta-analysis of reading research. Speaking time uses 150 wpm, a comfortable presentation pace. Both are rounded to the nearest few seconds, not up to whole minutes.
Is 238 words per minute right for everyone?
No — it is an average, and the spread around it is wide. Skimming runs far faster; studying dense technical material runs slower; reading in a second language slower still. Treat the number as a planning estimate for typical prose, not a stopwatch. Fiction averages slightly higher, around 260 wpm.
Why do reading-time estimates differ between sites?
Three reasons: different assumed speeds (tools use anywhere from 180 to 300 wpm), different word counting (code blocks, captions, and headings may or may not count), and adjustments some sites make for images — Medium famously adds 12 seconds for the first image. Same article, honestly different answers.
Is my text stored anywhere?
No. Counting happens in your browser as you type — the text never leaves the page, there is no server call, and nothing persists after you close the tab. Paste unpublished drafts freely.
How exactly are words counted?
The page splits your text at whitespace and counts the resulting chunks, so a URL, a code token, or a long hyphenated string each counts as one word. A raw character count, spaces included, is shown beside it so you can sanity-check the number.
Does the estimate work for non-English text?
It works for any language that separates words with spaces — the 238 wpm figure is an English-based average, so treat the result as a planning estimate elsewhere. Languages written without word spaces, such as Chinese, Japanese, or Thai, are undercounted by any whitespace-based counter, including this one, so the minute estimate is not meaningful for them.
Can I use this for my blog’s “min read” label?
Yes. The number is simply your word count divided by 238, and the calculator needs no account. Keep in mind that other platforms assume different speeds — anywhere from 180 to 300 wpm — so your label will not always match a competitor’s for the same article.
