Script Timer: How to Time Your Video Script Perfectly Before Recording
I once wrote what I was sure was a tight 60-second script, sat down to film it, and clocked in at 1:34. Not close. By the time I trimmed it down, re-filmed it, and re-edited the cut, I'd burned almost an hour on a video that should have taken fifteen minutes.
That's the thing nobody tells new creators: script timing isn't an afterthought, it's pre-production. Get it wrong and the cost shows up later, multiplied, in the editing room.
Here's how to actually estimate your duration before you press record — and why most "word counter" tools get it wrong.
---
Start With Words Per Minute, Not Word Count
The number that matters is Words Per Minute (WPM), not raw word count. Most people speak somewhere in the 130–150 WPM range when they're talking naturally to a camera rather than reading a press release.
The formula is simple:
Duration (seconds) = (Word Count ÷ Speaking Speed) × 60
At a baseline of 140 WPM, here's roughly what that buys you:
| Word Count | Estimated Duration | Ideal Platform |
|---|---|---|
| 35 words | 15 seconds | TikTok hook / ad intro |
| 70 words | 30 seconds | Quick TikTok / Instagram Reel |
| 140 words | 60 seconds | Maximum YouTube Short / Reels |
| 280 words | 2 minutes | LinkedIn tip / product update |
| 700 words | 5 minutes | Standard YouTube tutorial |
| 1,400 words | 10 minutes | Deep-dive documentary / podcast |
Treat this table as a starting point, not gospel — your actual pace depends on you.
Why a Plain Word Counter Will Lie to You
Google Docs' word count, or any generic online counter, will give you a number. It just won't be a number you can trust, because none of them account for how people actually talk:
- Punctuation changes pace. A sentence stitched together with three commas reads slower than a clean fifteen-word line with none.
- Delivery isn't constant. You naturally slow down on a complicated point and speed up while telling a story — the average hides both.
- Transitions cost seconds. A slide change, a B-roll cut, a beat before the next point — these aren't in the script, but they eat into your runtime.
[!WARNING]
Relying purely on a word-count estimate tends to undercount your real runtime by 10–20%. Build in a buffer.
Time Sections, Not the Whole Script
The fix most people skip: stop timing your script as one block. Break it into Intro, Step 1, Step 2, Conclusion — whatever your structure is — and time each piece on its own.
Why bother? Two reasons:
1. You'll spot exactly which section is dragging instead of guessing.
2. You get checkpoints. Mid-recording, you can glance at a timer and know immediately whether you're on schedule or need to pick up the pace.
This is the whole premise behind ScriptPacer.com — it parses your script using --- dividers, runs the math per section instead of as one lump average, and gives you a live read on pace while you're recording, not just a number before you start.
If you've been burned by a script that ran long once already, it's worth five minutes to paste it in and see where the time is actually going.