Text to speech on Windows: the built-in voices, edge-tts, and why subtitle dubbing never fits
Narration for a video, a spoken prompt in an app, a subtitle file turned into audio: all of it starts with getting text read out and saved to a file. Windows can do it with what's already installed, and the neural voices are a pip install away. Here's what each route costs you. The voices already in Windows Narrator and Edge's Read Aloud use the built-in speech engine, but neither will save what…
Windows can generate speech from text files using built-in voices and neural voices through pip installations. The System.Speech library allows for saving output to a WAV file and selecting voices, but installed voices may not always appear in GetInstalledVoices(). Edge-tts provides neural voices for generating MP3 files, with options for adjusting rate, volume, pitch, and length.
Subtitle dubbing often fails because the timing of the synthesized speech differs from the original subtitle cues. To improve the fit, adjust the voice rate by 10-20% or shorten the subtitle lines. For new projects, it may be better to generate narration separately from the visuals, ensuring a smoother workflow. Licensing for neural voices varies, with ElevenLabs offering a free tier but requiring paid plans for commercial use, while Edge-tts has no quota but operates under Microsoft's terms.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
