Why this has no length limit when many similar tools do#
Many free text-to-speech tools cap input at a few thousand characters, often because they route text through a paid cloud API with a per-request quota. This tool uses the Web Speech API's SpeechSynthesis interface, built into every modern browser — there is no API call and no per-request cost, so there is no commercial reason to cap length. The one real constraint is that some browsers become unreliable with a single very long utterance, which this tool works around by splitting text into sentence-sized chunks internally and queuing them — invisible during playback, but the reason long text actually finishes reading instead of cutting off partway through.
Why the voice list looks different on every device#
The available voices come from the operating system and browser, not from this tool — Windows, macOS, iOS, Android and each browser vendor ship a different set of installed voices, so the same page shows a different dropdown on a Windows Chrome install than on an iPhone Safari session. There is no way to standardize this from a client-side tool with no backend; the voice quality and language selection genuinely depend on what is already installed on the device being used.
What this is useful for#
Proofreading by ear — hearing your own writing read aloud catches awkward phrasing and typos that silent re-reading tends to skip past. Testing how a page or a piece of copy sounds for accessibility. Or simply listening to an article or a script instead of reading it, useful while doing something else. It is not a substitute for a professional voiceover — the voice quality depends entirely on what your device ships, from quite natural-sounding to distinctly robotic.