How to write a teleprompter script that sounds like you talking
By Zakaria Reziki · · 7 min read
A teleprompter script is written to be heard, not read. Use short sentences, one idea per line, contractions, and numbers spelled the way you'd say them. Then read the whole thing out loud and rewrite every line you trip over. Below: the rules, a before/after rewrite, and a template you can reuse.
Write for the ear, not the page
Written English leans on things listeners never see: commas that group ideas, parentheses, headings, the option to reread. Spoken English has none of that. The listener gets each sentence once, in order. So the rules change:
- Short sentences. Aim for sentences you can say in one breath. If a sentence has two commas, it's probably two sentences.
- Subject first. “We cut setup time in half” beats “Setup time, which used to be the biggest complaint, has been cut in half.”
- Contractions. “It's”, “you'll”, “don't”. Without them you sound like you're reading a legal notice.
- Plain words. “Use” not “utilise”. “Help” not “facilitate”. Say what you'd say across a table.
- Repeat the key point. On a page, repetition is padding. Out loud, it's how people remember.
Write numbers and symbols the way you say them
Anything you have to translate while reading will make you pause or stumble. Do the translation when you write:
| Don't write | Write |
|---|---|
| $1.25M | one and a quarter million dollars |
| ~40% | about forty percent |
| 3x faster | three times faster |
| Q3 2026 | the third quarter of twenty twenty-six |
| e.g. / i.e. / etc. | for example / that is / and so on |
| example.com/pricing | example dot com slash pricing |
| API, SQL | A-P-I, sequel (however you actually say it) |
Round where precision doesn't matter. “Almost half” is easier to say and to remember than “forty-seven point three percent”.
Format for a small window next to the camera
The best place to read is a narrow strip just below the camera, because that's where your eyes look closest to the lens. That strip is small, so the formatting has to suit it:
- One idea per line. Break lines at natural phrase boundaries, never mid-phrase. Your eye picks up a whole line at once.
- Short lines. A narrow column keeps your eyes from sweeping left and right. People are far more sensitive to sideways gaze than to a slight downward look.
- Blank line between sections. It shows you where to breathe and where a cut can go in the edit.
- Sentence case, large text. All caps is slower to read. Bigger text with fewer words per line beats small text with more.
For the reading technique itself (where to put the window, how to keep your eyes still), see how to read a script without looking like you're reading.
Mark pauses and emphasis (sparingly)
Pick a small, consistent set of markers and don't invent new ones mid-script:
- / a short breath inside a sentence.
- Blank line a full stop and a beat, or a topic change.
- One word in caps or bold the word you stress. One per sentence at most. If everything is stressed, nothing is.
- [square brackets] stage directions you don't say: [show dashboard], [smile], [hold up product].
A before/after rewrite
Here's a typical paragraph written for a page, then rewritten for a teleprompter.
Same facts. The rewrite is longer in lines but faster to say, because each line is one breath and one idea. The dropped detail (“several performance improvements”) either earns its own line or goes.
A reusable script template: hook → point → proof → ask
Most short videos, demos and pitches fit this shape. Word budgets below are for a 60-second video at 150 words per minute, so 150 words in total. Scale them for longer pieces, or check your draft with the speaking time calculator.
| Section | Job | ~Words (60 s) |
|---|---|---|
| Hook | Name the viewer's problem or a surprising fact in one or two lines. | 20 |
| Point | The one thing you want them to take away. | 40 |
| Proof | A demo, example, number or short story that shows the point is true. | 60 |
| Ask | One next step: try it, reply, book a call, subscribe. | 30 |
The shape also works for longer videos: repeat point → proof for each section, and keep one hook and one ask. For a full recording workflow, see how to record a YouTube video with a script.
The read-aloud edit pass
Never ship a script you haven't said out loud. Do this pass before you record:
- Read it aloud at recording pace. Mark every place you stumble, run out of breath or change a word without meaning to.
- Rewrite the marked lines using the words you actually said. Your mouth usually knows the better version.
- Cut anything you'd skip in conversation: throat-clearing openers, “in order to”, stacked adjectives.
- Check the length. Time the read, or count words and divide by your rate. The teleprompter words per minute guide has a length table.
- Read it once more on the prompter itself. Line breaks that look fine in a document can land badly in a narrow window.
Using your script with Cuey
When the script is ready, copy it and press ⇧⌘V to paste it straight into Cuey. It sits under the camera by default, and you can change the text size and window size to suit how short your lines are. In Read mode it advances at a speed you set; with Voice Follow it listens and moves on when you reach the next line, so a pause for emphasis doesn't leave you behind. ⇧⌘P starts and stops the prompter.
Summary
- Short sentences, contractions, plain words, subject first.
- One idea per line, short lines, sentence case, blank lines between sections.
- Write numbers and symbols as spoken words.
- Hook → point → proof → ask, sized to your speaking rate.
- Read it aloud and rewrite what you stumble on.