If your teleprompter app crashes mid-recording, three things cause about 95% of the damage: memory overload from long scripts, the operating system killing the app in the background, and thermal throttling on your tablet during long shoots. All three are common, all three are fixable, and all three are symptoms of teleprompter apps that haven’t been engineered for real shoot-day conditions. This post breaks down each cause, gives you specific fixes, and covers what to look for in a teleprompter built to survive a full production session.

Cause 1 — memory overload

Teleprompter apps load your entire script into memory so they can scroll it smoothly. For short scripts of 500 or 1,000 words, this is trivial. But once you push into 5,000+ words — long-form YouTube videos, sermon notes, conference keynotes — the app’s memory footprint moves into the range where older devices start running out of RAM. Android tablets with 3GB or less are particularly vulnerable. The OS kills the app to protect system memory, and you lose your script along with it.

The fix: split long scripts into sections. Most teleprompter apps allow multiple scripts — break a 6,000-word piece into three 2,000-word sections and switch between them in the app. Steady Cue’s section markers feature makes this even smoother — mark your script with bracketed section titles and jump between them without reloading the whole file.

Closing other apps before recording also helps. Every background app is memory you’re taking away from the teleprompter.

Cause 2 — the OS kills the app in the background

iOS and Android both kill background apps to preserve battery and free up RAM. If you switch from the teleprompter to your camera app, answer a call, check a notification, or swipe to a messaging app mid-shoot, there’s a real chance the teleprompter gets suspended — and when you come back, the app has to cold-start and your position is lost.

iOS is particularly aggressive: the system suspends non-foreground apps in 3–5 seconds. On Android, behaviour varies by manufacturer — Samsung and Xiaomi both have aggressive battery-optimisation policies that specifically target apps not in the foreground.

The fix: run the teleprompter on a dedicated device — separate from your camera, separate from your phone. An old iPad or Android tablet mounted on your camera rig, doing nothing except running the teleprompter, almost never gets killed. A phone that’s also taking calls, streaming music, and checking email will.

If you must use one device, enable “Keep app awake” or “Disable battery optimisation” for the teleprompter. On Android: Settings → Apps → [Teleprompter] → Battery → Unrestricted. On iOS: enable “Background App Refresh” for the app specifically.

Cause 3 — thermal throttling

After an hour of continuous recording, your tablet warms up. Once it crosses an internal temperature threshold, the operating system automatically reduces CPU and GPU performance to avoid hardware damage. Apps doing real-time processing get hit first — voice recognition is particularly demanding. You might notice the prompter starting to stutter, lag, or eventually crash outright.

Thermal throttling is an especially nasty failure mode because it doesn’t happen immediately. It shows up 30 to 60 minutes into a shoot — right when you’ve built momentum and don’t want to stop.

The fix is mostly behavioural: don’t leave the tablet in direct sunlight during outdoor shoots; take 5–10 minute breaks every 30–45 minutes to let the device cool; if you’re in a studio, a small fan pointed at the back of the tablet works surprisingly well; and avoid the highest-brightness screen setting unless the light genuinely requires it.

What “built for shoot day” actually means

A teleprompter app engineered for real production conditions handles all three of these failure modes gracefully. It loads long scripts efficiently so memory doesn’t pin. It persists state so that if the OS suspends it, you come back where you were. And it’s lean enough on CPU that thermal throttling doesn’t hit it first.

These aren’t flashy features — they’re the unglamorous engineering that determines whether the app survives a real shoot or stops you mid-take. Steady Cue is built this way because we use it on our own shoot days and had to fix these problems for ourselves first.