Talk2Camera
Menu
en-GB
teleprompter

The ideal teleprompter reading speed

The number everyone asks for is an average. An average, held for two minutes, is what recital sounds like.

Ask what speed to set a teleprompter to and you will get a number — most guides settle somewhere near 150 words per minute, because that is roughly where conversational English averages out. The number is honest and the advice is not, because an average is not a pace. Nobody speaks at 150 words a minute. They speak at 120 for one sentence and 180 for the next, and the average is what those two numbers leave behind when you flatten them. Set the scroll to any fixed rate and you become the flattener: every sentence now takes exactly the time the scroll allows it, the emphasis evens out, and the delivery sounds recited even when the voice is warm and the eyes are steady. The speed was never the problem. The fixedness is.

Listen to someone explaining a thing they know well and the pace never sits still. They slow down when a point matters, because slowing down is how speech does emphasis. They speed up through the parts a listener can be trusted to follow. And they stop entirely before a change of subject — a stop that does real work, telling the listener to put one idea down before picking up the next. None of this is technique; it is what speaking sounds like when the speaker means it. A script scrolling at one speed strips all of it out. You cannot linger on the sentence that deserves it, because the text runs on without you. You cannot press through the familiar stretch, because the words are not there yet. The variation a listener trusts is exactly what the fixed scroll removes.

A fixed pace still has honest uses, which is why Talk2Camera keeps one: set a speed, let the script run, and a progress bar shows the time remaining — useful when a video has to land inside a duration, and in rehearsal, where feeling the script fight the clock tells you which sentences are too long. But for the take itself, voice follow removes the question rather than answering it. The script scrolls as you speak, with recognition running on the device. Pause, and it waits. Slow down for the sentence that matters, and it slows with you. Skip a line, and it catches up. There is no speed to choose because the text is following you rather than the other way round — and "what speed should I set?" stops being a question at all.

If you still want to know your pace — and it is worth knowing — measure it rather than borrowing it. Record a take of a script you know, delivered as if explaining it to one person, and look at the number afterwards: delivery metrics report your pace in words per minute, measured on the device from the take itself. Then record the same script again, deliberately slower than feels comfortable. Most people find the slower take sounds more confident, not less — what feels laboured from inside reads as considered from outside. Your working pace will turn out to be a range rather than a number, and that is fine. Knowing the range tells you how long a script really runs, and it tells you something useful whenever a take comes back at the top of it: you were probably rushing.

Mentioned in this article

Manual and timed scrolling

Drive the script yourself, or set a pace and let it run. Progress bar with the time remaining.

Voice follow

The script scrolls as you speak. Pause and it waits; skip a sentence and it catches up. Recognition runs on the device.

Delivery metrics

Pace in words per minute, filler-word count, and how much of your script you covered. Measured on the device from the take itself.