How to read a teleprompter naturally

Why reading aloud sounds like reading aloud

Talking and reading are different jobs, and a camera records the difference.

When you talk, you assemble a sentence a phrase at a time. You pause to pick a word. Your eyes drift while you think. Your pitch falls at the end of a thought because you knew the thought was ending. When you read, all of that has been decided in advance. The words arrive in order at a fixed rate, your eyes track a line instead of wandering, and your intonation follows the punctuation rather than the meaning.

Nobody watching can see your prompter. They can see all three of those.

That is the whole of what "sounds read" means. It is not a quality some people are born with. It is a short list of specific behaviours, and each one has a fix that takes about a minute.

Three of them do most of the work. Get the script close to the lens. Set the speed to the rate you talk rather than the rate you read. Keep your eyes a phrase ahead of your mouth.

How close the script has to be to the lens

The number that matters is not the distance between the script and the camera. It is the angle between them, measured from where you are sitting.

Divide the offset by your distance from the camera and multiply by 57. That gives you degrees, closely enough for this.

A laptop at arm's length, 60 cm away, with the reading line 8 cm below the lens: about 8 degrees.
The same laptop and the same 8 cm, read from 1.2 m away: about 4 degrees.
A phone propped 12 cm to the side of the camera, read from 50 cm: about 14 degrees.

Under about 5 degrees most viewers stop registering it as looking away. Around 10 degrees it is unmistakable, and it reads as evasive rather than as reading, which is worse. They cannot tell what you are looking at, only that it is not them.

You have two ways to shrink the angle and one of them is free. Move the script closer to the lens, or move yourself further from the camera. Sitting back half a metre and framing tighter halves the angle without buying anything.

The third way is a beam splitter, which puts the script and the lens in the same place and takes the angle to zero. That is a rig with glass, a hood and a tripod, and most people reading to a webcam do not need one. If you shoot close-ups, or hold a look at the lens for a minute at a time, it is the only arrangement that fully works. Setting up mirror mode with a beam splitter covers what the parts are and how they sit.

One detail about the stage on this site is worth knowing before you arrange anything: the reading line sits in the middle of the viewport. On a laptop the camera is at the top of the screen, so fullscreen is the worst case, because it puts the line as far from the lens as the display allows. A short browser window parked along the top edge of the screen puts the same reading line just under the camera. On a second screen beside the camera, fullscreen is fine.

Set the speed to your voice, not to a number

Most people talk somewhere between 120 and 160 words per minute on camera. Where you sit inside that range is a fact about you, and it barely moves.

You can measure it in thirty seconds. Read half a paragraph of your own draft out loud at the pace you would actually use, time it, count the words, and scale up. Or start at 130, read a paragraph, and adjust once.

What you should not do is set it to a number you would like to be true. A roll that runs faster than you talk makes you chase it, and chasing flattens everything. You stop pausing. You clip the ends of sentences. You sound hurried in a way that has nothing to do with what you are saying. A roll that runs too slow leaves you waiting for the next line, and the pauses land between the wrong words.

There is a tell for this, and it is easier to watch than to feel. The script moves upward past a fixed line, so text you have not said yet is below that line. If you keep catching yourself speaking lines that are still below it, you are ahead of the roll and it is too slow. If your voice is on a line that has already gone past, the roll is too fast. Take ten words per minute off and read the same paragraph again.

Speed measured in words per minute rather than pixels per second is what makes that number portable. Change the text size or the window width and it still means the same thing, so a pace you set on a laptop is the same pace on a tablet propped beside the lens.

Read a phrase ahead of your mouth

This is the actual skill, and it is what separates people who look comfortable on a prompter from people who do not.

Fluent readers run their eyes ahead of their voice. The gap is small, a few words or sometimes a whole line, but it is what lets you put the right shape on a sentence, because you have already seen where the sentence is going. Without the gap you are discovering each word as you say it, and that is precisely what a listener hears when someone reads badly.

You can practise it away from the camera. Read a paragraph silently, look up, and say it. Then do the same thing with the prompter running: let your eye finish a line before your mouth starts it, and hold that offset. It feels like doing two things at once for about ten minutes, and then it stops feeling like anything at all.

The gap needs somewhere to live. If the line you are speaking is the last one visible, there is nothing to read ahead into. That is a text size problem more often than a speed problem.

Size the text for your eyes, not for the screen

The right text size depends on how far away you are sitting, which is why it is a control rather than a default someone picked.

Two rules decide it. Lines have to be short enough that your eyes do not visibly sweep across them, because a wide line of small text produces a left-to-right flick the camera picks up as clearly as looking away does. And there has to be context under the reading line as well as over it, or you have nowhere to read ahead into.

On a small screen those two pull against each other, and the resolution is usually to narrow the window rather than shrink the text. Fewer words per line at a size you can take in at a glance beats more words you have to work across.

Three failures worth naming

Catching up ruins whole takes. You fall behind, you speed up to close the gap, and your pace never comes back down. Do not try to save it. Recue, drop the speed, start again. A recue and a second take cost less than editing around forty seconds of gabbling.

The stare comes from the reading itself, because reading suppresses blinking. You end up with an unblinking, slightly widened look that reads as intensity or as nerves depending on the viewer. Do one take where you deliberately blink at every full stop. It feels absurd and it looks normal, and after that one take it stops being deliberate.

The flat ending is what happens when the punctuation does the work instead of the meaning, and every sentence lands on the same falling note. Pick the three sentences that actually matter and slow down on those rather than getting louder on them. Pace carries emphasis better than volume, and it survives compression.

A run-through that takes four minutes

Paste the script and read the duration estimate. If it is already over length, cut it now rather than in the edit.
Set the speed, read one paragraph out loud, adjust once, and leave it alone.
Set the text size until you have two lines of context below the reading line.
Frame the shot and check the angle in your camera's own preview, from where you will actually be sitting rather than from where you set it up.
Do one take with the three second countdown on, and throw that take away.

The thrown-away take is not a formality. It is where you find the sentence you cannot say, the name you cannot pronounce, and the paragraph that was thirty words too long. Every one of those is cheaper to fix before the real take than after it.

When the script should follow you instead

If you pause a lot, or the length of your pauses changes from take to take, a fixed rate fights you however well it is set.

Voice follow listens while you read and moves the script to match. Slow down and it slows, stop and it stops. It is off until you turn it on, and where your audio goes depends on your browser: the switch says which path you are on before you enable anything, and the voice follow page sets out which browsers sit on which side.

What a prompter cannot fix

A prompter fixes where your eyes point. It does not fix a sentence that was never going to survive being said out loud.

If you have done all of the above and it still sounds read, the problem has moved upstream into the script: a subordinate clause you have to hold in your head, a number with three decimal places, a pronoun pointing back four sentences to something the listener has already forgotten. Writing scripts for the ear is about that half of the job.

The prompter itself is on the home page. Paste a script, set a speed, and read.