Skip to content

Creator Tools

Words to Time Calculator

Paste a script or enter a word count to estimate how long it takes to read silently, read aloud, or record as narration — with pace presets from slow documentary voice-over to fast speech.

Paste text or enter a word count to see the timing.

How the Tool Works

  1. Paste your script or type a word count directly.
  2. Pick a pace: slow narration (~100 wpm), conversational (~130 wpm), presentation (~150 wpm), fast (~180 wpm), or silent reading (~238 wpm average adult).
  3. The tool reports duration in minutes and seconds, plus character, word, sentence, and paragraph counts for the pasted text.
  4. Adjust the words-per-minute manually when you know your own delivery speed from previous recordings.
Formula & Technical Standard
Time (minutes) = words ÷ words per minute. Silent-reading research commonly cites 200–250 wpm for non-fiction; narration typically runs 130–150 wpm.

Typical Use

YouTube video script
Input: 1,200 words at 140 wpm narration
Output: ≈ 8 minutes 34 seconds
Most scripted YouTube narration lands between 130 and 150 wpm; 1,200 words is a standard 8–9 minute video.
Blog post read time
Input: 2,400 words silent reading at 238 wpm
Output: ≈ 10 minutes
The 238 wpm figure comes from a large 2019 study of silent reading across languages — faster than most people assume.

Common Questions

What is the average speaking rate?

Conversational English averages 120–150 words per minute; audiobook narration is usually 150–160 wpm; presentations sit near 100–130 wpm once pauses are counted. Any of these is a valid input — measure your own pace once and reuse it.

Do pauses, slides, or b-roll change the estimate?

Yes. The calculation covers spoken words only. Add time for pauses, transitions, and on-screen moments: a common correction is 10–20% extra for edited videos and up to 30% for presentations with slide changes.

Why does my recorded video run longer than predicted?

Scripts are usually read with emphasis, breath, and retakes. If your recordings consistently run long, reduce the wpm setting by 10–15% — or accept that the first read is always slower than the estimate.