Speaking time calculator
Words to minutes, minutes to words — with pace presets for preaching rather than podcasting.
Runs in your browser — free, no signup, nothing uploaded
Speaking time
24 min 00 sec
3,000 words at 125 words per minute.
A sermon that length usually yields up to 5 short clips worth posting — the moments that stand on their own without the surrounding context.
How long a sermon actually takes to preach
The arithmetic is trivial — words divided by words per minute — and it is the second number that everyone gets wrong. Generic speaking-time calculators assume something near 130 words per minute, which is a fair average for a conference talk and a poor one for a sermon. Preaching carries pauses that conversation does not: a passage read from the text, a beat held after a hard sentence, a congregation answering back. Those pauses are real time, and they are the reason a manuscript that timed at 22 minutes in the study runs 28 in the room.
The presets above are delivery rates, not reading rates. Set the pace to how you actually preach and the estimate stops being a rough guide and starts being usable.
Words per minute by delivery style
- 105 wpm — slow and deliberate. Teaching through a difficult text, a large room with a long reverberation time, or a service with consecutive interpretation. Anything that forces you to leave gaps.
- 125 wpm — preaching. The working default for most pulpits. Faster than deliberate teaching, slower than ordinary conversation, because the pauses are doing work.
- 130 wpm — conversational. Unscripted delivery to a room, the pace of a good podcast episode or a talk given from notes rather than a manuscript.
- 155 wpm — reading aloud. Delivering written text more or less as written. This is the pace people default to when they rehearse silently, which is exactly why silent rehearsal underestimates the clock.
Common conversions
At a preaching pace of 125 words per minute, a 20-minute sermon is about 2,500 words, 30 minutes is about 3,750, and 45 minutes is about 5,600. Run the same manuscripts at a read-aloud 155 and each one comes in roughly a fifth shorter. If you write to a word count, pick your pace first — the difference between the two ends of that range is about six minutes on a half-hour sermon, which is the difference between finishing on time and running over.
What the calculator can’t see
Only the speech. A service has other minutes in it — the scripture reading before the sermon, a video that rolls in the middle, the response at the end, the announcement someone always adds. Add those separately. And read the thing aloud with a timer before a service you cannot afford to run long: no calculator knows what you will do with a paragraph until you do it.
Questions people ask
- How many words per minute is a normal speaking pace?
- Most people land between 110 and 150 words per minute when speaking to a room. Conversational delivery sits near 130. Reading prepared text aloud runs faster, around 150 to 160, because you are not pausing to think. Preaching is usually slower than both — roughly 110 to 140 — because it carries pauses for emphasis, scripture reading and congregational response.
- How long is a 3,000 word speech?
- At a conversational 130 words per minute, 3,000 words takes about 23 minutes. At a slower preaching pace of 115 it runs closer to 26 minutes, and read aloud at 155 it drops to about 19. That spread of seven minutes on the same manuscript is why a single average is not much use — set the pace to how you actually deliver.
- How many words should a 30 minute sermon be?
- Between 3,300 and 4,200 words for most preachers, taking 110 to 140 words per minute as the working range. Write toward the lower end if you read from a full manuscript, because a manuscript delivered live almost always runs longer than it does at your desk.
- Does this count the pauses?
- Only the ones already built into the pace you choose. The presets are measured delivery rates, so ordinary rhythm is included, but a long silence, a worship response, a video roll-in or an altar call is not. Add those minutes separately — for many services they are the difference between the estimate and the clock.
- Is the estimate accurate enough to plan a service around?
- It is accurate enough to catch a manuscript that is obviously too long, which is the usual reason to check. It is not a substitute for reading the thing aloud with a timer, and no calculator can be — your own pace varies with the room, the passage and the week.