Script reading time by WPM

This calculator estimates how long a script takes to read silently or deliver aloud, using either your own words-per-minute rate or a practical default for the selected mode. It also shows both silent and spoken benchmarks, making the difference visible at a glance. Use it for lessons, presentations, videos, podcasts, speeches, voice-over work, rehearsals, or any workflow where timing matters before recording or presenting begins.

Choose the timing mode that matches the real task

Silent reading and spoken delivery are different activities, so one universal words-per-minute figure can produce a misleading schedule. Silent readers can move quickly, skip familiar transitions, and recognize groups of words without articulating every sound. A presenter or narrator must pronounce the text, breathe, emphasize key points, and leave enough space for the audience to follow. Select silent mode when estimating review, proofreading, study, or private rehearsal. Select spoken mode for speeches, classroom delivery, narration, voice-over, podcasts, video scripts, and presentations. When you do not provide a custom rate, the calculator uses 238 WPM for silent reading and 150 WPM for spoken delivery. Those defaults are planning benchmarks, not claims about every reader. The response always includes both benchmark durations, even when you choose a custom speed, so you can see how the same word count behaves in each context. This comparison is especially useful when a script must first be reviewed privately and then performed aloud. It prevents a fast silent read from being mistaken for the final running time.

Use word count and WPM to produce a dependable estimate

Enter the script's word count, select silent or spoken mode, and optionally supply a positive WPM value measured from the intended reader. The core calculation is deliberately transparent: words divided by words per minute gives minutes. The result includes decimal minutes, rounded total seconds, and a clock-style duration that is convenient for production notes. For the most useful custom rate, time a representative sample rather than a single unusually easy paragraph. Read in the same style the final script requires, including ordinary pauses and natural emphasis, then divide the sample's word count by elapsed minutes. A speaker who delivers 300 words in two minutes has a measured rate of 150 WPM. Reusing that rate for later drafts gives a more personal forecast than a general benchmark. The calculator remains deterministic: identical inputs always return identical outputs, with no network request, randomness, or hidden language model judgment. It estimates continuous reading time only. Planned demonstrations, audience questions, slide changes, music, dramatic silence, applause, or editing transitions should be budgeted separately after the reading estimate is known.

Turn the estimate into a practical script revision

Treat the calculated duration as a baseline for editing and rehearsal. If a spoken script exceeds its slot, compare the allowed time with the current estimate before cutting material. At 150 WPM, removing 150 words reduces continuous delivery by about one minute; at another custom speed, use that speed as the corresponding words-per-minute target. Do not solve every overrun by telling the speaker to rush. Faster delivery can reduce clarity, weaken emphasis, and make technical or unfamiliar material harder to absorb. Instead, remove repetition, shorten transitions, simplify dense sentences, or move secondary detail into supporting material. If the script fits too comfortably, the spare time can support purposeful pauses, examples, interaction, or a calmer pace. For recordings, compare the estimate with the desired finished duration and then add known non-speech segments. For live events, include a buffer because room response and speaker variation rarely match a clean rehearsal exactly. Save the word count, chosen mode, WPM, and returned clock time with the draft so collaborators understand the assumption behind the schedule. Recalculate after meaningful edits; even a polished estimate becomes stale when the script changes.