Free · no sign-up · no upload
Script Timer
Will your script fit the cut? Estimate spoken duration from word count, reading speed and planned pauses.
This is an estimate, not a performed timing. Action descriptions and scene headings should not be included in spoken words.
Timing is only the first pass.
Keep this draft and its target when you continue into diagnosis and revision.
See the calculation in use
From spoken words to a practical timing check.
Browse three real product screenshots, then try the same calculation with your own script above.
75 spoken words at 150 WPM give an estimated read time of 30 seconds before planned pauses.
At 180 WPM with no planned pauses, the same 75-word script has an estimated read time of 25 seconds.
Adding a three-second planned pause brings the estimate to 28 seconds. Use the live calculator above for your own script.
Swipe, scroll, use the thumbnails or select a slide and use your arrow keys. No autoplay.
Read the visual guide
- Paste 75 spoken words into the timer.
- At 150 WPM with no planned pauses, the estimated read time is 30 seconds.
- Change the reading speed to 180 WPM; the spoken estimate becomes 25 seconds.
- Add a three-second planned pause; the final estimate becomes 28 seconds.
How the estimate works
The basic calculation is words ÷ words per minute × 60. A 75-word script at 150 WPM takes about 30 seconds before pauses.
Measured delivery
Useful for deliberate explanations, emotional scenes and space between ideas.
Natural starting point
A practical baseline for many conversational voice-overs. Test your own read.
Energetic delivery
Useful for fast short-form reads, but clarity matters more than fitting every word.
Frequently asked questions
Is 150 words always one minute?
No. It is one minute at exactly 150 WPM with no pauses. Record yourself once to find your natural rate, then adjust the slider.
Does Narrascout store the script I paste here?
No. This calculator runs entirely in your browser. It does not send the text to Narrascout or an AI model.
Can it time a feature screenplay?
It estimates spoken text, not screen time. Action, silence and visual sequences make word count unsuitable for feature runtime.