120 WPM calm explanation
Good for educational explainers, complex products, and videos with detailed screens.
Video narration timing
Estimate voice-over length while protecting time for visuals, product screens, diagrams, and transitions.
Estimate explainer narration length with pauses, visual transitions, and target video duration.
Your script is processed locally in your browser. It is not uploaded to a server.
Explainer timing must leave room for viewers to understand what they see, not just what they hear.
| Video target | Words at 140 WPM | Scene guidance |
|---|---|---|
| 30 seconds | 70 words | 1 idea, 3-4 scenes |
| 60 seconds | 140 words | Problem, solution, proof, CTA |
| 90 seconds | 210 words | Add one walkthrough beat |
| 2 minutes | 280 words | Use 6-8 visual scenes |
| 3 minutes | 420 words | Break into short chapters |
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.
Good for educational explainers, complex products, and videos with detailed screens.
A practical default for SaaS walkthroughs and product explainers with moderate visual movement.
Use for lighter promotional explainers, but keep sentences short and pauses intentional.
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.
Your script is processed locally in your browser. It is not uploaded to a server.
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.
Often yes. Viewers need time to interpret visuals, product screens, diagrams, and transitions.
Start with 5% to 10% for simple visuals and more for detailed screens or diagrams.
Remove setup the visuals already show, combine repeated benefits, and keep each scene tied to one idea.