Reading Time Calculator
A 1,000-word blog post takes about 5 minutes to read at the standard 200 words-per-minute pace. This reading time calculator estimates how long a piece of text takes to read by counting the words in your content and dividing that count by a words-per-minute (WPM) reading speed. Paste in a blog post draft, an email newsletter, a script, or any block of text, and the tool returns an estimated reading time in minutes and seconds along with the total word count. The default pace is 200 WPM, a common average for adult silent reading, but you can raise or lower it to match a specific audience, a technical topic, or a script meant to be read aloud. It is a fast way to set reader expectations, plan content length, or check whether a draft fits a target reading window before publishing.
Quick answer
Default reading speed is 200 words per minute, a common average for adult silent reading of general web content.
What this tells you
- •Default reading speed is 200 words per minute, a common average for adult silent reading of general web content.
- •You can adjust words-per-minute for slower readers, technical material, or fast skimmers.
- •The tool counts words directly from the text you paste, splitting on whitespace, so formatting like extra line breaks does not change the count.
- •Results show a rounded minutes value plus a minutes-and-seconds display for a more precise, reader-facing estimate.
- •Reading time is a planning estimate based on word count and pace, not a measurement of how long any single reader will actually take.
- •Useful for blog posts, newsletters, product descriptions, scripts, and any content where you want to communicate expected reading effort.
How to Use
- 1Paste or type your text into the text field. Full drafts, blog posts, emails, and scripts all work.
- 2Check the words-per-minute value. It defaults to 200, a typical adult silent reading pace for general content.
- 3Adjust words-per-minute if your audience reads faster or slower, or if you are timing a script meant to be read aloud rather than read silently.
- 4Click Calculate to see the estimated reading time shown as minutes and seconds.
- 5Use the word count shown alongside the result to cross-check your draft against a target length for SEO, newsletters, or scripts.
How It Works
Formula
Reading minutes = word count ÷ words per minuteThe tool counts the words in your input by splitting on whitespace, then divides that count by the words-per-minute value you set. For example, 1,450 words at 200 WPM equals 7.25 minutes. That raw value is rounded to two decimal places for the minutes figure shown alongside the result. Separately, the tool converts the raw minutes into a minutes-and-seconds display by multiplying the raw value by 60 and rounding up to the next whole second. Rounding up rather than down means the displayed time never understates how long the content is likely to take, which matters more for planning purposes than shaving off a stray second.
Calculation note: values are processed in the order shown above, using the current input units.
Worked Examples
Standard blog post at default pace
A 1,000-word article at the default 200 WPM pace takes exactly 5 minutes to read, since 1,000 divides evenly by 200 with no leftover seconds. This is a common benchmark for a standard-length blog post and a useful sanity check for the tool's default settings.
Long-form article with extra seconds
1,450 words divided by 200 WPM equals 7.25 minutes. Converting the fractional 0.25 minute into seconds (0.25 times 60) adds 15 seconds, giving a display of 7 minutes 15 seconds. This minutes-and-seconds format is more useful for a reader-facing estimate than a bare decimal like 7.25.
Technical content at a slower pace
Technical or unfamiliar material is usually read more slowly than general content, so this example lowers the pace to 150 WPM. A 3,200-word guide at that speed takes 21 minutes 20 seconds, noticeably longer than the same word count would take at the 200 WPM default.
Script timed for narration
Scripts read aloud for video or podcast narration move slower than silent reading, so 130 WPM is a more realistic pace for this case. A 900-word script at that speed runs about 6 minutes 56 seconds, close to what a narrator would actually need during a recording.
Short product description at a fast pace
At a faster pace like 238 WPM, common among experienced readers on familiar topics, a 250-word product description takes about 1 minute 4 seconds to read. Short-form copy like this rarely needs a WPM adjustment since the difference between paces is usually just a few seconds.
Typical Reading Speeds by Pace
General words-per-minute ranges used for different reading situations. Use these as a starting point, then adjust for your specific audience.
| Reading pace | Words per minute | Typical use case |
|---|---|---|
| Slow, careful reading | 100 to 150 WPM | Technical documentation, textbooks, or non-native readers |
| Average adult silent reading | 200 to 250 WPM | General blog posts, articles, and emails |
| Fast reading | 250 to 300 WPM | Experienced readers skimming familiar topics |
| Narration or public speaking | 130 to 160 WPM | Scripts read aloud, podcasts, presentations |
| Children and early readers | 100 to 130 WPM | Elementary-level content and picture books |
| Speed reading | 400 to 700 WPM | Trained speed readers scanning for key points |
Comprehension tends to drop as reading speed climbs, so a faster WPM is not automatically the better setting for content meant to be understood in depth, not just skimmed.
Why words-per-minute varies so much
Reading speed is not a fixed number. It shifts with content difficulty, sentence length, vocabulary, and how familiar the reader already is with the subject. A reader moving through a casual blog post about a topic they already know will naturally read faster than the same reader working through a dense technical manual or an unfamiliar legal document, even if both pieces have the same word count.
The reading context matters too. Reading on a phone screen, reading in a noisy environment, or reading text broken up by ads and interruptions all tend to slow people down compared to focused reading on a printed page or a clean, distraction-free layout. Purpose changes speed as well: a reader skimming for one specific answer moves faster than a reader studying content to remember it later.
Content creators use reading time estimates for a few practical reasons. Blog writers use it to set expectations at the top of an article, so readers know roughly what they are committing to before they start. Email marketers use it to keep newsletters inside a length readers will actually finish. Video and podcast creators use a slower WPM setting to time scripts for narration, since speech is slower than silent reading.
The words-per-minute field in this calculator exists so the estimate can flex with these real differences. Starting from the 200 WPM default works for most general web content, but lowering it for technical writing or raising it for short, easy copy keeps the estimate closer to how your specific audience will actually experience the text.
Common mistakes
- Using one fixed WPM setting for every audience. Technical documentation and casual blog posts do not read at the same pace, and a single default can mislead readers either way.
- Counting words from heavily formatted text with headers, captions, and code blocks, which inflates the estimate compared to how a reader actually experiences flowing paragraphs.
- Ignoring images, embedded video, and interactive elements, all of which add real time to a page that a pure word count cannot capture.
- Treating the result as precise to the second instead of as a planning range for content length.
- Forgetting to slow the pace down for scripts meant to be read aloud. Narration speed is closer to 130 to 160 WPM, well below typical silent reading speed.
Embed this calculator on your site
Drop this single line where you want the calculator to appear. It is responsive, mobile-friendly, resizes automatically, and is free to use with attribution.
<script src="https://calctide.com/embed.js" data-tool="reading-time-calculator" async></script>Preview the embed at /embed/reading-time-calculator/.