How long will it take to read this? Or speak it? Or type it?
Paste your text in and get three numbers: reading time (at 200 words per minute), speaking time (at 130 WPM), and typing time (at 40 WPM). Word and character counts show up alongside them. Everything updates as you type.
Those “5 min read” labels on blog posts? This is how they’re calculated. And it’s surprisingly useful for presentation prep too, I’ve seen people discover their “10-minute talk” was actually 25 minutes of material.
What it calculates
- Reading time at 200 WPM (the standard for adult silent reading)
- Speaking time at 130 WPM (accounts for natural pausing and articulation)
- Typing time at 40 WPM (average touch-typing speed)
- Word and character counts for reference
- Real-time updates, no button to click
- Runs in your browser, text stays private
The math in practice
A 1,500-word blog post? About 7.5 minutes to read silently. Roughly 11.5 minutes if you’re reading it aloud. And about 37.5 minutes to type from scratch.
Planning a 5-minute presentation? You’ll want around 650 words of script. Building a 10-minute segment? Aim for roughly 1,300 words, and add buffer time for slides and audience interaction.
When you’ll use this
Blog post “read time” labels: these genuinely increase engagement. Readers appreciate knowing what they’re getting into. Paste your draft, grab the number, add it to your post.
Presentation planning: the speaking time estimate saves you from the embarrassment of running over (or under) your allotted slot. Just remember that these are averages. Add a few minutes for pausing and Q&A.
Podcast scripting: before you hit record, check how long your scripted segment actually runs. Beats finding out you’re 20 minutes short during recording.
Email length: here’s a useful benchmark: if your email takes more than 2 minutes to read, most people won’t finish it. Paste it in and check.
Academic work: estimating reading time for assigned papers, or verifying your oral presentation fits the time limit.
Pair this with the Word Counter for full content metrics and the Sentence Counter if you want to analyze sentence structure too.
One thing to keep in mind: these are averages. Dense technical writing takes 25-50% longer to read than conversational content. If you’re writing about quantum physics, add some buffer to the estimate.
FAQ
Is 200 WPM accurate?
It’s the widely accepted average for adult silent reading of standard prose. Individual speeds range from about 150 to 300 WPM depending on the reader and how technical the content is. It won’t be perfect for everyone, but it’s a solid baseline.
Why is speaking slower than reading?
Your mouth can’t keep up with your eyes. Speaking averages about 130 WPM because of natural pauses between phrases and the physical act of articulation. Professional speakers might hit 150 WPM, but conversational speech usually falls in the 120-140 range.
Can I plan presentations with this?
Absolutely. The speaking time gives you a direct estimate. For a 10-minute slot, write about 1,300 words. Leave room for transitions and questions.
Is my text private?
Yes. All calculations happen in your browser with JavaScript. Nothing gets transmitted.
What about SEO content length?
There’s no magic number, but studies show top-ranking pages often fall in the 1,500-2,500 word range: that’s about 7-12 minutes of reading. The Word Counter can help you hit your target.