All field notes

How Long Should a YouTube Script Be? Word Counts by Video Length

How many words is a 10-minute YouTube script? Use this word-count-by-length table (130-150 wpm) to size any video, plus why padding to a runtime backfires.

"How long should my script be?" is one of the first questions every new creator asks, and it usually gets a frustratingly vague answer. The reason is that the honest reply depends on two things: how fast you talk, and how much of your video is you speaking versus footage doing the work. Once you pin those down, sizing a script becomes simple arithmetic.

The quick version: most people speak at around 130 to 150 words per minute on camera, which puts a 10-minute video at roughly 1,300 to 1,500 words. The table below extends that to every common length, and the sections after it explain when to write more, when to write less, and the one mistake that turns a solid script into a boring video.

This is a starting range, not a law. Treat the numbers as a sensible default you calibrate against your own pace - and read the section on padding before you use any of it, because getting the word count right matters far less than not stretching a good idea to fill time it does not need.

Script Word Count by Video Length

Video LengthWords (130-150 wpm)Target (~140 wpm)Fast (150-170 wpm)
3 minutes390 - 450~420450 - 510
5 minutes650 - 750~700750 - 850
8 minutes1,040 - 1,200~1,1201,200 - 1,360
10 minutes1,300 - 1,500~1,4001,500 - 1,700
15 minutes1,950 - 2,250~2,1002,250 - 2,550
20 minutes2,600 - 3,000~2,8003,000 - 3,400

Counts are spoken words in the finished cut. Reduce by roughly 0.85x for videos with heavy B-roll, demos, or screen recordings. Always calibrate against your own timed pace.

01

The Short Answer: Word Count by Video Length

At a natural speaking pace of roughly 130 to 150 words per minute, a 10-minute YouTube video works out to about 1,300 to 1,500 words of script. That single figure is the answer most people are actually searching for, and everything else on this page is just extending it to other lengths and explaining when to bend it.

The important word there is "spoken". Word count for a script means the words that actually come out of your mouth in the finished cut - not everything you type into the document, not your shot notes, not the bracketed directions like [cut to demo]. When you size a script, you are counting narration, because narration is the only thing that consumes runtime at a predictable rate.

The reason it is a range and not one fixed number is simple: nobody talks at exactly the same speed. Some presenters are calm and deliberate at 125 words a minute. Some are caffeinated and clip along at 165. The table below gives you a realistic band for each common length plus a middle-of-the-road target at about 140 words per minute, so you have a starting point before you have ever timed yourself.

02

Where 130 to 150 Words Per Minute Comes From

That band is not arbitrary. 130 to 150 words per minute is the comfortable conversational range for spoken delivery to a camera. It is brisk enough to feel energetic and keep people leaning in, but slow enough that a viewer can follow every point without rewinding. Drop much below it and you start to sound sluggish. Push much above it and a first-time viewer struggles to keep up with new information.

It also lines up with how people are used to being spoken to. Comfortable narration, the kind you listen to without effort, sits in a similar range, which is exactly why a script and a blog post of the same word count feel completely different. A YouTube script is written to be heard, not read silently, so its length is governed by talking speed rather than reading speed. That is the whole reason written word counts and spoken word counts are not the same thing.

For what it is worth, this is the number Scripti uses under the hood. When it sizes a script to a target length, it works at 150 words per minute by default, which lands you at the top of that conversational band and gives you a little room to breathe or cut on the day.

03

Time Your Own Pace (Do Not Skip This)

Here is the honest caveat that most word-count articles quietly leave out: speaking pace is personal, and a table can only ever be a starting range. Two creators can both be right and land 40 words per minute apart. If you script to a generic 140 and you naturally deliver at 120, your "10-minute" video runs closer to 12. If you actually talk at 165, it comes in under 9.

So measure yourself once, and stop guessing. Take a passage of your own writing that is about 200 words long - ideally a chunk of an actual script, not a random paragraph, because your reading voice and your presenting voice are different. Read it out loud the exact way you would record it: same energy, same pauses, no rushing to beat the clock. Time it.

Then do the maths. Words divided by minutes gives you your personal words-per-minute. Read it aloud two or three times and average the results, because your first take is usually slower than your real cadence. Once you have your number, rebuild the table in your head around it. That figure is worth more than any published average because it is yours.

Keep re-checking it too. Your pace drifts as you get more comfortable on camera, and a lot of creators speed up noticeably over their first year of posting. The word count that fit your videos six months ago might be leaving you 90 seconds short today.

04

Fast-Paced Tech and Commentary Run Higher

Not every niche sits in the same band. Fast tech reviews, AI-tool breakdowns, reaction, and commentary tend to skew quicker - roughly 150 to 170 words per minute. The delivery is denser, the edits are tighter, and the audience for that kind of content expects to move at speed. A fast-paced 10-minute video can carry up to around 1,700 words rather than 1,500.

The "fast" column in the table above reflects this. If you make punchy, information-dense videos in a fast-moving niche, size your scripts against that column instead of the standard one, or you will consistently write short and end up padding on the day to hit your target length.

One caution though: faster is not automatically better. Pace should serve the content, not the other way round. If a big slice of your audience is beginners, a slightly slower, clearer delivery usually holds them better than a wall of words fired at 170 a minute. Speed is a stylistic choice tied to your niche and your viewers, not a growth hack. Match it to who is actually watching.

05

B-Roll and Demos Need Fewer Scripted Words

Here is the adjustment that trips people up most. If large chunks of your runtime are screen recordings, live tool demos, or B-roll montages, you need fewer scripted words than the raw table suggests - not more. A useful rule of thumb from the calculators is to apply roughly a 0.85 multiplier for demo-heavy or B-roll-heavy videos.

