What's a typical speaking pace?

150 words per minute for typical podcast/voiceover delivery. Slower for authoritative or measured tones (130 wpm); faster for energetic or conversational (170+ wpm). Auctioneers and news readers can hit 200+.

How accurate is the estimate?

Within 10-15% for typical scripts. Accuracy depends on whether your delivery pace matches the configured wpm. Calibrate by reading and timing a known script.

Should I include stage directions?

No. Only spoken words contribute to spoken duration. Strip stage directions, parentheticals, and other non-spoken text before estimating.

What if I read at a different pace?

Adjust the wpm setting to match your actual pace. Read a script aloud and time yourself; word_count / minutes = your personal wpm.

Does it account for pauses and music?

No. The estimate is for continuous reading. Add 10-20% buffer for natural pauses, breaths, and any sound design elements.

Is my script uploaded?

No. Estimation happens in your browser.

What about read-along videos?

Read-along pacing matches narration, which is typically slower than typical speech (around 130 wpm) to allow audience comprehension.

Can I get per-section estimates?

Some tools split by paragraph or scene. The total is sum of parts; per-section estimates surface pacing variation.

Free Converter

Script Timer

Calculate how long it takes to read your script aloud. Perfect for YouTube Shorts, TikToks, and video content creators.

Speaking Speed

Platform

Target: 60 seconds

Results

Word Count

words

Estimated Time

150 wpm

Paste your script here...

Unlock Advanced Script Tools

Get pause markers, emotion cues, and export to teleprompter format with Any-Tools Pro.

About Script Reading Time

Script timers estimate how long it will take to read a script aloud at a typical speaking pace. Voiceover artists, podcasters, presenters, and YouTube creators all need to match scripts to target durations — too long and audio runs over, too short and the segment ends abruptly. The estimate lets writers adjust before recording rather than discovering the timing issue mid-session.

Standard adult reading aloud paces fall around 130-160 words per minute (wpm). Slower for measured authoritative tones (newscasters at 130 wpm); faster for casual conversation (170+ wpm). The default of 150 wpm is a reasonable middle. The timer accepts custom paces for specific applications — audiobook narrators, voiceover specialists, fast podcasters.

This tool counts words in the input and divides by the chosen pace to produce a duration estimate. For more accurate prediction, paste the actual script (not summary or notes) so the count matches what will be spoken.

Why Estimate Speaking Time

Producing audio content with target durations — 60-second ads, 5-minute podcast segments, 15-minute presentations — requires writing scripts that fit. Estimating before recording prevents wasted studio time.

Live presentations also benefit from timed scripts. Knowing that a prepared speech will take 18 minutes lets you plan for an 18-minute slot, with a few minutes of buffer for Q&A or unscripted content.

How to Time a Script

Paste the script, set speaking pace, get the time.

Paste your script: Drop the actual script text into the input area. Stage directions and non-spoken parenthetical notes can be excluded by removing them from the input before pasting.
Set speaking pace: Default is 150 wpm. Adjust for your delivery style: 130 for slow authoritative, 150 for typical, 170+ for energetic.
View the estimated time: Output is the estimated speaking duration in minutes and seconds. Some tools also show the breakdown by paragraph for pacing analysis.
Adjust the script if needed: If the estimate exceeds your target, trim. If it falls short, expand. Re-estimate after edits to confirm.

Common Use Cases

Writing podcast scripts to specific lengths — Podcast segments often have target durations. Estimating before recording avoids running long or short.
Producing voiceover scripts for video — YouTube videos, ads, and explainers need narration that matches video length. Script timing prevents misalignment.
Preparing for conference talks — Talk slots are typically 15, 25, or 45 minutes. Knowing your script's runtime confirms you can deliver on time.
Recording audiobooks — Audiobook narrators and producers estimate book runtime from word count to plan recording schedules.
Writing radio or TV ad copy — 30-second and 60-second ad slots have hard caps. Word counts matched to pace ensure the ad fits.

Technical Details

Estimate = word_count / pace_wpm. Output in minutes (with decimal) or minutes and seconds. The accuracy depends on whether the speaker matches the configured pace.

Standard paces: 130 wpm for slow authoritative narration, 150 wpm for typical podcast/voiceover, 170 wpm for energetic conversation, 200+ wpm for quick reads or auctioneers. Recording professionals know their personal pace; for general use, 150 is a safe default.

Edge cases: lots of pauses, complex pronunciation, technical jargon, or laughter all slow effective pace below the configured number. Add 10-20% buffer if your delivery style includes these elements.

Best Practices

Calibrate to your own pace — Read a known-length script aloud and time yourself. The result is your personal wpm; use it for future estimates.
Add buffer for non-spoken time — Pauses, breaths, sound effects, and music beds extend total runtime beyond words-per-minute calculations. Buffer 10-20%.
Time per section — For longer scripts, time each section separately. This shows pacing variation and helps spot sections that run too long.
Practice the actual delivery — Estimates assume continuous reading. Real delivery has pauses for emphasis, listener attention, or unscripted asides. Practice the actual delivery to refine the estimate.

Frequently Asked Questions

What's a typical speaking pace?: 150 words per minute for typical podcast/voiceover delivery. Slower for authoritative or measured tones (130 wpm); faster for energetic or conversational (170+ wpm). Auctioneers and news readers can hit 200+.
How accurate is the estimate?: Within 10-15% for typical scripts. Accuracy depends on whether your delivery pace matches the configured wpm. Calibrate by reading and timing a known script.
Should I include stage directions?: No. Only spoken words contribute to spoken duration. Strip stage directions, parentheticals, and other non-spoken text before estimating.
What if I read at a different pace?: Adjust the wpm setting to match your actual pace. Read a script aloud and time yourself; word_count / minutes = your personal wpm.
Does it account for pauses and music?: No. The estimate is for continuous reading. Add 10-20% buffer for natural pauses, breaths, and any sound design elements.
Is my script uploaded?: No. Estimation happens in your browser.
What about read-along videos?: Read-along pacing matches narration, which is typically slower than typical speech (around 130 wpm) to allow audience comprehension.
Can I get per-section estimates?: Some tools split by paragraph or scene. The total is sum of parts; per-section estimates surface pacing variation.

Script Timer

Results

Unlock Advanced Script Tools

Related Tools

Character & Word Counter

Twitter/X Thread Splitter

Meta Tag Length Checker

SEO Keyword Density Analyzer