Reading Time Calculator

The Reading Time Calculator converts a word count into an estimated time: how long a text takes to read silently, and — the feature most calculators skip — how long it takes to deliver aloud as a speech, presentation or video script. Paste your text or type a word count, choose a reading speed, and get the estimate instantly.

The maths is simple, which is exactly why it’s reliable: time equals words divided by reading speed. The craft is in the speed you choose. Silent reading of general web content averages roughly 200–250 words per minute for adults; presentation speaking runs noticeably slower at 130–150 wpm because spoken delivery includes pauses, breaths and emphasis; audiobook narration sits around 150–160 wpm. A tool that only offers one “average” quietly gives you the wrong answer for half of all use cases.

Where reading time is used

“6 min read” labels have become standard on blogs because they work: they set expectations, improve engagement, and help readers choose content that fits the moment. Video scripts and webinars need speech estimates to hit time slots. Podcast intros, course modules and accessibility transcripts all get planned against spoken duration. And content strategists use reading time to compare the real depth of pieces in a way that raw word counts don’t communicate to stakeholders.

Who uses this tool

• Bloggers and publishers adding reading-time labels to posts.
• Speakers and presenters timing talks against a slot.
• Video and podcast producers scripting to length.
• UX writers deciding whether a flow is too wordy.

Two paths: paste text and let the tool count, or type a known word count directly. Either way, the choice of speed is the decision that matters.

1. 1
   Open the Reading Time Calculator. Free, instant, runs in your browser.
2. 2
   Enter your text or word count. Paste the full text for a precise count, or type a known word count if you already have one.
3. 3
   Pick the right speed for the job. Silent reading around 200–250 wpm; speech delivery around 130–150 wpm; choose based on how the text will be consumed.
4. 4
   Read the estimate. The tool shows the time to read silently and the time to deliver aloud.
5. 5
   Adjust the speed for your audience. Technical or translated content reads slower; casual consumer content reads faster. Nudge the wpm accordingly.
6. 6
   Round sensibly for display. If you’re labelling a post, round to the nearest minute — “8 min read”, not “8 min 14 sec read”.
7. 7
   Use the number where it helps. Add the label to your template, trim the script to the slot, or flag the 20-minute read that needs restructuring.

How to interpret the results

Silent reading time is what blog labels mean: assume ~225 wpm for a general audience. If your post shows “15 min read” and your audience is busy professionals, expect most readers to skim or bounce — the number is telling you the piece may need a summary, a TL;DR block, or a table of contents (all of which improve engagement on long-form pages).

Speech time is the number that surprises people: a 2,000-word script at 140 wpm is over 14 minutes of talking, not the “8 minutes” a silent-reading estimate would suggest. If your conference slot is 10 minutes, the script needs to be around 1,300–1,400 words at a comfortable pace. Presenters who discover this during rehearsal discover it too late.

What to do next

If you’re adding reading-time labels to a blog, automate the display in your CMS from the word count rather than updating it manually. Then check the content itself: the Readability Checker tells you how hard the text is to process, and the Word Counter gives the underlying counts including characters for meta fields.

Example 1 — labelling a blog post

A 1,580-word guide at 225 wpm is a “7 min read”. The label sets expectations and measurably improves engagement for content-heavy blogs. Round, display, and keep the estimate consistent across the site so labels stay comparable.

Example 2 — fitting a conference talk

You have 15 minutes and a draft script of 2,900 words. At 140 wpm, that’s roughly 21 minutes of delivery — 40% over. Cut to ~2,000 words, or plan to speak at a pace you can’t sustain (and shouldn’t try). The calculator catches this before rehearsal instead of during it.

Example 3 — scripting a product video

A 90-second product explainer needs roughly 200–210 words at 140 wpm. The script lands at 340 words. Something must go: the calculator turns a vague “it’s too long” into an exact target — cut 130 words.

Calculate reading time whenever length is consumed as time: blog labels, documentation banners (“this guide takes about 20 minutes”), course modules, email newsletters (reading time predicts completion), video and podcast scripts, webinar run-throughs, and voice-over copy. It’s also a planning tool: a content brief that says “aim for an 8-minute read” (~1,800 words) communicates audience commitment better than a raw word count.

Remember the estimate is a model, not a measurement. Real readers skim, backtrack and pause; real speakers improvise, pause for laughs and speed up when nervous. Use the number to plan, and use real engagement data (or a stopwatch and a rehearsal) to verify.

• Using silent-reading speed for scripts. 225 wpm is a reading speed, not a speaking speed. Scripts timed at silent speeds run 40–60% over when delivered aloud.
• Displaying false precision. “6 min 38 sec read” implies a measurement you can’t make. Round to whole minutes.
• One speed for every audience. Technical documentation, legal content and non-native readers all run slower than the average; casual lifestyle content runs faster.
• Treating a long reading time as a badge of honour. A 25-minute read is a commitment request. Long is fine when the intent demands depth; otherwise the number is telling you to edit.

• Use ~225 wpm for general web reading labels, ~200 wpm for technical audiences, and 130–150 wpm for anything delivered aloud.
• Keep the calculation method consistent across your site so labels are comparable between posts.
• For long guides, add a table of contents and a short summary — the reading-time label then invites rather than warns.
• Rehearse scripts aloud once before finalising; the calculator gets you within 10%, a rehearsal gets you exact.
• Track whether “min read” labels affect engagement on your audience — most sites see a benefit, but your data wins.

• It’s an estimate. Individual reading speeds vary enormously (150–400+ wpm); the tool reports the centre of the distribution, not your reader.
• Format isn’t modelled. Code blocks, images, tables and interactive elements consume time that pure word counts miss.
• Skimming isn’t reading. Many visitors read 20% of a page. The label is a promise about full reading, which is still useful — just know what it claims.

• My label disagrees with another site’s calculator. Different tools use different wpm assumptions (200 vs 225 vs 250). Any consistent choice is defensible; consistency matters more than the exact figure.
• The speech estimate seems too long. It probably isn’t — people systematically underestimate spoken duration. Record yourself reading one paragraph and time it; your natural pace is usually slower than expected.
• Reading time for a PDF or slides? Paste the text extracted from the file. Slide decks need per-slide reading plus transition time — treat the tool’s number as a floor.