Paste any text to get an instant reading time estimate — the peer-reviewed 238 WPM standard, with slow, fast, and custom presets plus speaking time at 130 WPM.
Your text never leaves your browser. Nothing is uploaded or stored.
Reading time uses your selected speed · Speaking time stays at 130 WPM (presentation pace) · Custom range 50–1000 WPM · Image time follows Medium's documented formula.
Paste your text above and get your reading time in seconds. This calculator uses 238 words per minute, the figure from Marc Brysbaert's 2019 meta-analysis of 190 studies covering 18,573 participants, published in the Journal of Memory and Language. That is the most rigorously sourced reading speed figure available in the scientific literature, and it is what this tool defaults to.
You also get your speaking time at 130 WPM, the pace most commonly recommended for formal, audience-addressed delivery — a conference talk, a classroom lecture, or a keynote. That is different from the oral reading rate of 183 WPM, and the difference matters, because those are two very different use cases.
Below the tool, you will find a complete reading time reference table, the science behind every number this calculator uses, how platforms like Medium and Substack calculate their own read time labels, a guide to adding reading time to your own website, and a full FAQ covering every common question in this space.
If you already know your word count and just need the reading time, this table gives you the answer at three reader speeds, plus speaking time at 130 WPM.
Use the Slow column for technical documentation, academic papers, or legal text. Use the Average column for most blog posts, newsletters, and general web content. Use the Fast column for light fiction or content your audience already knows well.
| Word Count | Pages (approx.) | Slow (150 WPM) | Average (238 WPM) | Fast (300 WPM) | Speaking (130 WPM) |
|---|---|---|---|---|---|
| 300 words | 1 page | 2 min | 1 min 16 sec | 1 min | 2 min 18 sec |
| 500 words | 1.7 pages | 3 min 20 sec | 2 min 6 sec | 1 min 40 sec | 3 min 51 sec |
| 750 words | 2.5 pages | 5 min | 3 min 9 sec | 2 min 30 sec | 5 min 46 sec |
| 1,000 words | 3.3 pages | 6 min 40 sec | 4 min 12 sec | 3 min 20 sec | 7 min 41 sec |
| 1,200 words | 4 pages | 8 min | 5 min 3 sec | 4 min | 9 min 14 sec |
| 1,500 words | 5 pages | 10 min | 6 min 18 sec | 5 min | 11 min 32 sec |
| 1,800 words | 6 pages | 12 min | 7 min 34 sec | 6 min | 13 min 50 sec |
| 2,000 words | 6.7 pages | 13 min 20 sec | 8 min 24 sec | 6 min 40 sec | 15 min 23 sec |
| 2,500 words | 8.3 pages | 16 min 40 sec | 10 min 30 sec | 8 min 20 sec | 19 min 13 sec |
| 3,000 words | 10 pages | 20 min | 12 min 36 sec | 10 min | 23 min 4 sec |
| 5,000 words | 16.7 pages | 33 min 20 sec | 21 min | 16 min 40 sec | 38 min 27 sec |
| 7,500 words | 25 pages | 50 min | 31 min 30 sec | 25 min | 57 min 41 sec |
| 10,000 words | 33.3 pages | 1 hr 6 min | 42 min | 33 min 20 sec | 1 hr 16 min |
| 20,000 words | 66.7 pages | 2 hr 13 min | 1 hr 24 min | 1 hr 6 min | 2 hr 33 min |
| 50,000 words | 166 pages | 5 hr 33 min | 3 hr 30 min | 2 hr 46 min | 6 hr 24 min |
| 80,000 words | 267 pages | 8 hr 53 min | 5 hr 36 min | 4 hr 26 min | 10 hr 15 min |
Pages estimated at 300 words per page, a common web-publishing convention (a double-spaced manuscript page holds roughly 250 words). Speaking time uses 130 WPM for formal presentation pace.
Reading time has a simple formula at its core, but the number you divide by matters enormously, and almost every tool online gets that number wrong.
So for a 1,000-word article at 238 WPM, the calculation is: 1,000 divided by 238, multiplied by 60 = 252 seconds, or 4 minutes and 12 seconds. For a clean display label, most platforms round to the nearest whole minute and show it as "4 min read." This calculator goes one step further and shows the precise figure — minutes and seconds — updating live as you type.
The internet has repeated 300 words per minute as the average adult reading speed for decades. That figure has no credible peer-reviewed source. It appears to have originated from small, non-representative samples, often college students who read faster than the general adult population.
In 2019, Marc Brysbaert at Ghent University published a meta-analysis in the Journal of Memory and Language that reviewed 190 reading-rate studies covering 18,573 participants. The result was clear: the average adult silent reading rate for English non-fiction is 238 WPM. For fiction, the figure is slightly higher at 260 WPM, because narrative prose uses more familiar vocabulary and pulls readers forward. For reading aloud, the rate drops to 183 WPM.
This is the most comprehensive and rigorously controlled dataset on human reading speed in the scientific literature. Most competing reading time calculators use a figure between 200 and 300 WPM, and very few name their source. This tool defaults to 238 WPM and names its source, because precision matters when your estimate is guiding a reader's decision about whether to click.
Most tools conflate three very different rates as if they are the same thing. They are not:
| Mode | WPM | Source | Use Case |
|---|---|---|---|
| Silent reading (non-fiction) | 238 WPM | Brysbaert (2019) | Blog posts, articles, newsletters, documentation |
| Silent reading (fiction) | 260 WPM | Brysbaert (2019) | Novels, narrative content, light fiction |
| Oral reading / narration | 183 WPM | Brysbaert (2019) / Hasbrouck & Tindal | Audiobooks, read-aloud, voiceover |
| Presentation / keynote | 130 WPM | Speech-rate research; Toastmasters guidance places the most effective rate between 120 and 160 WPM | Conference talks, lectures, speeches |
| Casual conversation | 140 to 160 WPM | General speech research (roughly 150 WPM on average) | Podcasts, informal video |
The oral reading figure deserves its own note: Brysbaert's 183 WPM comes from a separate meta-analysis of 77 studies with 5,965 participants measuring people reading aloud at maximum fluency. It is a laboratory measure, not a presentation pace — a keynote speaker delivering to an audience runs closer to 130 WPM once pauses, emphasis, and audience processing are factored in.
This calculator exposes both silent reading time and speaking time because they serve different workflows. A blogger needs the reading time. A speaker needs the speaking time. A voiceover artist needs the narration rate. These are not the same number, and using the wrong one leads to systematically wrong estimates.
The single most useful adjustment you can make to a reading time estimate is matching the WPM figure to your content type. A 2,000-word API reference and a 2,000-word lifestyle blog post are not equal. The blog post might take an average reader 8 minutes. The API reference could easily take 20 minutes, because dense jargon forces re-reading, unfamiliar vocabulary slows processing, and readers pause to test or verify technical claims.
Here is what the research shows for reading speeds across common content types:
| Content Type | Typical WPM Range | Why It Differs |
|---|---|---|
| Light fiction / narrative | 260 to 350 WPM | Familiar vocabulary, narrative pull forward, emotional engagement sustains pace |
| General blog posts / news | 200 to 260 WPM | Standard web prose; readers may skim headings but read body text |
| Technical blog posts | 175 to 220 WPM | Mixed familiar and unfamiliar vocabulary; readers slow down selectively |
| Technical documentation / API | 100 to 150 WPM | Dense jargon; frequent re-reading; readers verify claims while reading |
| Academic papers | 75 to 150 WPM | Complex argument structure; unfamiliar concepts require active processing |
| Legal documents | 75 to 100 WPM | High-stakes precision; readers process every word deliberately |
| Medical / clinical content | 100 to 175 WPM | Specialized vocabulary; accuracy requirements slow reading significantly |
| Proofreading / editing | 30 to 55 WPM | Professional proofreaders cover roughly 2,000–3,000 words per hour |
| Code reading | Slower than prose | Active interpretation; pattern matching fails for unfamiliar syntax |
| Skimming / scanning | 600 to 700 WPM | Pattern recognition only; not comprehension reading |
If your content is technical, switch to the Custom WPM field in the calculator and enter a value between 130 and 175. If you are writing for a domain-expert audience already familiar with your vocabulary, 200 to 220 WPM is more realistic. The default 238 WPM is the right choice for general-audience non-fiction.
Reading speed develops continuously from childhood through adulthood. These are approximate silent-reading benchmarks: the school-grade figures are anchored to the Hasbrouck and Tindal (2017) oral reading fluency norms (children's silent reading typically runs faster than their read-aloud pace), and the adult figure is Brysbaert's peer-reviewed benchmark:
| Age Group | Approx. WPM (Silent) | Notes |
|---|---|---|
| Grade 1 (age 6–7) | 70 to 100 WPM | Early phonics; subvocalisation dominates |
| Grade 3 (age 8–9) | 100 to 130 WPM | Fluency developing; word recognition improving |
| Grade 5 (age 10–11) | 130 to 160 WPM | Near-automaticity for simple text |
| Grade 8 (age 13–14) | 160 to 200 WPM | Approaching adult pace for familiar content |
| High school (16–18) | 200 to 260 WPM | Adult range reached for non-fiction |
| College student | 250 to 300 WPM | Slightly above the general adult average; Brysbaert's college samples averaged about 280 WPM |
| Average adult (non-fiction) | 238 WPM | Brysbaert (2019) peer-reviewed benchmark |
School-grade figures anchored to the Hasbrouck & Tindal (2017) oral reading fluency norms (silent reading typically runs faster than oral for young readers); adult silent reading estimate from Brysbaert (2019).
The 238 WPM benchmark applies to English. Reading speed measured in words per minute varies across languages, because languages pack different amounts of information into an average word. In the International Reading Speed Texts (IReST) project, a standardized set of comparable texts read aloud by adults in 17 languages, the average oral reading rate was about 184 words per minute with substantial variation between languages — while the same texts measured in characters per minute converged much more closely. Long-word languages such as Finnish produce lower word-per-minute figures without slower reading, because each word carries more characters.
For character-based writing systems, the word-count model breaks down entirely: Chinese and Japanese text is measured in characters per minute rather than words. That is why Medium switches to 500 characters per minute for Chinese, Japanese, and Korean content instead of its 265 WPM word formula. If you write in multiple languages, treat word-based reading time estimates as comparable within a language family, and expect them to diverge across structurally different ones.
Adding a reading time label to a blog post is one of the smallest changes you can make to a content page, and one of the most consistently effective. The data behind this is real.
A widely cited case study published by Simpleview in April 2022 found that engagement rates increased by up to 40% after reading times were added to blog posts and news articles. The specific metrics that improved were: lower bounce rates, higher time spent on site, and a greater number of page views per session. The same pattern has been reported repeatedly in publisher case studies and content-marketing analyses since.
None of these results are flukes. They reflect a consistent underlying mechanism: when readers can see the time cost of an article upfront, the people who click are the people who actually intend to read it.
When a reader lands on an article with no reading time displayed, they face an unquantified time commitment. The psychological research on the "paradox of choice" shows that uncertainty about costs reduces decision confidence. Applied to content: when someone cannot see how long your article is in human time terms, the cognitive burden of the unknown pushes them toward leaving.
A "3 min read" label removes that uncertainty entirely. The reader makes a micro-commitment. They have decided to invest three minutes. That decision makes them significantly more likely to read through to the end, and significantly less likely to bounce mid-article. The reading time label is not decoration. It is a decision aid built on cognitive psychology.
One important modern context: in Google Analytics 4, a user who lands on your article, reads it for 8 minutes, and then closes the tab is not counted as a "bounce." GA4 defines an engaged session as one that lasts longer than 10 seconds, includes a key event (conversion), or includes at least two pageviews. A reader who spends 8 minutes on a single article triggers the engagement threshold easily.
This matters for reading time strategy because it means your reading time indicator is directly connected to your GA4 engagement rate. Pull in readers who see that a piece will take 8 minutes and commit to it, and your engaged session rate goes up. Display no reading time, attract mismatched readers who leave in 30 seconds, and your engagement rate suffers. The reading time label is a filter for the right audience.
Google does not directly use reading time as a ranking signal. What it does use, as signals of content quality, are the behavioral outcomes that reading time labels improve: lower bounce rates, higher dwell time, greater page engagement, and more internal navigation. Reading time is an indirect SEO lever that works by improving user experience and signaling relevance to the right reader.
Content length also matters in relation to reading time. Backlinko's analysis of first-page Google results found an average post length of 1,447 words, roughly a 6-minute read at 238 WPM. HubSpot's research points to 2,100 to 2,400 words as the sweet spot for SEO and engagement, which translates to an 8 to 10-minute read. Medium's data from 2013 identified the 7-minute read as the peak engagement length. These numbers have aged, but the principle holds: matching content depth to audience intent, then communicating that depth upfront via a reading time label, consistently outperforms content that leaves readers guessing.
If you have ever noticed that the reading time shown on Medium differs from what this calculator shows, that is expected. Each platform uses a slightly different WPM figure and applies different rules for images and other non-text elements.
Medium calculates reading time at approximately 265 WPM for English text. The formula is:
seconds = (word_count / 265) * 60 + image_weight * number_of_imagesFor images, Medium applies a descending weight: 12 seconds for the first image, 11 seconds for the second, minus 1 second for each subsequent image, with a minimum of 3 seconds per image. This accounts for the fact that image-heavy essays take longer to consume even though images do not add to word count.
For Chinese, Japanese, and Korean content, Medium uses 500 characters per minute rather than a word-based formula, because character-based languages do not map cleanly to the word-count model.
Substack auto-calculates reading time for every newsletter post and displays it in the email header and on the web view. Substack does not publicly document its exact WPM figure, but independent testing suggests it uses a figure close to 200 to 225 WPM, which is slightly lower than the Brysbaert benchmark. This means Substack estimates are typically a minute or two longer than this calculator for the same text.
Ghost has native reading time support built into its templating system. Ghost's official developer documentation states that the {{reading_time}} helper counts the words in a post and calculates an average reading time at 275 words per minute — a slightly faster figure than Medium's 265 — and Ghost also factors images into its estimate, adding 12 seconds for the first image and progressively less for each subsequent one, mirroring Medium's weighting. The helper exposes the reading time as a template variable, so developers can display it anywhere in their theme without additional plugins or custom code.
WordPress does not have native reading time support. Every reading time display on a WordPress blog comes from either a plugin or a custom code snippet. Plugin defaults vary widely: the popular Read Meter plugin defaults to 275 WPM, Yoast SEO Premium has offered an estimated reading time feature since version 15.6 (January 2021) without publicly documenting its WPM, and other plugins use figures ranging from 200 to 275 WPM — often without documenting which figure they use. This inconsistency is why plugin-estimated reading times on WordPress blogs can vary significantly from platform to platform. This calculator gives you the ability to set any WPM figure you want, so you can match whatever your CMS or plugin uses.
| Platform | WPM Used | Image Adjustment | Source |
|---|---|---|---|
| This calculator (default) | 238 WPM | No (text-paste tool) | Brysbaert (2019) peer-reviewed |
| Medium | 265 WPM | Yes: 12s, 11s, 10s... min 3s per image | Medium platform documentation |
| Ghost CMS | 275 WPM | Yes: 12s for the first image, decreasing (min 3s) | Ghost templating docs |
| Substack | approx. 200–225 WPM | Likely yes | Estimated from community testing |
| WordPress (typical plugin) | 200–275 WPM | Varies by plugin | Plugin-specific (Read Meter defaults to 275) |
| Yoast SEO for WordPress | Not publicly documented | No | Yoast SEO Premium feature since v15.6 (Jan 2021) |
Once you know the reading time for your content, the next logical step is displaying it automatically on your website so every post gets the label without manual calculation. Here are the most reliable methods across the most common platforms.
The Read Meter plugin is the most feature-complete free option. It calculates reading time server-side, displays it in a configurable position (top or bottom of post), supports custom WPM settings, and optionally adds a visual progress bar. Install it from the WordPress plugin directory and configure it from Settings, then Read Meter.
If you prefer not to install a plugin, WPCode is a code snippet manager that includes a pre-built reading time snippet in its library. Install WPCode, open the snippet library, search for "reading time," and activate it. This approach adds zero extra database tables and has minimal performance overhead.
Add this function to your theme's functions.php file or a child theme. This uses 238 WPM to match the Brysbaert benchmark:
function textcountify_reading_time() {
$content = get_post_field( 'post_content', get_the_ID() );
$words = str_word_count( strip_tags( $content ) );
$minutes = ceil( $words / 238 );
return $minutes . ' min read';
}Then call textcountify_reading_time() anywhere inside The Loop to output the label. For example, place it in your single.php or content.php template directly after the post title.
Ghost has reading time built in as a template helper. In your theme's Handlebars templates, use the reading_time helper wherever you want the label to appear:
{{reading_time}}By default this outputs a string like "4 min read." You can customise the output with the singular and plural options for posts above or below one minute.
This works on any HTML page, with no framework or library required. Paste this script into your page and call it with the text content of your article:
function getReadingTime(text, wpm) {
wpm = wpm || 238;
var words = text.trim().split(/\s+/).length;
var minutes = Math.ceil(words / wpm);
if (minutes < 1) return "Less than 1 min read";
return minutes + " min read";
}
// Usage:
var articleText = document.getElementById("article-body").innerText;
document.getElementById("read-time").textContent = getReadingTime(articleText);Replace "article-body" with the ID of your content container, and "read-time" with the ID of the element where you want the label to appear. Change the wpm parameter to 265 if you want to match Medium's estimate.
Webflow does not have native reading time support. Use the vanilla JavaScript method above in a custom code embed or in Project Settings under Custom Code. Target the Rich Text element using its class or ID. Because Webflow uses dynamic collections for CMS items, test on a live published page rather than in the Designer preview, since innerText calculations require a rendered DOM.
Substack calculates and displays reading time automatically on every post. You cannot override or customise it. If your Substack estimate differs significantly from this calculator, it is because Substack likely uses a slightly lower WPM figure than 238.
If you are writing to a specific time target rather than measuring an existing piece, use this table to plan your word count. These figures use 238 WPM for reading and 130 WPM for speaking. Then track your draft against the target as you write with the word counter.
| Target Time | Words Needed (Reading, 238 WPM) | Words Needed (Speaking, 130 WPM) | Typical Content Format |
|---|---|---|---|
| 1 minute | 238 words | 130 words | Micro-post, social update, email intro |
| 2 minutes | 476 words | 260 words | Short blog post, listicle intro, product description |
| 3 minutes | 714 words | 390 words | Standard announcement post, short email newsletter |
| 5 minutes | 1,190 words | 650 words | How-to guide, product review, feature article |
| 7 minutes | 1,666 words | 910 words | In-depth post (Medium's peak engagement length), full tutorial |
| 8 minutes | 1,904 words | 1,040 words | HubSpot average high-performing SEO post |
| 10 minutes | 2,380 words | 1,300 words | Long-form guide, pillar content section, chapter summary |
| 15 minutes | 3,570 words | 1,950 words | Comprehensive guide, deep-dive analysis, full white paper chapter |
| 18 minutes | 4,284 words | 2,340 words | Formal 18-minute keynote at 130 WPM (TED talks average about 160 WPM, roughly 2,880 words) |
| 20 minutes | 4,760 words | 2,600 words | Conference presentation, long-form research summary |
| 30 minutes | 7,140 words | 3,900 words | In-depth report, short book chapter, long white paper |
| 60 minutes | 14,280 words | 7,800 words | Full academic chapter, comprehensive e-book section |
The 7-minute read deserves a specific note: Medium's internal data from 2013 identified the 7-minute article as the format generating the highest total reading time across their platform. More recent data from Backlinko shows that the average first-page Google result sits at 1,447 words, a 6-minute read at 238 WPM. These two data points are close enough to suggest that the 6 to 8-minute range remains a strong target for content that both ranks and holds attention.
Speaking time is the separate calculation this tool provides alongside reading time, and the use cases are meaningfully different. Reading time serves content creators who want to label a blog post. Speaking time serves anyone who needs to know how long it will take to deliver content out loud. For the delivery side in full — pace presets, section-by-section timing, and rehearsal tools — the speaking time calculator covers it in depth.
| Format | Typical WPM | Notes |
|---|---|---|
| Keynote / conference talk | 130 WPM | Commonly cited standard; allows pauses and emphasis; clear projection |
| Academic lecture | 125 to 140 WPM | Slightly slower to accommodate note-taking and concept absorption |
| TED Talk | 150 to 175 WPM | Analyses of delivered talks average 163 WPM; rehearsed, high-production delivery |
| Podcast (conversational) | 150 to 160 WPM | Casual, fast; guests set pace naturally |
| Audiobook narration | 145 to 160 WPM | Audible's ACX standard is 9,300 words per finished hour (about 155 WPM); varies by genre |
| Voiceover (explainer video) | 150 to 180 WPM | Depends on target audience age and complexity |
| Wedding / social toast | 120 to 130 WPM | Slower to maximize emotional impact; includes pauses |
| Natural conversation | 140 to 160 WPM | General adult speech rate |
| Oral reading (Brysbaert) | 183 WPM | Measured lab figure; faster than natural speech because readers do not improvise |
This calculator uses 130 WPM for speaking time because it is the most commonly cited figure for formal, audience-addressed delivery. If you are writing a podcast script rather than a keynote, your actual delivery rate is likely 150 to 160 WPM. Use the Custom WPM field and set it to your real speaking pace for the most accurate estimate.
A common misconception worth addressing directly: reading faster does not mean understanding more. Above approximately 400 to 500 WPM, comprehension drops measurably in controlled studies. Speed reading courses that claim 1,000 or 2,000 WPM with full comprehension do not survive scientific scrutiny.
Keith Rayner's eye-tracking research, published with colleagues in Psychological Science in the Public Interest, found that the physical and cognitive constraints on reading speed are real: the eye identifies only roughly 7 to 9 letters in a single fixation. Speed reading techniques that eliminate subvocalisation or use rapid serial visual presentation (RSVP) can increase raw words processed per minute, but they consistently reduce comprehension of complex material.
Guinness World Records no longer recognises speed-reading claims because they cannot be verified with standardised comprehension checks. The 25,000 WPM claim you may have seen cited is a marketing figure, not a scientific result.
For the purpose of estimating reading time, this matters because the 238 WPM benchmark from Brysbaert represents reading with comprehension. If your audience is skimming, they are processing your content at 600 to 700 WPM but retaining a fraction of it. The reading time a serious reader will actually spend on your content is the figure that matters for editorial planning, and that figure is closer to 238 WPM than to any speed-reading claim.
The average adult reads at 238 words per minute for silent non-fiction reading, according to Marc Brysbaert's 2019 meta-analysis of 190 studies covering 18,573 participants, published in the Journal of Memory and Language. For fiction, the average is slightly higher at 260 WPM. The figure you commonly see cited elsewhere, 300 WPM, lacks a credible peer-reviewed source and is scientifically inaccurate for the general adult population.
Divide total word count by words per minute, then multiply by 60 to get seconds. At 238 WPM: a 1,000-word article takes approximately 252 seconds, or 4 minutes and 12 seconds. Displayed as a label, this rounds to "4 min read." This calculator applies the formula instantly as you type, using 238 WPM by default with presets for slow (150 WPM), fast (300 WPM), and a fully custom WPM input.
At the average adult reading speed of 238 WPM, 1,000 words takes approximately 4 minutes and 12 seconds. At 150 WPM for technical content, the same 1,000 words takes 6 minutes and 40 seconds. At a fast reading pace of 300 WPM, it takes 3 minutes and 20 seconds. For a speaking estimate at 130 WPM, 1,000 words takes 7 minutes and 41 seconds.
At the 238 WPM average reading speed, a 5-minute read is approximately 1,190 words. At 150 WPM for technical content, 5 minutes covers about 750 words. At a fast 300 WPM pace, 5 minutes covers around 1,500 words. For spoken delivery at 130 WPM, a 5-minute presentation requires approximately 650 words.
A 5-minute speech at 130 WPM, the commonly recommended conference and keynote presentation pace, requires approximately 650 words. At a faster podcast or conversational pace of 150 WPM, 5 minutes covers around 750 words. An 18-minute TED-style keynote at the same formal 130 WPM pace needs about 2,340 words, though analyses of delivered TED talks find speakers actually average 150 to 175 WPM, closer to 2,900 words for a full 18-minute talk.
Silent reading is faster because your eyes process word patterns without needing to physically produce each word. When speaking, you add natural pauses for emphasis, breath, and audience comprehension. A formal presentation at 130 WPM is deliberately paced to allow the audience to follow without note-taking pressure. This is different from the oral reading rate of 183 WPM, which Brysbaert measured in a laboratory setting and reflects reading aloud at maximum fluency, not natural presentation delivery.
Medium uses approximately 265 WPM for English text and adds image weight: 12 seconds for the first image, 11 for the second, minus 1 second for each subsequent image down to a minimum of 3 seconds per image. For CJK languages, Medium uses 500 characters per minute. If your Medium reading time estimate differs from this calculator, it is because Medium uses 265 WPM while this tool defaults to the more conservative peer-reviewed figure of 238 WPM. Set Custom WPM to 265 in this calculator to match Medium's output.
For technical documentation, API references, and developer guides, use 130 to 150 WPM. For academic papers, 75 to 150 WPM depending on how specialized the content is. For legal documents, 75 to 100 WPM. The default 238 WPM will systematically underestimate the actual time your readers spend on complex material, which can lead to mislabeled reading times and reader frustration when they find the article takes longer than the label suggests.
Yes, above approximately 400 to 500 WPM. Speed reading techniques increase the words your eyes pass over per minute, but comprehension of complex ideas drops significantly at speeds above this range. Studies consistently show that the cognitive capacity for comprehension, not eye movement speed, is the real constraint on reading rate. Claimed speeds of 1,000 WPM or higher represent skimming or pattern recognition, not reading with understanding.
Not directly, because reading time is not a Google ranking signal. Indirectly, yes. Reading time labels reduce bounce rates, increase average session duration, and improve the quality of your audience match, all of which generate stronger behavioral engagement signals that Google interprets as evidence of content quality. A Simpleview case study found that adding reading time labels improved engagement rates by up to 40%.
No. Every calculation in this tool happens entirely in your browser using JavaScript. Your text is never transmitted, stored, logged, or shared. Closing the tab removes everything. No account is needed and no data is collected.
Reading time is how long a silent reader takes to consume your content, calculated at 238 WPM. Speaking time is how long it takes to deliver the same content out loud at a pace appropriate for an audience, calculated at 130 WPM. The gap between them reflects the fundamental difference between silent reading, which is an internal visual process, and public delivery, which adds physical production, pacing, pauses, and audience awareness. The same 1,000 words takes 4 minutes and 12 seconds to read silently and 7 minutes and 41 seconds to deliver as a presentation.
For WordPress, the Read Meter plugin or a custom functions.php snippet at 238 WPM are both reliable approaches. For Ghost, use the built-in reading_time helper in your Handlebars template. For any HTML-based site, use the vanilla JavaScript function in the implementation section above. For Webflow, embed the same JavaScript in a custom code block. For Substack, reading time is auto-calculated and cannot be customised.
Yes. Enter the number of images in your article in the optional Images field, and the calculator adds Medium's documented image time to your reading time: 12 seconds for the first image, 11 for the second, minus one second for each subsequent image, with a minimum of 3 seconds per image. A 1,000-word article with 3 images at 238 WPM takes 4 minutes 12 seconds of reading plus 33 seconds of image time, a total of about 4 minutes 45 seconds. This makes the estimate match what Medium itself would display for your post.
More free counting tools from TextCountify