Reading Time Calculator
Estimate how long a blog post, speech script, or announcement takes to read.
How the estimate is calculated
The tool counts the characters in your text with spaces removed, then divides by a reading speed measured in characters per minute (cpm). The default is 350 cpm for silent reading and about 280 cpm for reading aloud. So a 3,500-character passage at 350 cpm comes to 3,500 divided by 350, which is exactly 10 minutes. Because it works on raw character counts, the number updates the instant you edit, and nothing is uploaded, so it is safe to paste an unpublished draft.
Calibrating it for English: words vs characters
Most English readers think in words per minute, not characters. Comfortable silent reading runs about 200 to 250 wpm, and an English word is roughly five characters once spaces are stripped out. That puts natural English reading closer to 1,000 to 1,250 cpm, far above the 350 default, which is tuned for Korean where each character carries more meaning. To get realistic English numbers, raise the characters-per-minute setting: a simple rule is to multiply your target words per minute by about five, so 250 wpm becomes roughly 1,250 cpm. Leave the speed at 350 and a normal English article will look three to four times longer than it actually reads.
A worked example with real numbers
Suppose you paste an English article and the tool reports 5,000 characters excluding spaces, which is about 1,000 words. At the 350 default it shows roughly 14 minutes, since 5,000 divided by 350 is 14.3, and that is far too slow for English. Set the speed to 1,250 cpm and it drops to exactly 4 minutes; at a more relaxed 1,000 cpm (200 wpm) it comes to 5 minutes. So the honest read time for that piece is about 4 to 5 minutes, and the label you show readers should reflect the calibrated number, not the raw default.
When to use it
- Blog and newsletter labels: show an honest 5 min read so readers can decide up front. A realistic number builds trust, while an inflated one gets ignored.
- Talks and presentations: test a script against a time slot. English speakers average 130 to 150 wpm out loud, so a 1,000-word script runs about 7 minutes, not the 14-plus that the 350-characters-per-minute default implies.
- Video and narration: estimate voice-over runtime before you record, so the script length matches the visuals you are cutting to.
- Course and study material: gauge how long a chapter or handout takes a learner, and split anything over roughly 15 minutes into shorter sections.
Common mistakes
- Leaving the speed at the default for English text, which inflates every estimate about threefold.
- Treating reading speed and speaking speed as the same. Speaking aloud is much slower, so use a lower rate or the speaking readout when timing a script.
- Ignoring pauses and emphasis. A live talk has breaths, slide changes, and audience reactions, so add 10 to 20 percent on top of the raw estimate.
- Timing dense material at a skim rate. Technical, legal, or math-heavy writing is read slowly and often re-read, so lower the speed for it.
Cautions and limits
- The estimate is character-based, so tables, code blocks, formulas, and images that people study rather than read can take far longer than the number suggests.
- Reading speed varies widely between people, so treat the result as a range rather than a promise.
- Skimming and close reading are different activities. The same text can be a 2-minute scan or a 10-minute study.
- The whole calculation runs in your browser and nothing is sent to a server, so pasting confidential or unpublished text is safe.
Pasted text is analyzed only in your browser to estimate the time and is never sent to or stored on a server. Unpublished drafts and speech scripts stay private.
Read the Privacy Policy →Frequently asked questions
What characters-per-minute setting should I use for English?
English silent reading averages 200 to 250 words per minute, and a word is about five characters once spaces are removed, so set the speed to roughly 1,000 to 1,250 cpm. The 350 default is calibrated for Korean and will make English text look three to four times longer than it reads. A quick rule of thumb is to multiply your target words per minute by five.
Why does it count characters instead of words?
The tool measures characters excluding spaces because that stays consistent across languages, including Korean and Japanese where word boundaries are hard to define. For English you can convert freely: divide the character count by about five to approximate the word count, or multiply your target wpm by five to pick a speed.
How is speaking time different from reading time?
Reading silently is much faster than speaking aloud. English presenters typically speak at 130 to 150 words per minute, versus 200 to 250 for silent reading, so any script takes longer to say than to read. Because a live delivery adds pauses, slide changes, and emphasis, add 10 to 20 percent to the raw speaking estimate.
How accurate is the estimate?
It is a solid ballpark, not a stopwatch. Real reading time depends on the reader, the difficulty of the text, and whether they skim or study it, and content like tables, code, and images is not captured by a character count. Use it to compare drafts and set expectations, not as an exact runtime.
My article shows 14 minutes but feels like a 4-minute read. Why?
That gap is the Korean-tuned 350 default at work. A 5,000-character English piece is about 1,000 words, which reads in roughly 4 to 5 minutes, but at 350 cpm the math gives 14.3. Raise the speed to about 1,250 cpm and the estimate will match how English actually reads.
Can I trust it for mixed English and Korean text?
Yes, but choose a speed that matches the dominant language, since the two read at very different character rates. If a document is mostly English, use around 1,000 to 1,250 cpm; if it is mostly Korean, the 350 default is closer. For a genuine mix, time a representative paragraph and adjust the speed until it feels right.