YouTube Script Length Calculator: Words, Minutes, and Speaking Speed

How long will this script be on screen? It's one of the most practical questions in scriptwriting, and one of the easiest to get roughly right. You need one formula, an honest estimate of your speaking pace, and an understanding of what changes the number.

Everything here is an estimate. Your finished runtime depends on delivery, editing and visuals, so treat these figures as planning targets rather than predictions.

The Formula

The core calculation is simple:

words = minutes × words per minute

And in reverse, to estimate the runtime of a script you've already written:

minutes = words ÷ words per minute

So a 1,200-word script read at 150 words per minute comes out at about 8 minutes of narration.

The tricky part is the words-per-minute figure. Many narrators land somewhere around 130 to 170 words per minute, but individual pace varies widely with personality, topic and style. A calm explainer on a technical subject might speak slower than this; an energetic commentary channel might speak faster.

Reference Table: Duration to Word Count

The table below uses three illustrative paces: deliberate (130 wpm), moderate (150 wpm) and brisk (170 wpm). These are rough, round figures for planning, not standards.

These numbers count narration only. They assume continuous speech with no extra pauses, which is not how most finished videos work.

What Changes Your Real Runtime

A script is a plan for audio. The finished video adds and removes time in ways a word count can't see.

Speaking pace

Your natural pace is the biggest variable. It also shifts within a single video: people often speed up through familiar material and slow down for explanations or emotional moments. Excitement tends to make delivery faster; nerves can go either way.

Pauses

Deliberate pauses after a key point, a punchline, or a question add up. A script with lots of dramatic beats will run longer than its word count suggests.

B-roll and demonstrations

Any moment where the visuals carry the story without narration adds time. A cooking video might spend a stretch just showing dough being kneaded. A tutorial might show a full process on screen. Mark these in your script, such as [DEMO: 20 SEC], so you can account for them.

Editing style

Tight, jump-cut editing removes breaths and hesitations, which can make the finished video shorter than the raw read. A more relaxed edit that keeps natural pauses runs closer to, or longer than, the estimate.

Ad-libs and retakes

If you improvise around your script, expect the runtime to drift upward. If you tend to trim as you record, it may drift down.

How to Measure Your Own Pace

A personal number beats any general range. Here's a simple way to find yours:

1. Pick a passage of a few hundred words from a script you've written. Your own writing matters, because you read it the way you'd actually deliver it.
2. Record yourself reading it in your normal on-camera voice, not a careful reading voice.
3. Time the recording from first word to last.
4. Divide the word count by the time in minutes.

Hypothetical example: a 400-word passage takes 3 minutes and 20 seconds to read. That's about 3.33 minutes, so 400 ÷ 3.33 gives roughly 120 words per minute, a slower-than-average pace that would mean writing fewer words for each minute of video.

Do this two or three times with different passages and take the average. Then, after you publish a few videos, compare each script's word count with the finished runtime. That ratio tells you how much your pauses, visuals and edits typically add, which is more useful than any table.

Using the Numbers When You Plan

Once you have a pace, use it to budget the script rather than to police it.

• Set a range, not a target. "Roughly 1,100 to 1,300 words" is more useful than "exactly 1,200."
• Budget by section. Give the hook only a small slice, the main sections most of the words, and the ending a short stretch.
• Check after drafting. If a draft is far over, look for repeated points and long setups before cutting examples.

Hypothetical example: you're planning an 8-minute tutorial and your measured pace is about 140 words per minute. That gives a narration budget of roughly 1,120 words. You also plan a 30-second on-screen demo with no voiceover, so trim the narration target to around 1,050 words. A sensible split might look like this:

Hook             about 60 words
Introduction     about 90 words
Section 1        about 280 words
Section 2        about 280 words
Section 3        about 220 words
Payoff and end   about 120 words

If your first draft comes in at 1,600 words, you know before recording that something has to go, which is far cheaper than discovering it in the edit.

For the full process this fits into, see the guide on how to write a YouTube script from scratch. Very short videos have their own rhythm, where every second counts; the framework for writing YouTube Shorts covers that format. And if you're planning several videos at once, word-count estimates help you size your workload realistically, as shown in this 30-day YouTube content calendar.

Let the Generator Do the Arithmetic

Once you know your pace, you shouldn't need to do this calculation by hand every time. The YTScriptPro script generator estimates word counts for a target length based on a speaking rate you can configure in Settings, so you can set it to your measured pace once and plan from there. As always, the estimate is a starting point; your read-through and your edit decide the final runtime.