How long should a short-form video script be?

Why does words-per-second advice miss the point?

Because everyone reads a line at a different pace, so a fixed words-per-second number describes nobody's delivery in particular. A fast talker and a slow one can read the exact same page of a script in visibly different times, and only one of those times is the one that actually fits your length.

The fix is to time your own reading instead of borrowing someone else's number. Read the script aloud, at the pace you would actually deliver it on camera, with a stopwatch running, and trim or add until the read lands inside the length you're aiming for. That number only describes the script you just timed — write the next one and read it again.

What fits in a short script?

A short script has room for three parts: a hook, one beat, and a close. There's no setup, because a short video doesn't have time to spend on context before the hook has to prove itself, and there's no separate turn beat — the single beat and the turn happen together.

That's a compressed version of the five parts covered in the parts of a short-form video script: the hook and the close stay exactly where they are, and everything in the middle collapses into whichever beat is carrying the reveal.

What fits in a medium script?

A medium script has room for a hook, a one-line setup if the premise genuinely needs it, two or three beats, a turn, and a close. This is the shape most brand scripts land in: enough beats to build a real demonstration, without so many that the turn arrives after a viewer has already decided nothing is going to change.

If you're writing in a two-column script, a medium length is usually three to five rows once the hook and close are counted, with the SAY column doing most of the work of carrying the video from one beat into the next.

What fits in a longer script?

A longer script adds beats, not longer beats. The hook, the setup and the close stay roughly the size they would be in a medium script; what grows is the number of steps between the setup and the turn — a second attempt that fails, a wider comparison, an extra angle on the same demonstration.

Stretching a single beat to fill the extra time is the more common mistake. A beat that already made its point and keeps talking isn't using the length, it's stalling inside it, and a stalled beat is exactly where a viewer who was still watching decides to stop.

What should you cut first if a script runs long?

Cut the setup first. It's the part most scripts can lose without losing meaning, because the hook and the first beat can usually carry the context between them on their own. If the setup is already gone, cut the least load-bearing beat next — the one that repeats a point another beat already made, not the one that introduces something new.

Never cut the turn to save time. The turn is where the hook's promise gets paid off, and a script that keeps every beat but rushes or drops the turn has spent its whole length on a promise it never actually keeps. The close can shrink to one line before the turn should lose a single second.

What does cutting a script down actually look like?

Here's the same idea written long, then cut down to the parts it actually needs. This is an illustration written for this guide, for a pair of wireless earbuds, not a real result.

1. hooksay: “Why do my earbuds die by lunch, every single day?”do: Close on the charging case, battery icon at 12%.
2. setupsay: “I charge them every night. I never leave the house without the case.”do: Drop the case into a bag next to a phone.
3. beat 1say: “I tried a bigger case. Same result by 1pm.”do: Hold up a bulkier case, a phone clock visible behind it.
4. beat 2say: “I turned off noise cancellation. Bought me maybe an hour.”do: Tap into the earbud settings, toggle noise cancellation off.
5. turnsay: “Then I checked how old the buds actually were. Eighteen months — that's the battery, not the case.”do: Hold the earbuds next to a phone screen showing the purchase date.
6. closesay: “Since I swapped them, they've made it to 6pm with no case in sight. Linked below.”do: Earbuds back in, phone screen shows late afternoon.

Cutting it down removes the setup and merges the two failed attempts into a single beat, while the turn and the close stay untouched.

1. hooksay: “Why do my earbuds die by lunch, every single day?”do: Close on the charging case, battery icon at 12%.
2. beat 1say: “I tried a bigger case, then turning off noise cancellation. Neither one made it past lunch.”do: Quick split of both attempts, a phone clock visible in each.
3. turnsay: “Then I checked how old the buds actually were. Eighteen months — that's the battery, not the case.”do: Hold the earbuds next to a phone screen showing the purchase date.
4. closesay: “Since I swapped them, they've made it to 6pm with no case in sight. Linked below.”do: Earbuds back in, phone screen shows late afternoon.

Questions

Should a script be written to a fixed time limit?

No. Pick the length range a platform or brief allows, then let the beat count decide how much of it you use — a script forced to hit an exact second count usually loses its turn or its close to make the number work.

What if the same script needs to work at two lengths?

Write the longer version first with its full beat map, then find the single beat that adds the least and cut only that one for the shorter version, so both versions still keep their hook, their turn and their close.