Text

Reading Time Calculator

Paste a text and get word count, character count and estimated silent reading time. Built for blogs, newsletters, social posts and content planning.

Instant🔒In your browserNo signup
Live

Why estimate reading time

Showing "5 min read" before an article is one of the simplest, highest-leverage UX wins. Readers decide in seconds whether to read now, later or never. Without a concrete number, they apply a pessimistic bias: "this'll be long" and bounce. With a clear time, the math changes: "I have five minutes, let's go".

The standard speed and why it matters

The most common standard is 238 words per minute (Brysbaert, 2019), the average silent reading speed for an adult on non-technical material. For dense academic text, drop to 150-180; for fast fiction, go up to 250-280. For an international audience reading English as a second language, stay around 200. Calibrating well matters: underestimate and you disappoint, overestimate and you look like you don't respect the reader's time.

Benefits of showing the time

  • Higher CTR — listings with "X min read" get more clicks.
  • Lower bounce — readers commit to a known horizon.
  • Better completion rate — readers who knew the time finish more articles.
  • Indirect SEO — Google rewards time on page and pageviews per session.
  • Honest UX — signals respect for the reader's time.

How to measure well

The math is simple: word count divided by reading speed. But nuances matter. Images, code blocks, tables and embedded videos don't count as words but consume time. Common convention: add 12 seconds per image and 5 seconds per short code block. Round to 15 seconds for complex tables. If your post is multimedia-heavy, this detail is the difference between an honest "5 min" and an optimistic one.

Real use cases

  • Blogs — visible label at the top of the post.
  • Newsletters — before the CTA, "Time: 4 min".
  • Technical documentation — helps the reader plan.
  • Internal manuals — predictable onboarding.
  • Social media — if your LinkedIn post hits 8 min, it belongs on a blog, not a feed.

Reading time as diagnostic

If your article comes out at 12 minutes, it's probably too long. Most web readers don't push past 7 minutes. Use this tool as a thermometer: if it's over 8, consider splitting into parts, adding a table of contents, breaking with images, or simply trimming. A well-written 5-minute piece beats a 12-minute one full of filler.

Difference vs. speaking time

Silent reading time is ~238 wpm. Spoken-word time is much slower: ~130 wpm conversational, up to 160 if you talk fast. If you'll read a text aloud (presentation, podcast, video), use a speaking time calculator, not this one. Mixing them up is a common mistake.

FAQ

Which reading speed does it use?

Default 238 wpm, adjustable for your audience.

Is it useful for newsletters?

Yes. Showing reading time raises CTR and lowers bounce.

How are words counted?

Split by whitespace, empty lines ignored. Works for English and Spanish.

Was this generator useful?