โ† Back to Blog

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 typeTypical WPMWhy
Tutorials, explainers120โ€“140viewers need processing time
Talking-head YouTube130โ€“150natural conversation pace
Energetic Shorts/Reels/TikTok150โ€“170pace is part of the format
Formal speech, church reading100โ€“130gravity lives in the pauses
Podcast intro / scripted segment130โ€“145radio 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 WPM4 words/line (large font)6 words/line8 words/line (small font)
12030 lines/min20 lines/min15 lines/min
140352318
160402720

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.
"Why does my delivery sound rushed even at the right speed?" โ€” Layout mismatch: too many words per line forces horizontal eye travel that feels* like time pressure. Narrow the column.
  • "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.

Want to Deliver Snappy, Perfectly Timed Videos?

Practice your speaking pace for free! ScriptPacer calculates your WPM, gives you colored pacing glows, auto-saves multiple scripts, and includes a floating selfie camera preview. No signup needed.

Try ScriptPacer Free