Reading time estimator, calculate how long to read any text

Need to know how long your article, essay, or report will take to read? Use ToolHQ's free reading time estimator to calculate reading time instantly. Your text is processed in your browser and never sent anywhere.

ToolHQ's reading time estimator is a free browser-based tool that calculates how long it takes an average adult to read a piece of text, based on established reading speed research and your word count.

Every reader has encountered a blog post with "5 min read" at the top. That estimate comes from a reading time calculation. This tool generates that number from any text you paste in, with no guessing required.

Key Takeaways

• Estimates reading time based on average adult reading speed (200-250 words per minute)
• Shows word count, character count, and sentence count alongside reading time
• Your text is processed in your browser, never sent anywhere
• Adjust the reading speed to reflect your audience (general public, technical readers, children)
• Free with no login and no usage limits

---

How reading time is calculated

Reading time is estimated by dividing total word count by a target reading speed in words per minute (WPM).

The formula: Reading time (minutes) = Word count / Reading speed (WPM)

The question is what reading speed to use. According to the Wikipedia article on reading, research on average adult reading speed consistently points to a range of 200-250 words per minute for silent reading of general-purpose prose. Key reference points:

• Average adult reading speed: 200-250 WPM for comprehension reading
• Speed reading: 400-700 WPM (with reduced comprehension)
• Technical or academic text: 100-200 WPM (denser, requires more cognitive processing)
• Children (age 10): Around 150 WPM
• Out-loud reading or presentation: 100-150 WPM

Most publishers and content platforms use 200 WPM as the baseline for general audiences. Medium uses 265 WPM. Readtime (common in CMS plugins) often uses 200-238 WPM. The exact value affects the estimate by a few seconds per paragraph, which is why reading time estimates are typically rounded to the nearest half-minute or minute.

---

Why reading time matters for writers and readers

Reading time estimates serve different purposes for the people producing content and those consuming it.

For writers and content creators:

Knowing the reading time lets you align article length with your format. A 400-word blog post takes about 2 minutes to read. A 2,000-word feature is about 8-10 minutes. If you're writing a 25-minute-read technical guide, that signals a very different commitment from the reader than a 3-minute news piece.

For readers:

Seeing a reading time estimate upfront helps you decide whether to read now, save for later, or skip. A "3 min read" tag on a lunch break feels achievable. A "22 min read" may go into a read-later queue.

For presenters:

Reading text aloud or narrating a script runs at around 120-150 WPM. A 900-word script = about 6 minutes of spoken content. Knowing this helps you script conference talks, video narrations, and podcast segments to the correct length.

Mini-story: Daniel is a 36-year-old content strategist who manages a B2B software blog. His team debates whether long-form articles (3,000+ words) perform better than short ones (800-1,000 words). He starts adding reading time estimates to each article using ToolHQ's estimator. He pastes each draft in, records the reading time in a spreadsheet, and tracks engagement by reading time bracket over 90 days. He discovers that 6-10 minute reads (1,200-2,500 words) generate the most time-on-page and the most shares. He adjusts the team's content brief template to target that length range.

Estimate reading time at ToolHQ

---

How to use the reading time estimator

