Video narration timing

Explainer Video Script Timer

Estimate voice-over length while protecting time for visuals, product screens, diagrams, and transitions.

Explainer Video Script Timer

Estimate explainer narration length with pauses, visual transitions, and target video duration.

Speaking speed
Target duration

Optional. Set minutes and seconds to 0 to ignore target comparison.

Your script is processed locally in your browser. It is not uploaded to a server.

Voice-over timeVisual transition bufferTarget video presets

Explainer video word count table

Explainer timing must leave room for viewers to understand what they see, not just what they hear.

Video targetWords at 140 WPMScene guidance
30 seconds70 words1 idea, 3-4 scenes
60 seconds140 wordsProblem, solution, proof, CTA
90 seconds210 wordsAdd one walkthrough beat
2 minutes280 wordsUse 6-8 visual scenes
3 minutes420 wordsBreak into short chapters

How to use this explainer video script timer

Paste the narration script, choose the video type, set the voice-over pace, add a pause buffer, and select a target video duration. The timer estimates narration time, visual transition time, total runtime, target comparison, and words to cut or add. It is built for product explainers, app walkthroughs, SaaS videos, onboarding clips, and educational explainers.

Explainer videos need pauses because the viewer is decoding visuals while listening. A product screen, diagram, process animation, or before-and-after comparison may need a quiet beat before the next sentence. If the voice-over runs continuously, the edit can feel rushed even when the WPM looks normal.

Recommended voice-over settings

120 WPM calm explanation

Good for educational explainers, complex products, and videos with detailed screens.

140 WPM natural voice-over

A practical default for SaaS walkthroughs and product explainers with moderate visual movement.

155 WPM energetic promo

Use for lighter promotional explainers, but keep sentences short and pauses intentional.

Match narration to visual scenes

Draft the script scene by scene. Each sentence should have a visual job: introduce a pain point, show a product action, clarify a diagram, or reinforce the outcome. If a sentence cannot be matched to a scene, it may be voice-over filler. The timer helps you convert those choices into runtime before the edit begins.

To shorten a script without losing clarity, remove setup that the visual already explains, combine repeated benefits, and replace abstract claims with one concrete action. Short explainers need fewer ideas and simpler sentence shapes. A 60-second video usually cannot support a full origin story, product tour, proof section, and detailed CTA.

Common explainer timing mistakes

  • Timing only the voice-over and forgetting scene transitions or screen comprehension.
  • Trying to fit too many product benefits into a 60-second video.
  • Writing long sentences that leave no clean edit points.
  • Using a fast promo read for a technical walkthrough.
  • Cutting pauses first instead of removing repeated ideas.

Privacy note

Your script is processed locally in your browser. It is not uploaded to a server.

FAQ

How many words fit in a 60-second explainer video?

At 140 WPM, about 140 words fit in 60 seconds before extra visual pauses. Many explainers work better with 110 to 130 words plus visual breathing room.

Should explainer narration be slower than a normal speech?

Often yes. Viewers need time to interpret visuals, product screens, diagrams, and transitions.

How much pause time should I add for visuals?

Start with 5% to 10% for simple visuals and more for detailed screens or diagrams.

How can I shorten an explainer video script?

Remove setup the visuals already show, combine repeated benefits, and keep each scene tied to one idea.