Script Timer: How to Calculate and Control Your Video's Running Time

The Script Timer Formula

You don't need a dedicated tool to time a script. The math is simple:

Script duration = word count ÷ speaking WPM

The only variable you need to calibrate is your personal speaking pace. If you don't know yours, record yourself reading a 300-word passage aloud and time it. Divide 300 by the number of minutes to get your WPM. Most content creators deliver at 120–160 WPM when recording scripted video.

As a default baseline, use 130 WPM — it's the lower end of comfortable scripted delivery and gives you a small buffer. If your actual pace is faster, your video will run slightly shorter than planned. Better to run short and cut cleanly than to run long and scramble.

Word Count Targets by Video Length

Here's a quick reference built from the 130 WPM baseline, which works for most talking-head and scripted educational content:

Analysis of 500 YouTube educational videos by TubeBuddy in 2024 found that videos between 7–12 minutes generate 40% more ad revenue per view than videos under 5 minutes, primarily because they cross the mid-roll ad eligibility threshold. For monetized content, this means targeting a minimum of 900–1,300 words at 130 WPM to comfortably reach the 7-minute mark.

Why Formula-Based Timing Isn't Enough

Script timers are useful for drafting, but your actual recording pace varies more than most creators expect. In my experience building courses, the same script recorded on different days can vary by 10–20% in duration. A 5-minute estimate might record at 4:20 on a high-energy day or 5:45 when you're speaking more carefully.

Three things consistently push actual recording time above the formula estimate:

• Planned pauses: Dramatic pauses, letting a visual settle on screen, or waiting for a demonstration to complete — none of these are words, but they all take time.
• Delivery emphasis: Slowing down for key points, repeating important phrases, or building tension in a story all extend real duration beyond word-count estimates.
• Natural variance: Hesitations, re-reads, or the micro-pauses between sentences that appear in natural speech but not in the word count.

My rule: budget 10–15% more words than the formula suggests, then trim in editing if needed. It's faster to cut than to re-record a section that ran short.

Using a Teleprompter as a Live Script Timer

The most accurate way to time a script before recording is to read it aloud through a teleprompter. This captures your actual delivery pace — pauses, emphasis, natural rhythm — rather than just dividing word count by an average WPM estimate.

Teleprompter-Scrolling Scripts shows an estimated reading time based on your set scroll speed as you write. Set your scroll speed to match your measured speaking pace, then check the timer at the bottom. If the script shows 6:40 for a 5-minute target, trim before you record rather than discovering the overrun in post.

This single-pass calibration step — taking 5 minutes before every recording session to do a live read-through at your actual pace — has saved me countless hours of re-recording and editing.

Script Timing for Different Content Formats

Not all video formats follow the same WPM norms. Here's what to expect across common content types:

• YouTube talking-head / educational: 130–150 WPM, conversational with natural pauses. Scripts typically run 10–15% longer than their word-count estimate due to pauses.
• Corporate training video: 120–130 WPM, more deliberate pace. Allow 15–20% buffer over formula estimate.
• Online course modules: 110–130 WPM, intentionally slower for complex concepts. Budget 20% over estimated duration for curriculum-dense content.
• News / broadcast scripted read: 150–180 WPM, very compressed. Broadcast scripts are written to precise second-counts, not word counts.
• Podcast monologue: 140–160 WPM, typically faster and more conversational. Script timing is less critical for audio-only formats since editing is easier.

Wistia's 2025 Video Benchmark Report found that viewer engagement drops sharply after the 8-minute mark for instructional content, with average completion rates falling from 68% at 5 minutes to 41% at 12 minutes. For course creators, this suggests front-loading key information and targeting 5–8 minute modules to maximize completion rates and course progression.

Script Length vs. Actual Delivery Length

One of the most persistent mistakes creators make is trusting the word count alone without accounting for delivery overhead. A script timer gives you a clean estimate, but your video's final runtime is almost always longer than the math suggests. That gap — between the script reading timer estimate and your actual recorded duration — is where most post-production headaches come from.

The key distinction is that your script captures spoken words, not dead air. A 650-word script at 130 WPM gives you five minutes on paper. In practice, you'll add 30 to 60 seconds of pauses, visual holds, and natural breath gaps that never appear in the word count. For a video script timer to serve you accurately, you need to build this buffer into your target. Aim for a script that times out 10–15% shorter than your target video length, then let your natural delivery fill the remainder.

For presenters who use a script reading app during recording, scroll speed is the real pacing control. Setting your scroll speed to match your comfortable spoken rate — rather than your maximum reading rate — gives you a speech timer you can trust on set.

Common Script Timing Mistakes to Avoid

After reviewing hundreds of creator workflows, the same script timer errors come up repeatedly. The most common: calculating word count from a draft that still includes notes, headers, and stage directions. Your video script timer should only count words you actually speak. Strip out brackets, action cues, and b-roll notes before running any timing estimate.

A second common error is calibrating your reading speed timer on a cold read rather than a warm delivery. Your first read-through of a script is almost always slower than your actual recording take. Measure your pace after you've rehearsed a section at least once — that's the number worth building your word-count targets around. If you use a teleprompter app with an auto-scroll timer, do a full pass at recording pace before locking in your script length.

Finally, avoid using a single WPM figure for all content formats. Your natural pace for a casual YouTube explainer is faster than your pace for a technical walkthrough or an online course module. Keep a simple log: record your WPM for each content type you produce and update your script reading timer baseline per format. It takes five minutes to set up and saves you re-records every week after that.

Using a Script Timer for Zoom Presentations and Live Video

A script timer isn't only useful for pre-recorded content. For live video presentations — webinars, Zoom calls, LinkedIn Live sessions — getting your script length right before going live is even more critical because you can't cut in post. A video script timer lets you confirm that your prepared remarks will land within your allotted slot before you're in front of an audience.

For live formats, calibrate your speech timer using a slightly slower pace than your normal recording WPM. Live presenting adds cognitive load — managing slides, reading chat, watching your own feed — which naturally slows delivery by 5–10%. If your recorded pace is 140 WPM, plan your live script using 125–130 WPM to account for the real-time demands of a live session.

If you're using a teleprompter for Zoom video calls, the scroll speed itself becomes your live pacing tool. Set it slightly slower than you think you need, and you'll arrive at the end of your material at exactly the right moment rather than running over and having to cut your close short. Check your speech word count against your time slot before every live session — it's a two-minute check that prevents the most common live presentation problem there is.

Frequently Asked Questions