1. Open ToolHQ's reading time estimator in your browser.
2. Paste your text into the input area. Your text is processed locally in your browser and never sent anywhere.
3. See the reading time estimate update immediately, along with word count, character count, and sentence count.
4. Adjust the reading speed if your audience differs from the general adult average (technical content, children's material, or presentation scripts).
5. Use the estimate for adding a reading time tag to your article, planning a script, or deciding if your content is the right length.

---

Reading time estimates for common content lengths

Word count	Reading time (200 WPM)	Typical content type
300 words	1.5 min	Short news item, product description
600 words	3 min	Blog post, newsletter item
1,000 words	5 min	Standard article
1,500 words	7.5 min	Feature article, long blog post
2,500 words	12.5 min	In-depth guide, whitepaper section
5,000 words	25 min	Research report, long-form essay
10,000 words	50 min	Ebook chapter, academic paper

Mini-story: Priya is a 28-year-old UX researcher who was designing the content layout for a healthcare patient portal. The design brief specified that all patient education articles should be under 5 minutes to read. The content team had written 12 articles at varying lengths. Priya pasted each article into ToolHQ's reading time estimator and recorded the result. Eight of the twelve articles were under 5 minutes. Three were between 5 and 8 minutes (she flagged these for editing). One was 14 minutes (she flagged it for splitting into two articles). The audit took under 20 minutes to complete across all 12 articles.

For counting words in your text, use ToolHQ's word counter. For counting characters, use the character counter. For changing text case, use ToolHQ's text case converter. Browse all text tools in the ToolHQ text category.

---

How reading speed varies by content type

The 200-250 WPM baseline for average adult reading is appropriate for general-purpose prose, but reading speed varies significantly depending on the type of content. Understanding these differences helps you calibrate the estimator for your specific audience.

General text and news articles. The 200-250 WPM range is well-supported by research. A 2016 meta-analysis published in Psychological Bulletin (Rayner et al.) reviewed 190 studies on reading speed and found the average silent reading speed for college-educated adults is approximately 238 WPM for fiction and general prose. This is the figure ToolHQ's estimator uses as its standard.

Technical documentation and developer content. Technical readers slow down significantly when processing reference material, code samples, configuration examples, and step-by-step instructions. The cognitive load of parsing code, mentally tracing logic, or cross-referencing documentation means effective reading speed for this content type is closer to 100-150 WPM. A 2,000-word API reference guide may take 15-20 minutes to meaningfully process, not the 8-10 minutes the standard formula would suggest. If you are estimating time for developer documentation, use 100-150 WPM for a more realistic number.

Academic papers and research. Trained academic readers process papers in their field faster than a general reader would -- familiarity with the domain reduces the cognitive overhead of parsing specialized terminology. However, reading for comprehension and critique (as opposed to scanning) still runs slower than general prose. Experienced researchers typically read academic papers in their own field at 200-300 WPM. Reading a paper outside one's specialty can drop to 100-150 WPM.

Speed reading techniques. Speed reading methods (RSVP, skimming, chunking) claim 500-1,000 WPM. Research on comprehension at these speeds is mixed. Most studies find comprehension drops significantly above 400-500 WPM. Speed reading is more accurately described as structured skimming than as reading with retained comprehension, which is why publishers do not use these higher figures for "time to read" estimates.

The 230 WPM standard. ToolHQ's estimator uses 230 WPM as its default, which falls within the 200-250 WPM range documented in reading research. This matches the widely cited figures used in publishing, content management systems, and the research literature. For a general adult audience reading blog posts, articles, or reports, this produces estimates that closely match observed reading behavior.

---

Frequently asked questions

Is my text sent to a server when I paste it in?

No. ToolHQ's reading time estimator processes your text entirely in your browser. Your text is never sent anywhere and never leaves your device.

What reading speed does the tool use?

The default is 200-250 WPM, matching average adult silent reading speed for general-purpose prose. Many tools let you adjust this for technical content (lower WPM) or fast readers (higher WPM).

Why does my reading time differ from Medium or other platforms?

Different platforms use different baseline reading speeds. Medium uses approximately 265 WPM. Platforms targeting general consumer audiences often use 200 WPM. A 1,000-word article will show 3 min 46 sec at 265 WPM vs. 5 min at 200 WPM. Both are valid; the right number depends on your audience.

Does reading time include images?

Some CMS plugins add 12 seconds per image to the reading time estimate (to account for time spent looking at visuals). ToolHQ's estimator calculates based on text only. If your content has many images, the actual reading time may be longer than the text-only estimate.

What about code blocks and technical content?

Code takes longer to process than prose. If your text includes significant amounts of code, consider using a lower reading speed (100-150 WPM) to get a more realistic estimate for your technical audience.

---

The short version

Reading time estimates help writers target the right length and help readers decide what to read now vs. later. ToolHQ's reading time estimator calculates reading time instantly from any text you paste in -- with word count, character count, and sentence count alongside the estimate. Your text is processed in your browser, never sent anywhere.

Paste your text, get your estimate. One step.

For word counting, use ToolHQ's word counter. For character counting, use the character counter. Browse all text tools at the ToolHQ text category.

Estimate reading time now

---