Edits Teleprompter Not Scrolling? Check the Script, Speed and Phone Settings

If the Edits teleprompter jumps to the bottom or never moves, you do not need to keep restarting a full recording. Use a tiny script first. A thirty-second diagnostic can show you what to report and whether you can safely continue filming.

Meta confirms that Edits has an in-app teleprompter with adjustable text size and speed in its one-year update. The article does not document every button or guarantee identical behaviour on every phone. This guide was source-checked on September 15, 2026; it is not a hands-on device test.

Save the script before troubleshooting

Copy the complete script into a note outside Edits. Keep any existing takes and confirm important recordings open independently. If you have a partly finished project, preserve its source media before attempting broader app troubleshooting.

Do not clear Edits storage or reinstall it merely to reset scrolling. Google's Pixel app guidance warns that clearing app data erases saved information. An accessible copy of the script does not mean every video draft is backed up.

Write down phone model, operating system and Edits version. If a tutorial shows different controls, compare versions and platforms before assuming the feature is broken.

Identify what “not scrolling” means

There are several distinct symptoms:

• The teleprompter option is absent.
• The script is visible, but remains still when the relevant start action is used.
• The text immediately jumps to the end.
• Scrolling works, but the slowest available pace still feels too fast.
• The text moves correctly, but recording or audio fails.

For a missing feature, check the official app update and available creation mode. Do not download an unofficial modified app or give a third-party site your Instagram password to “unlock” a control.

If the script scrolls but no usable video is recorded, check that separately. A successful scrolling preview is not proof that the camera and microphone captured the take.

Run a four-line plain-text test

Use this original test script, without private or client information:

This is line one.
This is line two.
I will pause before line three.
This is the final line.

If your script-entry field adds unusual spacing when pasted, type the four sentences directly as a comparison. You are testing whether a short simple input behaves differently, not asserting that copied formatting causes every failure.

Set an available slow speed and a readable text size. Follow the start or record control that your installed version presents. Observe whether the text stays still, scrolls, jumps or stops at a consistent point.

Do not assume the teleprompter follows your voice. Meta's description confirms adjustable scrolling speed, not a universal voice-tracking mode that waits whenever you pause.

Check the available speed and reading setup

If the short test scrolls normally, restore your saved script in small sections. Remove large blank areas and accidental repeated paragraphs. Break sentences at natural thought boundaries so you do not have to search across a dense wall of text.

Rehearse from the distance and camera position you will actually use. A speed that seems slow while holding the phone may feel fast when it is on a tripod. Increase text size for comfortable reading, then reconsider pace rather than moving your face close to the screen.

Keep your wording conversational. A long sentence with several numbers can be difficult even when scrolling is working perfectly. Our natural teleprompter guide covers delivery; it is a different problem from the app skipping the entire script.

What about the reduced-animation workaround?

A creator discussion about a Pixel teleprompter failure reports text jumping to the bottom and an apparent improvement after changing reduced-animation settings. This is firsthand anecdotal evidence, not an official Meta diagnosis or a fix we reproduced.

Google documents Android's Remove animations setting as an accessibility control. If it is enabled, record that fact in your report. If you do not rely on it and are comfortable with animation, an optional brief comparison can help: note the original setting, change only that control, repeat the same harmless four-line test, then restore your preference.

Do not disable an accessibility setting you need or continue if the change causes discomfort. Do not alter developer animation scales or unrelated system settings based on a random tutorial. An app should be usable with your accessibility needs; a possible compatibility issue belongs in the support report.

On iPhone, Apple documents Reduce Motion, but that does not prove the reported Android workaround applies to iOS. Record the setting rather than assuming platform parity.

Reopen, update and retest without losing work

After preserving the script and finished takes, leave an active recording safely before reopening the app. Check for an official update and, if needed, restart the device. Repeat the same short script with the same settings.

Changing the script, speed, orientation and operating-system settings at once makes any improvement hard to explain. Keep a one-change log. If the fresh test still jumps immediately, stop spending your filming session on the same attempt.

Worked example: save the recording session

Imagine a creator needs to film a forty-five-second tutorial, but the four-line test jumps to its final sentence. This is an original illustrative scenario, not a tested phone result.

They preserve the full script, record the symptom and check whether an optional diagnostic is comfortable. If scrolling stays unreliable, they split the tutorial into four thoughts. They read a thought, look at the lens, say it naturally and pause before the next take. A simple cut can join the sections.

The fallback may take several takes, but it avoids racing through an unreadable script or giving up the entire session. A note beside the lens can also hold short cues without requiring a new app.

Send a report someone can reproduce

Include phone, operating system, Edits version, creation mode, the harmless test script, selected text size and speed, and the exact observed behaviour. Mention relevant accessibility settings without presenting them as a confirmed cause.

Attach a short screen recording only if it is safe and useful; hide notifications and account details. State whether video recording itself works. Keep original takes while waiting for support.

Use the worksheet below to decide between one more controlled check and a workable filming alternative.

EDITS TELEPROMPTER TEST
Source-checked, not a guaranteed device fix. Keep accessibility settings you need.

PRESERVE
Full script saved outside Edits:
Existing takes independently opened:
Original project media backed up:
Phone / operating system / Edits version:
Creation mode:
Do not clear storage or uninstall to perform this test.

OBSERVED FAILURE
[ ] Option missing
[ ] Text stays still
[ ] Jumps to end
[ ] Scrolling too fast
[ ] Scrolling works, recording fails
Exact action:
What happens next:
Selected speed:
Selected text size:

HARMLESS FOUR-LINE SCRIPT
This is line one.
This is line two.
I will pause before line three.
This is the final line.

CONTROLLED COMPARISON
Baseline result:
Typed directly or pasted:
One changed variable:
Result:
Original setting restored:
Do not change script, speed and phone settings at once.

ACCESSIBILITY NOTE
Reduced/remove animation setting:
Needed for comfortable or safe device use? Keep it.
Optional comparison comfortable and appropriate? If no, skip.
If tested: original value / brief result / restored value.
Anecdotal workaround is not proof of a universal app defect.
No developer settings or unrelated permissions changed.

FILMING FALLBACK
Tutorial's one useful takeaway:
Thought 1:
Thought 2:
Thought 3:
Thought 4:
Read thought, look at lens, speak, pause, check take.
Short cue beside lens:
Usable take filenames:
No need to race through the entire script.

ILLUSTRATIVE SCENARIO
Four-line test jumps immediately.
Preserve script and evidence; use thought-by-thought takes if the test remains unreliable.
Outcome is not a measured device test.

SUPPORT REPORT
Exact reproduction with harmless script:
Mode, speed and text size:
Does camera/audio recording itself work?
Relevant accessibility setting:
Update/reopen result:
Safe screen recording with notifications hidden:
Keep originals while waiting for support.