A teleprompter should not need onboarding.

Why this exists

Many teleprompters begin with mandatory account creation, pricing tiers, paywalls, or feature-heavy dashboards. Those things get in the way of the moment when you simply need readable words moving at the right pace.

This project treats speed, typography, privacy, accessibility, and predictable controls as the product itself, not as premium extras.

Open source on purpose

The code is completely open source so anyone can inspect how local storage, microphone input, and analytics work, report an issue, improve accessibility, or self-host the tool. The core application does not need a database or a script-storage service.

Local voice tracking is documented in detail, including the pinned model, temporary recognition state, and fallback behavior. Read how local voice tracking works.

View SABYA648/Telemprompter-WTF on GitHub.

What it will not do

teleprompter.wtf will not put scripts in public links, require an account for the basic presenter, sell attention to advertisers, watermark your video recordings, or claim your words need a cloud database to scroll on your screen.

Tested across real browsers

We test and document exact browser capabilities and fallback states. For details on desktop and mobile browser support, inspect our Browser & Device Compatibility Matrix.

Use it, then tell us what hurt

The most useful contributions are concrete: a browser where fullscreen behaves oddly, a control that is hard to reach on a particular phone, or a wording choice that does not work with assistive technology. Open a GitHub issue with reproducible details. Never include a private script.