Teleprompter Speed: What WPM Should You Set? (With Cheat Sheet)
"What speed should I set my teleprompter to?" is the most-asked question in every prompter forum โ and the most common answer, "around 20", is useless without context. Speed sliders aren't standardized: 20 in one app is a crawl, in another it's a horse race. The only number that transfers between tools, scripts, and setups is words per minute (WPM) โ your real speaking pace.
Get that number right and every other setting follows from arithmetic. Here's the whole chain: finding your WPM, converting it to scroll speed, and calibrating the result so the prompter follows you instead of dragging you.
---
1. Start with your real WPM (not the app's default)
Most people believe they know how fast they talk. Most people are wrong in the same direction: scripts timed by "reading speed" run 30โ50% longer spoken aloud, because silent reading skips the breathing, the emphasis, and the consonants.
Typical on-camera ranges:
| Content type | Typical WPM | Why |
|---|---|---|
| Tutorials, explainers | 120โ140 | viewers need processing time |
| Talking-head YouTube | 130โ150 | natural conversation pace |
| Energetic Shorts/Reels/TikTok | 150โ170 | pace is part of the format |
| Formal speech, church reading | 100โ130 | gravity lives in the pauses |
| Podcast intro / scripted segment | 130โ145 | radio pacing |
To measure yours: take 150 words of an actual script (not a tongue twister), read it aloud as if explaining to a friend, and time it. 60 seconds โ 150 WPM; 70 seconds โ 129 WPM. Do it twice โ the second read is closer to your on-camera reality. I've gone deeper on choosing a target pace in what's the ideal speaking pace for video.
---
2. Why the same WPM needs different scroll settings
Here's what the "just tell me the number" crowd misses: a prompter doesn't scroll words per minute โ it scrolls lines per minute. And how many words fit on a line depends on your font size and column width:
Lines per minute = WPM รท words per line
| Your WPM | 4 words/line (large font) | 6 words/line | 8 words/line (small font) |
|---|---|---|---|
| 120 | 30 lines/min | 20 lines/min | 15 lines/min |
| 140 | 35 | 23 | 18 |
| 160 | 40 | 27 | 20 |
Same speaker, same script โ the required scroll rate doubles between a small-font wide column and a large-font narrow one. This is why copying someone else's "speed 22" never works: unless you also copy their font size, window width, and speaking pace, their number means nothing on your screen.
Practical consequence: fix your layout first (font size from your camera distance, column ~40โ50 characters โ the setup logic is in the complete beginner's guide), and only then tune speed. Change the layout later and you re-tune the speed, no way around it.
---
3. The 3-pass calibration method
Forget dialing in speed by feel mid-recording. Three passes, five minutes, done:
Pass 1 โ cold read, no prompter. Read the script aloud at your natural pace and time it. This is your ground truth. A 420-word script in 3:00 = 140 WPM.
Pass 2 โ race the prompter. Start the scroll and read along without adjusting anything. If you finish before the prompter, it's too slow; if it drags you forward, too fast. Adjust until the prompter and your voice finish within a couple of seconds of each other.
Pass 3 โ subtract 10%. Here's the counterintuitive one: on the real take, nerves speed you up in the first 30 seconds, then pauses and emphasis slow you down overall. A prompter set exactly to rehearsal pace feels subtly rushed on camera. Nudge it one notch slower than perfect โ you should feel like the prompter is very slightly waiting for you. That margin is where natural delivery lives.
If your tool supports live speed adjustment, resist using it as a crutch mid-take; it's for drift correction, not for chasing a bad baseline.
---
4. One speed is still a compromise โ time your sections
A constant scroll rate assumes your whole script flows at one pace. Real scripts don't: hooks are punchy, explanations breathe, calls-to-action punch again. With one averaged speed, the prompter is slightly wrong everywhere โ slightly ahead during your careful explanation, slightly behind on your rapid-fire list.
The fix isn't a smarter slider; it's knowing your per-section timing before you record. Split the script at natural breaks, time each section at its own pace, and you'll know that the intro runs 0:22, the demo 1:40, the outro 0:15 โ and where you can afford to slow down.
That per-section math is exactly what ScriptPacer does: paste your script, split sections with --- dividers, set your WPM, and it shows the duration of every section plus the total โ then feeds the same script straight into a browser teleprompter with the scroll speed to match. Free, no signup, and the script never leaves your device.
---
Quick answers
- "What WPM should I set?" โ Your measured cold-read pace, minus ~10%. For most creators that lands between 115 and 145 on the prompter.
- "Should beginners use slower speeds?" โ Yes, but fix it in the script: write shorter sentences and mark pauses. A slow scroll over dense text still reads as robotic.
- "Does speed change between platforms?" โ Your speaking pace changes (Shorts โ +15โ20% vs. tutorials), so re-time the script per format instead of reusing one setting.
Measure once, calibrate in three passes, and the speed question disappears โ which is the whole point. The prompter you stop thinking about is the one that's set correctly.