100% in your browser · no upload
0 words0 charactersAverage pace (230 wpm)
Reading Time Calculator
Reading + speaking time · Slow / average / fast presets · Runs in your browser · no upload
How reading time is calculated
Estimate how long a piece of text takes to read silently or speak aloud. Pick a slow, average (the canonical ~230 wpm), or fast pace; speaking time always uses the standard ~130 wpm broadcast pace. Everything runs in your browser; your text never leaves your device. Free, private, no sign-up.
Reading time is a function of two numbers: how many words are in the text, and how fast the reader processes words per minute (wpm). Word count comes from the same tokenizer the Word Counter uses (runs of letters and digits, with hyphenated compounds and apostrophe contractions counted as one). The wpm comes from a 2019 meta-analysis by Marc Brysbaert covering 190 studies of adult silent reading, which settled the canonical adult silent rate at roughly 230 wpm. Speaking aloud lands closer to 130 wpm (broadcast-TV pacing, TED-talk average), which is what the speaking-time number on this page uses.
- Three presets: slow (150 wpm), average (230 wpm), fast (400 wpm)
- Reading time recomputes live as you type or switch the preset
- Speaking-time alongside it always uses 130 wpm (no override needed)
- Word count uses the same tokenizer the rest of the suite uses
- Everything runs in your browser; nothing is uploaded
Quick answer
Use the Average preset by default. Pick Slow for technical material, careful study, or text in a language the reader is still learning. Pick Fast for skimming or for a reader you know is well above the population average.
Reading time by word count
Common word-count anchors at each of the three presets. The middle column (230 wpm) is the canonical adult silent-reading average. Numbers are computed from the same library the live tool uses, so the table never drifts out of sync.
| Word count | Slow (150 wpm) | Average (230 wpm) | Fast (400 wpm) |
|---|---|---|---|
| 500 | 3 min | 2 min | 1 min |
| 1,000 | 6 min | 4 min | 2 min |
| 2,000 | 13 min | 8 min | 5 min |
| 5,000 | 33 min | 21 min | 12 min |
| 10,000 | 1 hr 6 min | 43 min | 25 min |
What the numbers actually mean
Three angles on the estimate: the research it's built on, what slows readers down in practice, and where the estimate stops being useful.
The research
- Brysbaert meta-analysis2019
- 238 wpm non-fiction silent
- 260 wpm fiction silent
- ~230 wpm across bothAvg
What slows readers
- Density of technical material
- Re-reading for full comprehension
- Small text, low contrast, poor leading
- Background noise and distractions
When to stop trusting it
- Code and equations (not prose)
- Image-heavy or tabular pages
- Anything under ~50 words
- Speed-reading claims past 700 wpm
How to use the reading-time calculator
Three steps. No sign-up, no setup, nothing to install.
- 1
Paste or type
Drop your draft into the input. Reading and speaking times update on every keystroke; nothing is uploaded.
- 2
Pick a pace
Average is the default. Pick Slow for technical material; pick Fast if your reader scans rather than reads.
- 3
Read the numbers
The big mint number is silent reading time; the sky number is speaking-aloud time. Use the silent figure for blog "X min read" badges and the speaking figure for talk scripts.
Who built this
Same team behind the Word Counter, Character Counter, Sentence Counter, and the rest of the suite. The wpm constants and the word tokenizer used here are imported directly from the shared counter library, so any change to the canonical rates flows through automatically.
The WordCounters team
Linguists, editors & engineersA small team of writers and engineers shipping privacy-first text tools. The reading-time numbers are computed from the Brysbaert 2019 silent-reading meta-analysis (~230 wpm) and the standard broadcast-TV / TED-talk speaking pace (~130 wpm). The slow (150) and fast (400) presets bracket the meta-analysis range.
Frequently asked
Direct answers; mirrored in this page's FAQ JSON-LD so AI answer engines can cite them cleanly.
How is reading time calculated?
Reading time is words divided by words-per-minute. The page counts words with the same tokenizer the word counter uses (runs of letters and digits, with hyphenated compounds and apostrophe contractions counted as one), then divides by the wpm you pick. The default is the canonical adult silent-reading average of about 230 words per minute, sourced from Marc Brysbaert's 2019 meta-analysis of 190 studies. Speaking time uses a separate constant of about 130 words per minute, which matches broadcast TV pacing and the average TED talk delivery.
What is the average reading speed?
For adults reading silently, the best-supported figure is about 238 words per minute for non-fiction and 260 wpm for fiction, with a cross-genre average near 230 wpm (Brysbaert 2019). Earlier folklore figures of 300 or 250 wpm overstate it. The Slow preset (150 wpm) brackets careful and technical reading; the Fast preset (400 wpm) brackets scanning with comprehension. Anything claiming reliable 700+ wpm with comprehension is usually scanning, not reading.
How does silent reading time differ from speaking time?
People process words faster silently than they can articulate them. Silent reading averages around 230 wpm for adult readers, while speaking aloud is closer to 130 wpm. The speaking-time figure on this page is useful for talk scripts, podcast intros, and conference presentations: dividing your script's word count by 130 gives you a realistic minute count for an out-loud read. The silent figure is what blogs use for the 'X min read' badge at the top of an article.
Why does my actual reading speed vary?
Density slows you down: technical writing pulls comprehension reading down to 150 wpm or below. Re-reading sentences for full retention roughly halves effective speed. Tiny font, low contrast, and narrow line-height all measurably drag speed; background noise and distractions do too. The presets on this page are averages across populations and texts. Your speed on any one piece will land within the slow-to-fast bracket, but not always at the average.
Should I trust speed-reading claims?
Programs that promise 700+ wpm with full comprehension don't survive controlled testing. What those programs actually train is scanning: skipping for keywords, useful for finding a name in a directory, useless for understanding an argument. If a piece is worth understanding, you'll read it at roughly the rates this page assumes. If it isn't, scanning is fine and the reading-time estimate doesn't matter.
Is my text uploaded anywhere?
No. The calculator runs entirely in your browser. We don't upload, log, or send a single character to any server. Your text is held in your browser's per-tab session storage so a refresh doesn't lose your work, and it clears the moment you close the tab. The page itself is static HTML; the calculator is a small client-side script. Closing the tab is the only privacy guarantee you ever need.
Try the rest of the tools
Same brutalist console, same privacy promise. Pick a tool: