Text to Speech Time Calculator

What this text to speech calculator does

This calculator estimates how long a block of text will take to read aloud or to play as text to speech. You enter the word count and a speaking rate in words per minute, and it returns the spoken time in minutes and seconds.

It also adds time for punctuation pauses, because real speech slows at periods, commas, and question marks. The method follows how the narration industry times scripts: by words per minute, not by raw character count. The National Center for Voice and Speech notes average English speech runs about 150 words per minute.

The tool runs entirely in your browser, so your text never leaves the page. Type a word count from any editor, set the rate, and read the result in seconds without uploading a file.

You do not need the full manuscript to plan. A chapter count times an average word count per page gives a close enough total to schedule a recording session.

How speaking time is estimated

The core math is simple division. Spoken seconds equal the word count divided by the words per minute, then multiplied by 60. So 100 / 150 * 60 = 40 seconds, and 500 / 150 * 60 = 200 seconds, for a 500-word passage.

The table shows common script sizes at a steady 150 words per minute. Change the rate and the time stretches or shrinks in direct proportion; half the rate doubles the time.

Minutes and seconds are easier to picture than a raw second count, so the result is shown as a clock reading such as 2:05. The underlying seconds are exact; the clock form just reads better on a call sheet.

If you know the target length instead of the words, invert the step: multiply the minutes by the rate to get the word budget. A 3-minute intro at 150 words per minute allows about 450 words.

Why words per minute, not characters

Word count is a better predictor of speaking time than character count, because speech is paced by words and phrases, not by individual letters. A 300-word text is about 300 * 5.1 = 1530 characters, yet the word-based timing is the one voice actors and engines use.

Counting characters can mislead: short words and long words have widely different letter counts, but a narrator still speaks one word in roughly the same beat. That is why this tool asks for words, not characters.

Characters still matter for storage and for some engines that stream by the letter, but they do not set the clock. Two texts with equal characters can differ in spoken time if one uses short words and the other long ones.

When a client asks for a character limit, convert with the 5.1 factor, then check the word time separately. The two numbers describe different things, and mixing them up is the common planning mistake.

Punctuation and pauses add time

Punctuation is where estimates drift. A period, comma, or semicolon makes a speaker pause, and those pauses add up across a long script. This calculator adds 0.4 seconds per punctuation mark you count.

For the 300-word example, 12 pauses add 12 * 0.4 = 4.8 seconds on top of the 120 seconds of speech. On a 1,500-word chapter with 60 pauses, that is 24 extra seconds, small but real for tight timing.

Not every mark deserves a full 0.4 second pause. A comma is shorter than a period, and a paragraph break is longer. The fixed value is a planning average; tighten it for light punctuation, loosen it for dramatic reads.

Listing the pause count separately from the speech time also helps editors. They can see at a glance how much of the clock is structure rather than content, which guides where to cut.

Choosing a speaking rate

The right rate depends on the material. Conversation and most narration sit near 150 words per minute. ACX, Audible's audiobook platform, sets 9,300 words per finished hour, about 155 words per minute; see acx.com for that benchmark.

Slow the rate for dense technical content and speed it up for a short ad. The calculator lets you set any rate from 80 to 220 words per minute, so you can match the voice or the brief.

Rates above 200 words per minute start to sound rushed to most listeners, while rates below 120 can feel slow. The 150 baseline sits in the comfortable middle that audiobook listeners expect.

Children's books and poetry often drop to 120 or less for clarity, and technical manuals may slow further. Pick the rate that fits the listener, then trust the word math to set the length.

Worked example you can check

Work through a 300-word script at 150 words per minute. The base time is 300 / 150 = 2 minutes, or 120 seconds. With 12 punctuation pauses at 0.4 seconds each, 12 * 0.4 = 4.8 seconds, the total is 120 + 4.8 = 124.8 seconds, about 2 minutes 5 seconds.

The same text is about 1,530 characters. At 13 characters per second that is roughly 1 minute 58 seconds, close but a touch shorter, which shows why word-based timing is the steadier rule for planning.

The 2:05 figure already includes the pauses, so do not add them twice. If you want the pure speech time for comparison, the base 2:00 is the number to quote, and 2:05 is what the recorder will spend.

This same walkthrough works for any rate. Swap 150 for 130 and the 300 words stretch to about 2:18 with pauses, a useful check when a slow read is requested.

A longer script example

A longer script scales the same way. A 1,500-word article at 150 words per minute is 1500 / 150 = 10 minutes of speech, or 10 * 60 = 600 seconds. Add 30 pauses of 0.4 seconds, 12 seconds, and the clip lands at about 10 minutes 12 seconds.

Doubling the words to 3,000 would double the speech time to 20 minutes, before pauses. The relationship is linear, so you can scale any estimate by the word count once you fix the rate.

The 10-minute mark is a common podcast segment length, so the 1,500-word estimate is a handy rule of thumb for producers. Two such segments fill a 20-minute show before ads and intro.

Because the relation is linear, a spreadsheet can reproduce this with one formula: words divided by rate times 60. The calculator is just that formula with a pauses field bolted on.

Tips for realistic estimates

For realistic numbers, count every comma, period, and paragraph break as a pause, not just sentence ends. Engines also pause at headings and numbered lists, so add a few extra seconds per section break.

If your text has many short sentences, bump the pause count up; if it is one long paragraph, you can trim it. Treat the result as a planning estimate, then add a 5 percent buffer before you commit to a recording slot.

A 5 percent buffer means a 10-minute estimate becomes 10 minutes 30 seconds of booked time. On a tight broadcast schedule that half minute prevents an overrun and a frantic edit.

Finally, rehearse once with a timer. Real delivery reveals whether your pause count was honest, and the second pass usually trims a few seconds that the plain word math could not see.