How to read a script while looking at the camera (without looking like you're reading)
By Zakaria Reziki · · 8 min read
To read a script while looking at the camera, put the words right under the lens and write them for the ear. People can tell you're reading from your eyes and your voice. The eyes sweep side to side and drop at line ends. The voice goes flat and fast, with pauses in the wrong places. Fix the eyes with a narrow column right under the camera. Fix the voice by writing for the ear, marking pauses, and rehearsing aloud.
What gives away that you're reading?
Six tells give most scripts away:
- Eye sweep. Eyes track left to right across a line, then snap back. Viewers notice this most.
- Eyes dropping at line ends. Your gaze falls to find the next line, or to the trackpad to scroll.
- Flat intonation. Every sentence has the same melody, because you are decoding words rather than meaning them.
- Reading too fast. Reading pace runs ahead of speaking pace, and listeners can't keep up.
- Pauses in the wrong places. You pause where the line breaks, not where the thought ends.
- Written language. Long clauses and words like “utilise” nobody says out loud.
The first two are about where the text sits. The last four are about the script and your delivery.
Keep the text in a narrow column near the camera
Horizontal eye movement is the most visible. Chen's CHI 2002 study found people are an order of magnitude less sensitive to gaze below their eyes than to gaze left, right or above. So the width of your text matters more than its height. At 55 cm from the screen:
| Column width | Eye travel per line | Typical example |
|---|---|---|
| 30 cm | ~30° | A document window across a laptop screen |
| 20 cm | ~21° | A half-width notes window |
| 12 cm | ~12.5° | A narrow prompter column |
| 8 cm | ~8° | A compact prompter under the notch |
Aim for 5–8 words per line and a column centred on the lens. Put the current line as close to the camera as you can: viewers perceive eye contact at about 2° below it, which is about 2 cm at laptop distance. See where to look on a video call for the research and geometry.
Write the script for the ear, not the page
A script written to be read silently will sound read aloud. Rewrite it so it sounds like you talking. Our guide to writing a teleprompter script covers structure. For delivery, focus on these edits:
- One idea per sentence. Split anything with more than one comma.
- Use contractions: “it's”, “we're”, “don't”.
- Write numbers the way you say them: “about two and a half million”, not “2,473,000”.
- Put the point at the end of the sentence, where your voice naturally lands.
Before: “Utilising the new dashboard, which was released last quarter, teams can now monitor performance across all regions.”
After: “We shipped a new dashboard last quarter. Now you can see every region in one place.”
Mark pauses and emphasis in the script
Pausing at line breaks is the clearest sign of reading. Take control of the breaks instead. A simple marking system:
| Mark | Meaning |
|---|---|
| New line | End of a phrase. Keep going unless there is a pause mark. |
| / | Short pause, a breath |
| // | Full stop pause, let it land |
| CAPS on one word | Stress this word |
| Blank line | New section. Reset, glance away, come back. |
Example, as it would appear on screen:
One stressed word per sentence is enough. Stressing several flattens them all again.
Slow down to a speaking pace
Many people read aloud faster than they talk, and speed flattens intonation. A quick check: time yourself reading 150 words. 150 words per minute is a common benchmark for a steady conversational pace (it is what Cuey uses for its time estimates), so that should take about a minute. If you finish in 45 seconds, you are rushing. Our teleprompter words-per-minute guide covers pace by format, and the speaking time calculator tells you how long a script runs at the pace you choose.
Rehearse in three passes
- Pass 1, aloud, off camera. Read the whole script out loud. Every time you stumble, rewrite that line. Stumbles are almost always written-language problems.
- Pass 2, for meaning. Read it again and add pause and stress marks. Ask what each sentence is for.
- Pass 3, on camera. Record it. Watch once with the sound off, checking only your eyes. Then listen once without watching, checking only your voice.
By the third pass you know where each sentence is going, so you glance at the text rather than decode it. That is the real difference between reading and speaking from a script.
Look away on purpose, then come back
In conversation, people look away briefly when they think, then look back. A fixed, unblinking stare at the lens for three minutes looks odd in its own way. Use the blank lines between sections: glance off to the side for a moment as you start a new thought, then return to the camera for the key sentence. Keep these glances short and deliberate, not a drift down to the text.
Stop scrolling by hand
Manual scrolling sends your eyes down to the trackpad or to find your place. A timed auto-scroll fixes that but sets your pace for you. Speed up and you wait. Slow down and the text leaves without you.
Cuey gives you three ways around this. Read mode scrolls on a timer at a speed you set. Follow mode, Voice Follow, listens to you, matches your words to the script and moves on when you reach the next line. If you pause or ad-lib, it waits. Notes mode is for bullet points you step through by hand when you would rather talk freely. All three keep the text in a small window right under the camera.
Checklist before you record
- Text in a column 8–12 cm wide, centred under the camera.
- 5–8 words per line, broken at thought boundaries.
- Contractions, short sentences, numbers written as spoken.
- Pause marks and one stressed word per sentence.
- 150 words take you about a minute.
- Three rehearsal passes, the last one recorded.
- No hand on the trackpad while you speak.