Free Reading Time Calculator Online

What is reading time and why does it matter?

Reading time is an estimate of how long it will take a person to read a piece of text from start to finish. It is calculated by dividing the total word count by an assumed reading speed, measured in words per minute (WPM). The result is typically displayed in minutes — sometimes rounded to the nearest half-minute, sometimes shown as a range — and appears at the top of articles, blog posts, and documentation pages worldwide.

The metric matters for a surprisingly psychological reason: people decide whether to start reading based on how long they think it will take. A reader scanning a news feed makes a split-second judgement — if an article says "14 min read" and they have two minutes to spare, they skip it. If it says "3 min read", they click. Publishing platforms understood this early, which is why Medium started displaying reading times in 2013. The feature was quickly copied by Substack, dev.to, Ghost, and virtually every modern CMS.

For writers and content strategists, reading time is a proxy for commitment. A 1-minute read is a snack — low friction, high shareability. A 10-minute read is a meal — it demands attention and signals depth. Neither is inherently better; the right length depends entirely on what you are asking the reader to invest in and what you are giving them in return.

Reading time also affects engagement metrics. Pages where the estimated reading time matches the actual time users spend on the page tend to have lower bounce rates. When readers arrive expecting a 3-minute article and get a 12-minute wall of text, they leave immediately — and that bounce signals a mismatch to search engines. Accurate reading time labels set honest expectations and attract readers who are genuinely willing to spend that time, which keeps your engagement numbers healthy.

Beyond the web, reading time estimates are useful in editorial planning, email marketing (subject lines like "3-minute read inside" improve open rates), course content design, and accessibility planning for users with cognitive load considerations.

How reading time is calculated

The formula is straightforward: reading time = word count ÷ words per minute. If a blog post contains 1,500 words and the assumed WPM is 238, the result is approximately 6.3 minutes. Most tools round this to "6 min read" or display it as "6–7 min".

What counts as a word? In practice, most calculators use whitespace tokenisation — any sequence of characters separated by a space or newline counts as one word. This means hello, hello-world, https://example.com/very/long/url, and $49.99 each count as one word. HTML tags stripped from the content do not count. Numbers count as words. Code snippets embedded in technical articles are typically counted but are read more slowly than prose — a nuance that basic calculators do not account for.

The 238 WPM benchmark comes from a landmark 2019 meta-analysis by Marc Brysbaert, published in the Journal of Memory and Language, which aggregated data from 190 individual studies covering 17,887 participants reading in 17 languages. For English specifically, the median silent reading speed was 238 words per minute. This replaced the older commonly cited figure of 200–250 WPM, which was based on much smaller and less rigorous samples.

WPM is not a fixed property of a person — it varies with content type, fatigue, purpose, and environment. The same reader might skim a news headline at 600 WPM and plod through a legal contract at 80 WPM. The 238 WPM figure represents silent, comprehension-oriented reading of narrative or journalistic prose — the kind of reading most blog and article audiences do. It is a reasonable default but should be treated as an approximation.

Some calculators add extra time for images — Medium, for example, historically added 12 seconds for the first image and 3 seconds for each subsequent image in the post. Code blocks in technical articles are often treated at a slower rate (around 200 WPM or less) because parsing syntax takes longer than reading sentences. This tool uses the standard 238 WPM prose baseline, which is appropriate for most content types.

Average reading speeds by audience

Not all readers move at the same pace. Age, reading proficiency, and the medium of delivery all influence how quickly content is consumed. Understanding this helps you calibrate reading time estimates for your specific audience — a technical reference aimed at expert developers can safely assume a faster reader than a general-interest health blog.

Note that speed readers achieving 400+ WPM in controlled tests often show significantly reduced comprehension at those speeds. For content that needs to be understood and remembered — instructions, legal copy, technical specifications — slower, deliberate reading at 150–200 WPM is more realistic and should be assumed when estimating reading time for high-stakes content.

Reading time for different content types

The "right" reading time is not universal — it depends on format, audience intent, and platform norms. Here is how reading time breaks down across the most common content categories, assuming a reader at 238 WPM.

How major platforms calculate reading time

Reading time estimates are not standardised across publishing platforms — each makes its own assumptions about reader speed, image handling, and content type. This means the same article can show different reading times depending on where it is hosted.

Medium uses 265 WPM as its prose reading speed, slightly above the research average. It adds time for images: 12 seconds for the first image, then decreasing seconds for each subsequent image, eventually reaching a floor of 3 seconds per image. Code blocks are counted at a lower effective rate. Medium displays the result rounded to the nearest whole minute and has shown reading time on every post since 2013. Their rationale was simple: they found users were more likely to start reading when they knew how long it would take.

Substack uses a more conservative estimate — approximately 200 WPM — which means Substack reading times run noticeably longer than Medium's for the same article. Substack's audience skews toward long-form newsletters, so a slightly longer reading time estimate may actually serve as a quality signal rather than a deterrent, communicating depth and seriousness of content.

dev.to uses 250 WPM for prose and applies a flat multiplier for code blocks, treating them as taking longer to parse. The platform targets a developer audience that is comfortable with technical content but still benefits from the expectation-setting that reading time provides.

The takeaway: if you are writing for a specific platform, use that platform's own reading time display as your reference rather than a generic calculator. For general-purpose estimation — drafting content before choosing a platform, planning editorial calendars, or setting reader expectations in your own CMS — the 238 WPM standard is the most defensible baseline, as it comes from the largest and most rigorous research base available.

Tips for writers: optimising for reading time

Reading time is not just a vanity metric — it is a design constraint. Knowing your target reading time before you write helps you structure content appropriately and avoid the two most common length mistakes: writing too little to cover the topic, or padding to hit an arbitrary word count with filler.

• Match reading time to platform norms

  Email newsletters perform best at 1–2 minutes (250–500 words). Twitter threads top out at around 3 minutes before engagement drops. LinkedIn long-form posts work at 3–5 minutes. Medium articles see the highest completion rates at 7 minutes. Know your platform before you set a target length.

• Use reading time as an editorial brief

  Before writing, decide your target. A 4-minute read at 238 WPM means roughly 950 words. That constraint forces you to prioritise — every section has to earn its place. Writers who work without a word target tend to over-explain the easy parts and under-explain the hard parts.

• Front-load your value for longer pieces

  Readers decide whether to continue within the first 10–15% of a piece. For a 10-minute article, that's your first minute — roughly your introduction and first section. Put your most compelling insight, surprising fact, or clearest statement of the problem up front, not in your conclusion.

• Break long reads into scannable sections

  A 12-minute read feels more approachable when it is clearly structured with descriptive headings. Readers mentally chunk it into pieces ("I can read the first two sections now and come back later"). Clear H2s and H3s also help screen readers and search engines parse content hierarchy.

• Check your word count as you draft

  Use a dedicated Word Counter to track your progress in real time. Seeing your live word count prevents the common mistake of writing 1,200 words when you needed 2,000 — and discovering the gap only after you think you are done. The word counter also shows reading time, so you can validate your estimate as you write.