Reading Time Calculator

What is a Reading Time Calculator?

A reading time calculator estimates how long a piece of text will take to read, based on its word count and a reading speed measured in words per minute. Paste or type any text in, and the tool instantly reports the estimated reading time, the estimated speaking time if the same text were read aloud, and a full breakdown of the text itself — word count, character count, sentence count, and average word length. Reading speed can be set to a slow, average, or fast preset, or fine-tuned with a slider for a more personal estimate.

It's built for anyone who publishes or edits text and wants readers to know what they're getting into before they start: bloggers adding a "5 min read" label to an article, writers pacing a speech or presentation against a time limit, students estimating how long an assigned reading will take, and editors checking whether a piece runs too long for its intended format.

How to use it

How the calculation works

Reading time is calculated by dividing the total word count by a reading speed measured in words per minute, then converting that figure into minutes and seconds. The three presets — slow (130 wpm), average (200 wpm), and fast (300 wpm) — reflect the typical range of adult silent reading speeds, with 200 words per minute widely cited as a reasonable average for general-audience text. Speaking time is calculated the same way but against a fixed rate of about 130 words per minute, which approximates a comfortable, clearly-paced speaking tempo — noticeably slower than silent reading, since spoken words take longer to articulate than the eye takes to scan them. Word count is determined by splitting the text on whitespace, sentence count by splitting on sentence-ending punctuation, and average word length by dividing the total non-space characters by the word count.

Features & benefits

Why people calculate reading time

The most visible use is the "X min read" label seen at the top of blog posts and articles, which research suggests can influence whether a reader decides to start reading at all — a number that feels achievable encourages a click, while an unexpectedly long one can turn a reader away before they've even seen the content. Content teams also use reading time estimates to keep newsletters, emails, and landing pages within an attention span that won't cause a reader to abandon partway through.

Speaking time matters just as much in a different context: anyone rehearsing a speech, a conference talk, a podcast script, or a video voiceover needs to know whether the script fits inside an allotted time slot before they get on stage or start recording, and trimming a script after the fact is far easier than discovering a time overrun live. Teachers and students use the same numbers to gauge how long an assigned reading or a prepared presentation will actually take.

Why this runs entirely in your browser

Text pasted into this tool is often unpublished — a draft, a script, an internal document — so nothing typed or pasted here is ever sent to a server. Every calculation, from the word count to the final time estimate, happens locally in JavaScript the moment the text changes, which means the tool keeps working offline once the page has loaded and nothing persists after the tab is closed.

Getting a more accurate estimate

The right reading speed depends heavily on the audience and the material: technical or unfamiliar content is read more slowly than a casual blog post, and a non-native reader may read closer to the slow preset than the average one. If a specific audience's typical pace is already known, dragging the slider to that value gives a more useful estimate than relying on a generic preset. For speaking time, remember the 130 wpm baseline assumes a clear, unhurried pace with normal pauses — a script read faster or with less pausing will finish sooner, so treat the number as a solid starting estimate rather than an exact rehearsal timer.