If your voice-activated teleprompter isn’t working, there are four things to check — and you should check them in order, because they’re ranked from most common to least. The four causes are: microphone permissions, internet connection, language settings, and speaking too far off-script. Most troubleshooting confusion comes from skipping the obvious causes and jumping to the complex ones. This post covers each in order with specific fixes, plus what a voice-tracking teleprompter built with proper tolerance handles differently.

Cause 1 — microphone permissions (most common)

This is almost always the first thing to check, and it’s the cause nine times out of ten if your teleprompter was working yesterday and isn’t today. Operating system updates — particularly on iOS and Android — frequently reset or revoke microphone permissions for individual apps without warning. If the app doesn’t have permission, it can’t hear you, and voice tracking silently fails.

On iOS: Settings → Privacy & Security → Microphone, then confirm your teleprompter app has access.

On Android: Settings → Apps → [your teleprompter] → Permissions → Microphone, check it’s allowed.

If the permission was off, turn it on, fully close the app, and relaunch. Don’t just background it — close it from the app switcher and start fresh.

Cause 2 — internet connection (for cloud-based apps)

Most voice-activated teleprompters — especially browser-based ones — route audio through cloud speech recognition. That means they need a stable internet connection, and weak or intermittent Wi-Fi produces unreliable scrolling.

A quick test: put your device in airplane mode and try voice tracking. If it stops working entirely, you’re on a cloud-based app and your Wi-Fi is the variable. If it keeps working, voice tracking is running on-device and your internet isn’t the problem.

Fix: move closer to the router, use a wired connection if possible, or switch to a teleprompter with on-device voice tracking that doesn’t depend on your connection quality.

Cause 3 — language settings

Many teleprompter apps default to US English for voice recognition, but accent and dialect matter more than the category admits. If you’re speaking UK English, Australian English, or any non-US variant, a US-tuned speech engine will struggle — not with every word, but with enough words to make tracking unreliable.

Check your app’s language settings and match them to how you actually speak. If the option is available, en-GB, en-AU, or en-IN will track those accents much more reliably than en-US. Some apps only offer a single “English” option, in which case your tracking accuracy will be capped.

Steady Cue launches with en-US and en-GB; more languages are on the roadmap.

Cause 4 — speaking too far off-script

This is the one most people miss. Voice tracking works by matching what you say to what’s written in the script. If you ad-lib, skip a line, misread a word, or paraphrase — which solo creators all do unconsciously — the app can lose your position. It’s not broken; it just can’t find you.

The diagnostic test: pick a script you wrote yourself and read it verbatim for 30 seconds. If voice tracking works perfectly then, the issue is how closely you’re reading, not the app. A teleprompter built with tolerance for natural delivery will handle real-world speaking better than a strict matcher. But no teleprompter will handle pure ad-libbing.

A note on external microphones

One extra cause that deserves mention: Bluetooth lavalier microphones (Rode Wireless GO, DJI Mic, etc.) can break voice tracking on some apps due to audio latency. Wired lavaliers are noticeably more reliable. If you recently added a wireless mic and voice tracking started failing, try a wired one as a diagnostic.

The bottom line

Nine out of ten “voice-activated teleprompter not working” problems are one of these four causes. Check them in order — permissions first, connection second, language third, speaking style fourth — and one of them is almost always the fix.