Reading Time Calculator
Prefer pasting text? Use the Word Counter tool. Images add ~12s for the first, then less (Medium-style).
Results
FREE TOOL · NO SIGN-UP
This reading time calculator tells you how long a piece of content takes to read silently and to read aloud. Enter the word count, set a reading speed and add the number of images, and you get the total reading time, the speaking time and a ready-to-use “X min read” label. It’s built for bloggers, editors, speech writers and anyone who wants to set honest expectations before a reader starts.
How Reading Time Is Calculated
Every reading time estimate starts with the same idea: divide the number of words by how many words a person reads per minute. The rest is about adjusting that baseline so it matches how people actually move through a page.
Words ÷ WPM
The core formula is simple: reading time = word count ÷ words per minute (WPM). A 1,500-word article read at 238 WPM takes a little over six minutes. The calculator uses 238 WPM as its default because it is a commonly cited average for adults silently reading non-fiction in English, but you can change it to anything you like.
The result is shown in minutes and seconds, so you can see the difference between a 4-minute and a 4-minute-50 read. That precision is useful for scripts and lessons. For a blog label, the tool rounds up to the next whole minute.
Images and code adjustments
Readers pause on images, so the calculator adds time for each one, Medium-style. The first image adds 12 seconds, the second 11, the third 10 and so on, until each extra image adds a floor of 3 seconds. That pattern reflects the fact that people look closely at the first few visuals and skim later ones.
Code blocks, tables and charts also slow readers down, but they vary too much for a fixed rule. If a post is heavy on code or data, lower the WPM setting a little rather than guessing a per-block penalty.
How to Use the Reading Time Calculator
The tool works live, so results update as soon as you change a number.
Step 1 – Enter your word count
Type the number of words into the Word count field. If you have the draft but not the count, paste it into our Word Counter first and copy the total across. Only count the main body; navigation, footers and comments don’t belong in the estimate.
Step 2 – Set reading speed
The Reading speed field defaults to 238 words per minute. Lower it for dense, technical or academic material, or for an audience reading in a second language. Raise it for light, skimmable content such as listicles or news briefs.
Step 3 – Check aloud time
Look at Speaking time (130 wpm) in the results. It uses a fixed, comfortable speaking pace, so it’s a quick way to see whether a script, podcast segment or talk will fit your slot. Text only shows the reading time without image adjustments.
Step 4 – Add the label to your post
The Display label gives you a rounded-up value such as “7 min read”. Add it near the title or byline in your theme or post template. Use the Clear button to reset the fields for the next article.
Reading Speed by Audience and Format
One number never fits every reader. Treat the default as a starting point and adjust it for who’s reading and on what device.
Technical vs casual content
Technical guides, legal pages and research summaries need more attention per sentence. Readers stop to reread definitions, follow steps or check a number, so a lower WPM gives a more honest estimate. Casual content works the other way. People skim headings, jump to the part they need and skip examples they already understand, so a higher setting is closer to reality.
If your site mixes both, pick a speed per content type instead of a single site-wide figure. A tutorial category and a news category can reasonably use different settings.
Mobile reading
On phones, the screen shows fewer words at once and people read in shorter bursts, often with interruptions. That doesn’t always mean slower reading, but it does mean long, unbroken paragraphs feel longer than the clock says. If most of your traffic is mobile, keep paragraphs short, use descriptive subheadings and check that the label still feels fair when you scroll through the post on a phone.
Timing Speeches and Presentations
Reading aloud is much slower than reading silently, which is why the calculator shows speaking time separately.
Speaking WPM ranges
The tool’s speaking estimate uses 130 words per minute, a relaxed and clear pace for presentations, voice-overs and podcasts. Real speakers vary. Nervous presenters often speed up, while people explaining something complex slow down. If you know your own pace, record yourself reading one paragraph, count the words and set your expectations from that. For a talk with a strict limit, aim for a script that lands a little under the time so you have room to breathe.
Pausing and slides
Scripts don’t include the silence between sentences, slide transitions, demos or audience questions. Each pause is small, but they add up quickly. Plan for them by trimming the script rather than speaking faster. A good habit is to rehearse with the slides once and compare your actual time with the estimate, then adjust your word count for the next draft.
Reading Time Labels and Engagement
A visible reading time helps readers decide whether to start now or save the post for later.
Where to place the label
Put the label where people look before they commit: next to the title, the author name or the publish date. Many themes and plugins can show it automatically; if yours doesn’t, paste the value from the Display label result. Keep the format consistent across the site, for example “6 min read”, so readers learn to trust it.
Matching length to intent
A label works best when the content length fits what the searcher wanted. Someone looking for a quick answer appreciates a 2-minute read with the answer near the top. Someone researching a decision will happily commit to 12 minutes if the page is thorough. Use the estimate as a check: if a “quick tip” post shows 9 minutes, it might need trimming or splitting.
Reading Time Estimate Mistakes
One speed for every audience
Using the same WPM for a developer guide and a lifestyle post makes one of the labels inaccurate. Set speed by content type.
Ignoring images and tables
A post with fifteen screenshots takes longer than its word count suggests. Enter the real image count and slow down the WPM for heavy tables.
Padding to look longer
Adding filler to push the label up doesn’t help anyone. Readers notice, and they leave. Write until the question is answered, then measure.
Set Honest Expectations for Readers
Readers give you their time when they know what they’re getting. Use the reading time calculator to label posts accurately, time your scripts and spot drafts that run too long. Get an exact count first with the Word Counter, count lines in a script or list with the Line Counter, and test how easy the copy is to follow with the Readability Checker. You’ll find more free writing and SEO tools in the FHSEO Hub free SEO tools collection.
