Explainer Video Script Length: Word Count by Runtime

Plan an explainer video script at roughly 130 to 150 spoken words per minute, then reduce the count for technical language, product interactions, deliberate pauses, or character performance. For a 60-second explainer, that usually means 130 to 150 words. Treat that range as a ceiling, not a container you have to fill.

A quick note from Trey

I think the word-count question gets asked a little backward. Teams will ask how much they can fit into 90 seconds, then spend the next few weeks trying to squeeze in one more feature, one more qualifier, and one more audience. I usually start with a simpler question: what needs to land for the viewer? Once that is clear, cutting the extra stuff gets much easier.

In this guide: Word-count ranges · Time the read · Write for the ear · Review checkpoints · FAQs

Word-count ranges by runtime

The table below is DemoFlick planning guidance. It gives you a sensible place to start, not a universal rule for every narrator or subject.

Target runtime	Planning range	Typical job
30 seconds	65 to 75 words	A focused campaign cutdown or one clear idea
60 seconds	130 to 150 words	A concise product or category overview
90 seconds	195 to 225 words	A B2B explainer with room for context and proof
120 seconds	260 to 300 words	A more involved product story or technical concept
3 minutes	390 to 450 words	Detailed education or a guided workflow

Start with the lower end whenever the viewer needs to read a screen, follow a cursor, compare states, or absorb a new term. A useful companion is our SaaS demo runtime guide, which helps decide whether the video itself needs to be short, mid-length, or a deeper workflow demo.

Why filling the time weakens a script

An explainer has more than one communication channel. There is narration, motion, on-screen text, interface activity, music, and sometimes character performance. If the narration describes every detail the viewer can already see, it competes with the visual instead of helping it.

Imagine a dashboard changing from scattered warnings to a prioritized queue. The visual can show the transition. The narration should explain why the transition matters: the team can see what needs attention without hunting through five systems. That division of labor makes the video feel smarter and easier to follow.

More words also create a revision problem. Once a script is packed to the limit, every new stakeholder comment either makes the read rushed or pushes the video longer. A stronger move is to decide what the new point replaces.

Start with one sentence

Before anyone writes an opening, finish this sentence: After watching, the buyer should understand that…

If the answer contains several unrelated promises, the script probably needs a priority before it needs another paragraph. A focused B2B explainer often has five jobs:

1. Name a problem the audience recognizes.
2. Show why the current approach gets in the way.
3. Introduce a clearer approach.
4. Use selected proof to make that approach believable.
5. Give the viewer one useful next step.

That structure does not mean every video has to sound the same. It simply protects the message from becoming a feature inventory.

Estimate the read before polishing

Use this basic formula before treating the script as finished:

estimated narration seconds = word count ÷ words per minute × 60

A 210-word script read at 140 words per minute takes about 90 seconds of continuous narration. Then add visual holds. A product interaction, comparison, customer quote, logo reveal, or final call to action may need time when nobody is talking.

Enter a target runtime and narration pace in the script word-count calculator, then reserve time for visuals and pauses.

Use the calculator

Script word-count calculator

Use this as a planning check. The result is a ceiling, not a quota.

Target runtime in seconds
Narration pace in words per minute
Visual holds in seconds

Plan about 187 spoken words after 10 seconds for visual holds.

Formula: (runtime seconds minus visual holds) divided by 60, multiplied by words per minute. Reduce further for technical language or dense interface activity.

Runtime	130 WPM	150 WPM
30 seconds	65 words	75 words
60 seconds	130 words	150 words
90 seconds	195 words	225 words
120 seconds	260 words	300 words

The embedded calculator lets you subtract visual holds before turning a target runtime into a word ceiling. It includes the same 30-, 60-, 90-, and 120-second table shown above for readers who prefer a quick reference.

Take the scene timer with you

Use the editable DemoFlick Explainer Script Timer to plan scene narration, on-screen text, visual holds, owners, and approvals. It is free to download and does not require an email address.

Read the full draft out loud at a conversational pace. Better yet, record a temporary version and time it. Silent reading hides long sentences, awkward turns of phrase, and lines that ask the viewer to remember too much at once.

Write for the ear

People do not get to scan backward through a voiceover the way they scan a page. Use familiar words, short sentences, contractions, and concrete outcomes.

Watch for phrases like robust platform, seamless ecosystem, and end-to-end transformation. They take up time without giving the visual team much to show. Replace them with a change the viewer can picture:

• Find the answer without switching between five systems.
• Give every location the current process.
• Show sales which accounts need attention.
• Help new users reach their first successful outcome.

The goal is not to make everything casual. It is to make each line understandable the first time someone hears it.

Slow down for complexity

Slow down when the viewer is learning a new category, hearing technical terminology, following an interface action, or considering a regulated subject. That does not require a dramatic delivery. It means leaving room for the information to register.

The same goes for important visuals. If the viewer needs to notice a data change or understand a workflow handoff, the script should not race past it. If the animation only works after muting the voiceover, the two were not planned together.

Separate narration from on-screen text

On-screen text is useful for structure, terminology, proof points, and silent viewing. It should not become a second script competing with the narrator. In a product demo, the interface already contains labels, so overlays should direct attention instead of repeating every spoken sentence.

Plan captions early, especially for versions likely to be watched without sound. The W3C explains that captions for prerecorded media are intended to make audio information available to people who cannot hear it. Section 508 guidance on captions and transcripts also helps teams distinguish captions from a separate transcript or media alternative. This is practical accessibility guidance, not legal advice for a particular situation.

Dense narration creates dense captions. Simpler spoken sentences make both experiences easier.

Protect the target during review

Feedback has a way of adding words. Someone remembers a feature. Someone wants a qualifier. Someone wants the opening to address a second audience. Without a message hierarchy, a 90-second script quietly turns into a much longer piece.

Put the target runtime and planning range in the creative brief. When a point is added, ask what it replaces, what visual proof it needs, and whether it belongs in a supporting asset instead.

For a fuller production view, see the DemoFlick production process. DemoFlick reviews the script and visual concept before design, voice, animation, sound, and delivery. Those early checkpoints help the team solve the right problem while changes are still straightforward.

DemoFlick review checkpoints

The most useful review is not a pile of line edits at the end. It is a series of small decisions made in order:

Checkpoint	What to decide	Keep an eye on
Script	Message, audience, and target length	One clear promise
Visual concept	What the viewer needs to see	Holds for interface actions and comparisons
Storyboard	Scene order and information density	Narration versus on-screen text
Final production	Read, pacing, captions, and call to action	Whether the video still does one job well

If your team needs help getting the message and visual plan into the same shape, DemoFlick explainer video production starts with that communication job before the final treatment is chosen.

Frequently asked questions

How many words fit in a 60-second video?

Plan around 130 to 150 words, then reduce the count when visuals, product actions, or deliberate pauses need room.

Why does a recorded read run longer than the draft suggests?

Writers read silently faster than people speak. Natural pauses, unfamiliar language, emphasis, and visual holds add time. Time a spoken read before finalizing the script.

Should on-screen text repeat the voiceover?

Only selectively. Use it for structure, terminology, and key proof. Repeating every spoken sentence makes the viewer choose between two scripts.

When should we choose a slower narration pace?

Use a slower pace when the audience needs to learn a new concept, follow an interface, read meaningful text, or understand a complex comparison. The video should feel clear before it feels efficient.

Ask DemoFlick a script or project question