Speech time calculator

A worked example with a deliberate pause allowance

A 150-word spoken script at your chosen 150 words per minute gives a one-minute speaking estimate. Add 10 seconds of extra pauses and the total becomes 70 seconds: about 1 minute 10 seconds. That result follows from your assumptions. It does not establish how fast a particular person or voice engine will deliver those words.

Try the original workshop example above, then change the pace or pause allowance. A slower chosen pace increases the estimate. A different pause allowance changes the total independently of the word count. The result is cleared when you edit an input, so a previous estimate is not presented as if it described the newly edited script.

Count the words you intend to say

Written shorthand and spoken wording can differ. “Meet at 3pm” has three written tokens here. If your intended spoken version is “Meet at three in the afternoon,” it has six. Use the spoken version in the calculator when that is what you plan to render, and use Voicetrell’s separate spoken-spelling field when you need to keep the written script intact.

This counter keeps a contraction such as “don’t” together. It separates a hyphenated phrase such as “well-known.” It accepts letters, numeric runs and internally joined apostrophes, with connected decimal/grouped numerals counted as one numeric token. It does not turn a numeral into a phrase, interpret abbreviations, strip HTML or remove stage directions automatically. Scripts without word spacing need a different counting method; this is an English-style estimate.

WPM is different from a voice engine’s rate setting

The words-per-minute field is your planning assumption. An engine’s “normal” setting is relative to that engine and voice. The app’s 1.0× position is therefore not a universal 150 WPM setting, and this calculator does not convert between those controls. Preview the selected installed voice and check the rendered audio when timing matters.

You can choose a useful assumption from a timed read: divide the number of spoken words by the number of minutes taken. Keep the same counting method when comparing versions. Automatic punctuation pauses, pronunciation choices, emphasis and delivery changes can still make the finished audio differ from a simple steady-pace estimate.

Plan segments before rendering

1. Keep an editable original of the written script.
2. Prepare the wording actually intended for speech, including expanded shorthand where needed.
3. Choose a pace assumption and a separate allowance for deliberate pauses.
4. Split the project into supported segment sizes and preview troublesome names or short phrases with the selected voice.
5. Render, listen to the whole result and check the actual WAV duration before sharing.

The website’s pause field is a total allowance in seconds. The app’s pause controls are per-gap values in milliseconds. A planning total does not guarantee that a script fits the app’s segment or output limits, and no browser calculation automatically transfers into the mobile project.

Local voices and output have their own limits

Voicetrell uses compatible offline voices installed on the device. Voice names, languages and availability vary by system speech engine. Personal Voice, cloned voices and network voices are outside its scope. The selected engine and platform terms determine permitted voice use; the app is not a blanket commercial voice licence.

This browser page performs word counting and arithmetic only. It does not request microphone access, contact a speech service or create an audio download. Use the actual voice preview and finished WAV for delivery decisions, while retaining the editable script for later changes.

Method and other planning tools

Speaking estimate in seconds = word-like token count ÷ chosen WPM × 60. Total estimate = speaking estimate + your additional pause seconds. The detailed result retains decimal seconds; the main summary rounds upward for a readable planning duration.

Edge Studio’s speech script timer and FrameCompose’s script length calculator provide other planning workflows. Their counting rules or pace assumptions may differ. Our original workshop example, explicit token rules and pause allowance make this page’s result reproducible.