GoScript
Back to Blog
GoScript Journal

Matching Word Count to Shorts Pacing

·5 min read·GoScript Team /Editorial

Word count is the most honest pacing tool you have. A comfortable speaking rate runs about two and a half words per second, so the script length quietly caps how much you can say before the runtime is full.

Most bloated Shorts are not badly edited. They were written longer than the clock allows and then squeezed. Counting words before you record saves the squeezing.

Budget the runtime before the words

A thirty second Short leaves you around seventy five spoken words once you account for pauses and cuts. A sixty second one gives you roughly a hundred and fifty. Write to the number instead of discovering it in the edit.

This budget forces hard choices early. If the script is twenty words over, one idea has to go, and choosing it before recording is easier than choosing it on a timeline at midnight.

Leave room for the cut

Spoken scripts almost always shrink in the edit, never grow. Filler removal and dead air trimming take out ten to fifteen percent on average. If you write to the exact limit, you finish with a little space to breathe.

That leftover space is useful. It becomes the pause before the payoff or the extra half second the loop needs. Writing slightly under the budget gives the edit somewhere to work.

The runtime you see is the edit. The runtime you can fill is the script. Know the number before you sit in front of the mic.

Count in beats, not just words

Words per second is a rough gauge, but beats are the real currency. A three word beat and a fifteen word beat can take the same time if the short one gets a pause. Budget ideas, then check the word count against them.

I sketch the beats first and assign a rough second count to each. Adding the seconds tells me whether the clip fits before a single line is polished. The plan is faster to fix than the recording.

Key takeaways

  • Assume roughly two and a half spoken words per second.
  • Budget ninety words for thirty seconds, about one fifty for sixty.
  • Write slightly under the limit to leave space for cuts.
  • Assign a time estimate to each beat before writing the lines.

Turn this into your next script.

Analyze a channel, extract its structural DNA, and generate scripts engineered from patterns that actually work.

Analyze a Channel