Script Timer: Calculate Script Length in Minutes (Formula + WPM Table)

If you have a hard runtime (a 60-second ad, a 5-minute presentation, a 2-minute explainer), guessing your script length is how you end up rushing, cutting lines last-minute, or re-recording.

Disclosure: This page contains affiliate links. If you buy through them, we may earn a commission at no extra cost to you.

Quick answer: how a script timer works

A script timer estimates spoken duration from word count and a speaking pace (words per minute, or WPM). The basic math is simple:

Minutes = words / WPM
Seconds = (words / WPM) * 60

Most script timer tools let you paste your script, choose a pace (for example 120 WPM for slow, 150 WPM for normal, 180 WPM for fast, 200 WPM for very fast), and they output an estimated runtime.

Limits can change-check the platform help center for the latest. (Especially if you are writing for a specific ad unit, short-form format, or presentation slot with a strict time spec.)

What to do before you calculate

Count words first. If you have the full script text, paste it into your word counter. If you only have an outline, estimate rough words per section and sum them. (If you are new to counting fields, see Character count basics.)
Pick a realistic pace. A single number is fine for planning, but your actual delivery depends on genre, pauses, and how technical the content is.
Add a pause buffer. Even strong readers pause for emphasis, breathe, and let visuals land.

Pick a speaking pace (WPM) that matches your format

There is no perfect WPM for everyone. The goal is to choose a starting pace that matches your audience and format, then adjust after a read-through. Many professional tools and voiceover resources use ranges like:

120-140 WPM: educational or technical content (more time to process)
130-150 WPM: business presentations (clear, confident, not rushed)
140-160 WPM: general online video (engaging but understandable)
170-200 WPM: short-form or high-energy delivery (use carefully)

Use the table below as a practical starting point, then validate with a quick rehearsal.

Script Timing Table

Use case	Good starting pace	Why it works	Quick note
Educational / tutorial	120-140 WPM	Gives listeners time to follow steps and absorb new terms	Add 10-15% for pauses and on-screen demos
Business presentation	130-150 WPM	Clear, confident pacing without sounding rushed	Leave time for slide transitions and emphasis
General YouTube video	140-160 WPM	Engaging pace that stays understandable	Cut filler words before increasing speed
Casual vlog	150-180 WPM	Closer to conversational energy	Watch for breath and clarity on longer takes
News / formal delivery	160-180 WPM	Efficient broadcast-style cadence	Use shorter sentences for clean articulation
Shorts / high-energy promos	170-200 WPM	Matches quick consumption and tight runtimes	Use sparingly; comprehension drops if you cram

Next, follow the workflow below to calculate a realistic runtime (not just a best-case math result).

Trim your script to match your target time

Generate shorter alternatives, then choose the cleanest line for a natural read.

Try QuillBot

Step-by-step: time any script without a tool

This method works for video voiceovers, podcast segments, speeches, and presentations. All you need is a word count and a stopwatch.

Get the word count. Paste your script into your word counter (or count per section and add up). If your script includes stage directions, decide whether they will be spoken. Spoken directions count; visual-only notes do not.
Choose a baseline WPM. If you do not know your pace, start with 150 WPM for conversational English, then adjust by format (use the table above as a starting point).
Compute the raw time. Example: 450 words at 150 WPM = 450 / 150 = 3.0 minutes (180 seconds).
Add a pause buffer. Add 10-15% if you expect emphasis, breathing, or visuals that need time to land. For the example above, 3:00 becomes about 3:18 to 3:27.
Add fixed extras. Add intro/outro lines, calls to action, music beds, or audience reactions that are not in the word count.
Do a real read-through. Read it out loud once at a natural pace. Time the read. Then compute your true pace: WPM = words / minutes. Use that WPM for your final estimate.

Make your estimate more accurate in real life

Punctuation matters. Commas, dashes, and parentheses slow delivery. So do numbers you need to say carefully (dates, prices, statistics).
Complex ideas slow delivery. Technical explanations, unfamiliar terms, and long sentences often require a slower pace to stay clear.
On-screen actions take time. If you are demoing software, showing B-roll, or waiting for a visual punchline, your runtime will be longer than the pure spoken math.

How to hit a target duration (without sounding rushed)

Once you have an estimate, your real job is editing: cutting or expanding while keeping the message intact. Use this quick process:

Decide what is non-negotiable. Write 1 sentence for the main promise, 3 bullet points for the key proof, and 1 clear next step.
Cut first, then speed up. If you need to save time, remove redundancy and filler before you increase WPM. Faster delivery is the last lever, not the first.
Swap long phrases for short ones. Replace multi-word hedges with a single clear verb (for example, change 'in order to' to 'to').
Front-load value. Put the payoff early and move nice-to-have context later. This makes it easier to trim from the bottom if you run long.
Rewrite rough lines until they read smoothly. Tongue-twisters and awkward phrasing cause stumbles that add time.

If you want a fast way to tighten wording without changing meaning, a paraphraser can help you generate shorter alternatives to the same idea, then you pick the cleanest option. One option is shorten your script without losing meaning by rewriting sentences more concisely and smoothing grammar so the final read feels natural.

Tip: after you revise, re-count words and re-run the same timing math. Small cuts compound quickly: shaving 30 words at 150 WPM saves about 12 seconds, before pause buffers.

Mistakes to avoid

Using a random WPM and treating it as fact. Use a starting pace, then validate with a real read-through.
Forgetting the buffer. Even a clean voiceover usually needs extra time for breaths, emphasis, and transitions.
Editing by speed instead of clarity. If you cram words into a short runtime, comprehension drops and the script feels stressful.
Counting words but ignoring structure. A script with short sentences often reads faster and cleaner than one with long, nested sentences, even at the same word count.
Not timing the final version. Always do one last read at delivery pace (and in the room, if it is a live talk).

Quick mini-checklist before you record or present

Word count confirmed (spoken text only)
Baseline WPM chosen for the format
Pause buffer added (10-15% is a common starting range)
One full read-through timed and your personal WPM calculated
Final script edited for clarity (not just speed)

Rewrite awkward lines so delivery feels smoother

Rewrite with QuillBot

FAQ

How many words is a 1-minute script?

It depends on pace, but a common planning range is about 120-180 words per minute. Many creators start around 140-160 WPM for general video and adjust after a rehearsal.

What is a good WPM for an explainer or tutorial?

Start slower than casual conversation: roughly 120-140 WPM is a practical range for educational content, especially when viewers need time to follow steps.

How do I calculate script time from word count?

Use minutes = words / WPM. Then add a pause buffer (often 10-15%) and any fixed extras like an intro, outro, or audience reaction time.

Are script timer estimates accurate?

They are useful for planning, but they are still estimates. Accuracy improves when you (1) choose a pace that matches the format, and (2) time one real read-through and use your personal WPM.

Should I time by words or characters?

For spoken runtime, words are the most practical unit. Characters are still useful for tight fields (titles, captions, on-screen text), but they do not predict speaking time as reliably as word count.

Why does my final recording run longer than the estimate?

Common causes are pauses, emphasis, complex sentences, and on-screen actions that were not accounted for. Add a buffer and do a timed rehearsal before you lock the final script.

Conclusion: the simplest way to use a script timer

Count your words, pick a realistic WPM for the format, do the math, and then validate with one timed read-through. If you need to hit a strict runtime, edit for clarity first (cut redundancy and simplify phrasing), then re-time the final version.

As you iterate, keep your drafting workflow tight: measure word count, time it, revise, and repeat. You will feel the difference immediately in smoother delivery and fewer last-minute cuts.