Three rates, and why these three
Any words to minutes calculator is only as good as the rate it assumes, and most of them hide a single number behind a confident answer. This one shows its work by reporting three rates side by side on every run.
The three are 110, 130 and 160 words per minute. They are not arbitrary. 130 is the number that recurs across public speaking references as a typical clear presentation pace. 110 sits where a measured, pause friendly delivery lands, the pace of an audiobook narrator or a speaker who wants the room to keep up. 160 is a genuinely fast delivery, sustainable for a podcast or a piece to camera but hard to hold for an hour.
Seeing all three at once turns a false precision into a range, which is the shape the answer actually has.
Producing an estimate
- Paste your script into the input box.
- Pick a Highlighted speaking rate if you want one of the three called out separately. Average is the default.
- Set a target duration in minutes if you also want the reverse calculation. Leave it at zero to skip that section.
- Run the tool and read the report.
- Copy or download the report if you want to keep it alongside the draft.
What the report actually contains
The output is a plain text report in two labelled blocks. The first block gives the word count, then the estimated speaking time at each of the three rates in a lined up column, then a single highlighted line repeating whichever rate you selected.
The second block answers the reverse question for the target duration you set, listing the words needed at each rate. If no valid target is set, that block says so instead of printing a meaningless row of zeroes. A closing note repeats that these are estimates from general English rates and that real delivery varies.
Because the whole thing is text, it drops straight into a script document as a header, which is how I actually use it when a talk has a hard time limit.
Writing to a slot instead of timing a draft
The reverse calculation is the half that gets overlooked, and for anyone writing to a fixed length it is the more useful of the two. You rarely start with a finished script and wonder how long it runs. You start with a five minute slot and need to know how much to write.
The answer is a range there too. Five minutes is 550 words if you plan to speak deliberately and 800 if you plan to move. Writing to the top of that range and then cutting is usually a worse plan than writing to the middle, because the material you cut under time pressure is rarely the material you should have cut.
Where the estimate breaks down
The model is a constant rate with no silence in it, so every source of error points the same way: real delivery takes longer than the estimate, not shorter. Pauses for effect, a laugh you have to wait out, a demo that stalls, a slide that will not advance, and any question from the room are all invisible to a word count.
The practical correction is to leave headroom rather than to adjust the rate. Then check the draft with Word Counter as you write, run the finished version through Teleprompter at the speed you intend to use, and time a real rehearsal against Online Timer. If the script reads slower than you expect, Readability Checker is often the reason, since dense sentences take longer to say than their word count suggests.

