Fullscreen Teleprompter

For tutorial makers

Teleprompter for software tutorials

A teleprompter for software tutorials puts the narration on a screen next to the application you are showing, so the words you read and the clicks you make stay in the same order. It is useful when you record a screen walkthrough, a product demo or a how to video and you have to name buttons, menus and settings without hesitating. This guide covers the reading speed for a technical explanation, how to write the script so it matches what is on screen, and how to keep the script in a separate window so it never appears in the recording. The script stays in the browser of your own device, and nothing is uploaded.

Why a teleprompter for software tutorials helps

A screen tutorial has two jobs at once, and they pull in opposite directions. Your eyes follow the interface, and your mouth explains what just happened. The first time you see the interface you are learning it while you are filming it, so the pause between the click and the explanation grows without you noticing. In the edit that pause is the first thing a viewer complains about.

A teleprompter does not solve the clicking. It solves the wording. The sentences you read are fixed before you start, so you do not have to invent a sentence while your hand is still on the mouse, and you do not lose the technical terms you need to say exactly as they appear on screen.

  • You can name a button, a tab or a setting while it is visible, instead of describing it later.
  • You keep a consistent structure across episodes, because the script is written before the recording.
  • You can film an intro or a summary separately, with the same tool and the same pace.
  • You can re-record one paragraph of narration and keep the rest of the take.
  • You can switch from a full script to a list of bullet points for the parts you know well.

How to record a tutorial with a teleprompter in four steps

  1. Write the script screen by screen
    One paragraph per screen or per action, two or three sentences each. Say what the viewer sees, not what you did. If a paragraph only makes sense with the previous one, the jump with the arrow keys will confuse you.
  2. Paste it and set the speed
    Start at 130 words per minute and read the first paragraph out loud at your normal pace. Lower it by 10 words per minute if you have to drag the words.
  3. Open the script in a second window
    The prompter runs in your browser, so open it in a separate window and move it to a second monitor, or to a phone or tablet next to the laptop if you have one. Keep it off the screen you are capturing.
  4. Record thirty seconds and check the sync
    Record the first step and watch it with the sound on. If the words land before the click, slow down by 10 words per minute. If they land after, speed up or add a line to the paragraph.

The prompter only shows and scrolls the text. Your recording software (OBS, QuickTime, ScreenFlow or the built-in recorder) does the capture, exactly as before.

The reading speed for a technical explanation

Technical narration is slower than social video, because the viewer has to hold a new idea in their head while the interface changes on screen. People speak between 120 and 160 words per minute on camera, and a tutorial sits at the slow end of that range. The arrow keys change the speed by 5 words per minute while the text is moving, so you can slow down for a definition and speed up for a summary.

  • 110 to 120 words per minute: detailed walkthroughs with settings, formulas or configuration steps.
  • 130 words per minute: a normal software tutorial at an ordinary pace.
  • 140 to 150 words per minute: short product demos and update announcements.
  • 160 words per minute or more: quick tours of a landing page or a new feature in one take.

A 260 word script at 130 words per minute takes about 2 minutes. The editor shows the same estimate next to the word count, so you can check the length of a segment before you record it. A 10 minute tutorial is roughly 1,300 words, and a 20 minute one is about 2,600 words.

Say the name of the button, not the idea of it

The most common mistake in a tutorial is describing an action instead of naming the thing on screen. If the button says Export, the sentence should say Export, and it should say it at the moment the cursor reaches it. Viewers search for the exact label, and a tutorial that calls it Save as or Download sends them looking in the wrong place.

  • Write the exact label of every button, tab, menu and field you click on.
  • Say the shortcut as well when there is one, for example Control plus S.
  • Repeat the value you type, because the viewer will write it down.
  • Say where the result appears, not only how to produce it.
  • Read file names and paths exactly as they are, with the same capital letters.

Numbers and names are the parts worth scripting word for word. The rest of the explanation can be looser.

Keep the script in a window the recording never captures

Screen recordings usually capture one display or one window, and if the prompter shares that display the viewer sees your script scrolling across the interface. The fix is placement, not a setting: put the prompter on the other monitor, on a phone or on a tablet, and capture only the screen with the application.

  • Two monitors: the application on the main screen, the prompter on the second one.
  • One monitor: capture a single window instead of the whole display, and move the prompter off the captured area.
  • One screen and a phone: open the page on the phone and read from there.
  • Full screen recording: record a second take of the interface on its own, and narrate both with the same script.

The prompter has four screen backgrounds, including the yellow of old television sets and a soft grey. On a screen recording that ends up in the frame, pick the one that reads as part of your video rather than as a piece of software.

Re-record one step instead of the whole tutorial

A tutorial that takes twenty minutes to film is expensive to re-film, so most mistakes should not be filmed again. The arrow keys jump between paragraphs, so you can leave the text on the step that went wrong, press the left arrow to go back and record that one piece with the same take of the screen.

  • Give each step its own paragraph, so a mistake costs one paragraph and not the whole video.
  • Save the script under a name with the version number, for example tutorial v3, and keep the old one.
  • Export the script to a .txt or .md file before a long session, in case the browser data is cleared.
  • The countdown can be 0, 3, 5 or 10 seconds, which gives you a moment to find the cursor before you speak.

The keyboard shortcuts that keep the take clean

Everything below works while the prompter is open, so you do not have to stop the recording to change the text, the speed or the size of the letters. Press the question mark in the editor to see the same list on screen.

Key What it does
Space Start or pause the scrolling
Arrow up Increase the speed by 5 words per minute
Arrow down Decrease the speed by 5 words per minute
Arrow right Jump to the next paragraph
Arrow left Jump to the previous paragraph
R Restart the script from the beginning
+ Increase the font size by 2 pixels
- Decrease the font size by 2 pixels
M Mirror the text horizontally
V Mirror the text vertically
F Switch to full screen
Esc Close the teleprompter
Ctrl + Enter Open the teleprompter from the editor
? Show the list of shortcuts

A Bluetooth presentation remote does the same job: the play button starts and pauses, the direction pad changes the speed and jumps between paragraphs.

References and tools

These are the official documents for the recording side, if you need to go deeper on how to capture a window or a display.

Frequently asked questions

Can I use a teleprompter while recording my screen?
Yes. The prompter is a normal browser window, so any screen recording software keeps working exactly as before. Put the prompter on a second monitor, on a phone or on a tablet, and capture only the display that shows the application. That way the script never appears in the video.
How fast should I read a software tutorial?
Around 130 words per minute is a good starting point. Technical explanations are slower than talking head videos because the viewer has to follow the interface at the same time. Read the first paragraph out loud and adjust by 10 words per minute until the words land with the clicks rather than before or after them.
What if I forget what to say in the middle of a tutorial?
That is what the paragraph jump is for. You can move to the previous paragraph with the left arrow key and read from there, or pause with the space bar, look at your notes and carry on. The text stays where it is, so a pause of a few seconds does not cost you the take.
Can I keep my tutorial scripts between recordings?
Yes. The editor keeps up to 10 scripts in the browser of your own device, each with a name, a word count and the date of the last change. You can load one, update it and export it to a .txt or .md file. Nothing is uploaded and there is no account to sign in to.

Open the teleprompter for your next tutorial

Open the teleprompter, paste the script of your tutorial and set the speed in words per minute. The text scrolls at your pace while you click, the script stays on your device and there is nothing to install.

Open the teleprompter

Support this project

If you'd like to support the project, take a look at these beautiful illustrated products. I'm also a fantasy illustrator, and you can support me by buying prints. I'm sure you'll find something special for you, for a friend or for family.