The logic is straightforward once you see it. Unscripted screen time fills runtime on its own. When you are clicking through an interface, waiting for a render, or letting a montage breathe, minutes are passing but you are barely talking. That footage is doing the work your narration would otherwise do, so if you script the full word count for the total length, you will overrun badly.

Picture a 10-minute walkthrough of an AI tool where three or four of those minutes are you demonstrating the product on screen with only light narration over the top. The full table says 1,300 to 1,500 words. In reality you might only need something closer to 1,100 to 1,300, because the demo carries several minutes almost by itself. Only script the words you are actually going to speak, and let the screen do the rest.

The practical move: when you outline, mark which segments are talking-to-camera and which are demo or B-roll. Budget full words for the talking segments and a fraction of that for the visual-led ones. That is far more accurate than applying one flat number to the whole runtime.

06

The Word Count Is a Container, Not a Quota

This is the part that actually matters for whether your video does well, so read it twice. The single biggest mistake creators make with word counts is treating the number as a target to fill rather than a budget not to exceed. They decide the video "should" be 10 minutes, see that 10 minutes means 1,400 words, and then stretch a 900-word idea across 1,400 words of runtime. That padding is what makes viewers click away.

The reason comes straight from how YouTube actually ranks things. Todd Beaupré, YouTube's Senior Director of Growth and Discovery, explained on Creator Insider in January 2025 that the recommendation system "pulls" a video toward each individual viewer rather than pushing it out to everyone. Aggregate numbers like click-through rate and average view duration are inputs to that per-viewer prediction, not targets you are supposed to chase. There is no single "good" AVD number that unlocks the algorithm.

More to the point, Beaupré was clear that not all watch time is valued equally. YouTube feeds satisfaction signals - things like in-product survey responses and likes - into ranking, and viewers consistently reward videos that get to the point efficiently. Adding those satisfaction signals to the system increased long-run return visits. In plain terms: padding to hit a runtime can actively work against you, because a bored viewer who feels their time was wasted is a negative signal, not a neutral one.

The creator-side version of the same idea is to maximise value-per-minute. If your idea is fully delivered in 900 words, deliver it in 900 words and let the video be six and a half minutes. A tight, efficient video that respects the viewer's time will out-perform a bloated one almost every time - it is the same principle Paddy Galloway points at when he says the idea and its execution, not raw length, are what set a video's ceiling. The word count exists to stop you rambling, not to license it.

07

Turn the Number Into an Outline

A word budget is most useful before you write, as a planning tool, not after, as a scorecard. The trick is to spread the total across the structure of the video so you know where every hundred words is going. That way you catch an overrun on paper instead of discovering it when your edit comes in at 14 minutes.

Start with the hook. A long-form hook is usually about 20 to 30 seconds, which at a normal pace is only around 50 to 75 words. That is a tiny fraction of the total, and it is the highest-impact writing in the whole script, so it should get disproportionate attention relative to its word count. Its job is to confirm the promise in your title and thumbnail, raise the stakes, and open the first question - not to introduce yourself.

Then divide the body. If a 10-minute video gives you roughly 1,300 to 1,500 words and the hook takes 75 of them, you have around 1,250 to 1,400 words for the body and outro. Split that across your main points or story beats and give each one a rough word allowance. As a loose pacing guide, aiming for a fresh turn or payoff roughly every 90 to 120 seconds keeps the middle from sagging.

Now you can see the shape before you record. If your outline demands 1,900 words for a 10-minute slot, something has to be cut or the video has to be longer - and you know that at the outline stage, not in the edit. The number stops being a vague worry and becomes a checklist you can actually plan against.

08

Let the Maths Happen Automatically

Sizing a script by hand is fine, and now you know how to do it: pick your length, apply your personal words-per-minute, adjust down for demo-heavy segments, and budget the total across your outline. But it is also the kind of repetitive arithmetic that is easy to hand off so you can spend your attention on the idea and the hook instead.

This is one of the things Scripti handles for you. You give it a target length, and it generates a full script sized to that runtime at a sensible speaking pace, structured into a hook and body rather than one undifferentiated block of text. Because the length is baked into generation, you are not writing blind and then discovering you are 600 words over.

Whether you use a tool or a stopwatch and a calculator, the principles do not change. Count spoken words, not typed ones. Time your own pace instead of trusting an average. Write fewer words when the screen is doing the talking. And never, ever stretch an idea to fill a runtime - the word count is there to keep you honest, not to give you a quota to pad out.

The Word Count Checklist

1.Start from the table: about 130-150 words per spoken minute, so ~1,300-1,500 words for a 10-minute video
2.Count spoken narration only - not shot notes, directions, or anything you will not say out loud
3.Time your own pace with a 200-word passage read the way you record, then rebuild the numbers around your result
4.For fast tech or commentary, size against 150-170 words per minute instead of the standard band
5.Cut roughly 15% (a ~0.85x multiplier) for videos where demos, screen recordings, or B-roll fill the runtime
6.Budget the total across your outline: ~50-75 words for the hook, the rest split across body beats
7.Never pad an idea to hit a runtime - deliver the value and let the video be as long as it needs to be
8.Re-check your pace every few months, because most creators speed up as they get comfortable on camera

From idea to record-ready

Get a script sized to your runtime

Scripti builds to your target length and structures the hook and body, so you can spot an overrun before the edit.

Analyze a script free

No account or card required.

Scripti uses optional analytics and session replays to improve the product. Privacy and cookies