You paste your script into the teleprompter, hit record, and within twelve seconds you’re already behind the scroll. Not because you read slowly, but because the script was written to be read silently off a laptop, in long paragraphs, with clauses that only make sense if your eyes can jump backward. On a phone screen, at scroll speed, none of that survives.
Short answer: A good teleprompter workflow is 80% script formatting and 20% reading. Write in short, self-contained chunks of 8 to 12 words, one idea per line, no clauses that require backtracking. Then paste that text into DemoScope’s built-in teleprompter on iPhone or iPad, which auto-scrolls at an adjustable speed and stays invisible in the recorded video.
Why does the script matter more than the teleprompter settings?
The scroll speed slider gets all the attention, and it is the wrong dial to be fiddling with. A teleprompter scrolls at a constant rate. Your speech does not. You slow down for a product name, speed up through a transition, and pause entirely while a screen loads. Any script written as flowing prose forces you to fight that mismatch continuously.
Formatting the script fixes it structurally. When each line is one complete thought, you can absorb it in a single glance, look away at the screen you are demoing, and come back without losing your place. The line is the unit of recovery. Long paragraphs give you nothing to recover to.
This is the part most people skip, and it is the root cause behind a lot of the problems covered in teleprompter workflow: why most creators get mobile script recording wrong. The reading feels hard because the writing made it hard.
How should you format a demo script for a mobile teleprompter?
Five formatting rules that hold up on a phone screen:
Cap lines at 8 to 12 words. That is roughly one breath. If a line runs longer, split it at the nearest natural pause, even if that leaves an orphan fragment. Fragments read fine out loud.
One idea per line, no dependent clauses across lines. “When you tap the settings icon, which lives in the top right, you’ll see three options” becomes three lines: “Tap the settings icon.” / “It’s in the top right.” / “You’ll see three options.”
Front-load the verb on action lines. “Tap,” “open,” “swipe,” “watch.” You are narrating your own hands, and the verb tells you what to do with them before you finish reading.
Write in blank-line blocks per demo step. Group the lines for a single on-screen action together, then leave a blank line. The blank space that scrolls past is your visual cue that a step just ended, which is exactly when you should be checking whether the screen caught up.
Spell out anything you might stumble on. Version numbers, URLs, API names. “iOS one four” instead of “iOS 14” if that is how you want it said. The teleprompter shows plain text, so whatever you type is what your eyes get.
What are the actual options for staying on script while recording?
DemoScope’s teleprompter overlays your script on your own screen during in-app recording and does not appear in the exported MP4, so viewers never see it. Here is how that compares to the other things creators try:
| Approach | Setup effort | Eye contact with camera | Risk of it appearing in the video |
|---|---|---|---|
| Memorize the whole script | High (multiple rehearsals) | Best | None |
| Bullet notes on paper beside you | Low | Poor (you look down) | None |
| Script on a second device propped up | Medium | Medium (off-axis) | None |
| Notes app open in split view | Low | Medium | High, it is on your screen |
| DemoScope teleprompter overlay | Low (paste text, set speed) | Good (script sits near the camera) | None, it is not recorded |
The overlay approach wins mostly on logistics. There is no second device to position, nothing to hold, and no chance of a notes panel ending up in the final recording. The tradeoff is that you are reading, which means the formatting work above is not optional. Reading badly formatted text on camera sounds exactly like reading badly formatted text on camera.
Where does script formatting interact with the rest of your recording setup?
Two practical points.
Touch indicators change how much you need to narrate. DemoScope shows an animated circle wherever you tap during in-app recording, with a customizable color. When the tap is visible, you do not need the line “now I’m tapping the button in the bottom left.” You can cut that line entirely and let the indicator do the work, which shortens your script and reduces how much you are reading rather than talking.
External PiP recording has no teleprompter. DemoScope’s External PiP mode activates a system-wide floating face cam so you can record any app on your iPhone, but iOS limits the tools available in that mode to Camera, PiP Border, and Text on screen. No teleprompter, no touch indicators. If your demo requires leaving DemoScope to record another app, plan for a bulleted memory outline instead of a full script, and keep segments short enough that you can hold them in your head.
That second point is worth deciding before you write anything. A script you can read and a script you have to remember are different documents, and rewriting one into the other after the fact wastes more time than planning the recording mode first.
How do you rehearse a formatted script without over-rehearsing?
Read it once out loud at your natural pace and time it. Then read it again while doing the taps, without recording. That second pass is where you find out your script assumes a screen loads instantly when it takes two seconds, or that you wrote four lines of narration for an action that takes one.
Fix the script, not your delivery. If a line always trips you, rewrite the line. If you are always waiting on the scroll, cut words. Three passes is usually enough. Past that you start sounding rehearsed rather than confident, which is the failure mode covered in mastering the teleprompter workflow: how to sound natural while recording on your iphone.
For dense material, version numbers, config steps, error states, the formatting rules get stricter, and advanced teleprompter workflow tips: handling technical demo scripts on iphone goes deeper on that. If you are building the process from scratch, how to build an efficient teleprompter workflow for mobile recording in 2026 covers the end-to-end sequence.
The takeaway: spend ten minutes reformatting the script before you spend an hour re-recording. DemoScope is worth a look if you want the teleprompter, face cam overlay, and touch indicators in one iPhone app. It is a $19.99 one-time purchase for Pro, which removes the watermark from exports, and there is a free tier if you want to test the workflow with a watermark first.
Frequently asked questions
How do you format a script for a teleprompter on iPhone?
Break the script into lines of 8 to 12 words, one complete idea per line, with no clauses that continue across a line break. Group lines into blocks by demo step and separate blocks with a blank line. This lets you read one line per glance and look back at your screen without losing your place while the text scrolls.
Does the teleprompter show up in the recorded video?
No. DemoScope’s teleprompter overlay is visible only to you on your own screen and is not captured in the exported MP4. The recording contains your screen, your face cam overlay, microphone audio, and device audio, but not the script text.
Can you use a teleprompter while recording a different app?
Not in DemoScope’s External PiP mode. External PiP recording lets you record any app on your iPhone with a floating face cam, but iOS limits the available tools in that mode to Camera, PiP Border, and Text on screen. The teleprompter and touch indicators only work in DemoScope’s in-app recording mode.
What scroll speed should a mobile teleprompter be set to?
Set it slightly slower than your natural reading pace, then let your script formatting absorb the difference. DemoScope’s teleprompter auto-scroll speed is adjustable, and the correct setting depends on your speaking rate and how much you pause for on-screen actions, so time one full read-through and adjust from there rather than guessing.
Do you need a full script or are bullet points enough?
A full formatted script works better for in-app recording where a teleprompter is available, and bullet points work better for External PiP recording where DemoScope’s teleprompter is not available. Decide which recording mode you are using before writing, because converting between the two formats afterward takes longer than writing the right one first.