Use a teleprompter for YouTube without rushing the demo.

A tutorial gets awkward when the script keeps moving while your hands are still doing the demonstration. Write the camera lines and the demonstration as separate beats. Let the reader wait for you.

Write the shot plan before the full script

Take a spreadsheet tutorial. The viewer needs to see the chart being made, then hear what it means. A single scrolling paragraph mixes those jobs together. Separate the lines you will say to camera from the actions you will show on screen.

Use plain labels in your draft: CAMERA, DEMO and PICKUP. The reader displays those labels as ordinary text. They do not switch cameras, trigger a screen recording or pause playback for you.

CAMERA
This chart answers one question:
which month had the most orders?

DEMO — pause the reader here
Select the data. Insert the chart.
Show the month labels.

PICKUP — return to camera
March is the busiest month in this example.
That is the point I want the chart to make.

The month is part of this fictional example, not a result from a customer or a study. Replace the demonstration and conclusion with what your own screen actually shows.

Budget for what the viewer needs to see

Here is a planning calculation: 90 spoken words at 120 words per minute take about 45 seconds. Add a 30-second demonstration and the sequence becomes roughly 75 seconds before extra pauses. That is arithmetic for this example, not a recommended YouTube video length.

The app’s estimate counts all displayed words, including your production notes. It also cannot know how long selecting a menu or waiting for an export will take. Time a rehearsal with the actual demonstration. If the segment is too long, cut a repeated explanation before speeding up the reader.

Use your own 30-second retention data

YouTube’s Intro metric measures the percentage of viewers still watching after 30 seconds. At an assumed 120 words per minute, that is about 60 spoken words before allowing for pauses. Read your first 60 words: have you shown or explained the thing your title promised, or are you still introducing the channel?

After publishing, compare that opening with your audience-retention graph. A dip during an explanation is a reason to watch that moment again, not proof that the teleprompter caused it. Keep the draft with your shot notes so you can connect the numbers to what viewers actually saw.

Check the first sentence on camera

Place the reader close to the lens and read a sentence containing both a short and a long line. Watch that clip back. If your gaze sweeps sideways, increase the side margins. If you lean toward the screen, increase the text size. Change one setting, then repeat the same sentence so you can compare the result.

A preview window is not enough to judge eye contact. Look at the recorded clip at the size a viewer will watch it. If your camera sits behind reflective glass, use the mirror setup guide instead of trying to compensate with window placement.

Retake one complete thought

When a line goes wrong, pause, scroll back to the start of that thought and leave a short silence before trying again. Restarting halfway through a sentence makes the edit harder to hide. Include the lead-in to a gesture if your hands are in shot.

While paused, click the script to replace words that keep tripping you up. Space inserts a space while you are editing; use Play when the revised line is ready. Outside text entry, Space pauses and resumes without repeating the countdown.

The browser’s Record video feature captures a local camera and optional microphone, not your tutorial screen. Record the screen separately and assemble the shots in your editor. For reading and recording on an iPhone, Teleprompter Pal is the companion app, currently in private beta.