Password Generator
Cryptographically random passwords with a live entropy meter.
Utilities & Converters
Read text aloud with the voices already installed on your device.
Whatever your operating system provides, which varies considerably.
Windows 11 ships with several neural voices per language and lets you add more through Settings → Time & Language → Speech. The neural voices are close to indistinguishable from cloud services.
macOS and iOS include a large voice library, with the high-quality variants available as an optional download in Accessibility → Spoken Content. The default installed voice is the lower-quality one, and downloading the enhanced version is a substantial improvement most people never discover.
Android uses the Google Speech Services engine, generally with good quality across many languages.
Chrome on desktop adds its own network-backed voices on top of the system ones, marked as non-local in the voice list.
This means the same text sounds different on different devices, and a voice you select here may not exist for someone else. It is the trade for having no per-character cost.
Not directly from the Web Speech API, which is a genuine limitation of the platform rather than of this tool. The API renders audio to the system output device and provides no access to the audio stream.
There is a workaround: capture the system audio with a screen recorder that includes audio, then extract the track. The Screen Recorder tool on this site can capture tab audio while the speech plays, which produces a usable file with a couple of extra steps.
If you need a downloadable audio file as a primary workflow, a cloud TTS service is the right tool — the trade is per-character billing and sending your text to a server. For proofreading, accessibility and previewing, playback without a file is usually all that is needed.
| Device voices (this tool) | Cloud TTS | |
|---|---|---|
| Cost | Free, unlimited | Per character, typically $4–16 per million |
| Character limit | None | Per request and per month |
| Privacy | Text never leaves the device | Text sent to the provider |
| Voice quality | Good to excellent, OS-dependent | Consistently excellent |
| Voice consistency | Varies by user device | Identical for everyone |
| Download audio | Not supported | Yes |
| Works offline | Yes, with local voices | No |
The decision is straightforward: for reading text to yourself, device voices are better in every dimension that matters. For producing audio that will be published or distributed, cloud TTS is the right tool because you need a file and consistent output.
No. Long documents are queued in chunks internally to work around a Chrome limitation, but there is no cap you will reach.
You are likely using a lower-quality default voice. On macOS and iOS, download the enhanced variant in Accessibility settings. On Windows, add neural voices in Speech settings.
Not directly — the Web Speech API does not expose the audio stream. Use the Screen Recorder with tab audio enabled as a workaround.
Yes, with locally installed voices. Voices marked as network-based in the list require a connection.
Voices are installed per language by your operating system. Add the language pack in your system settings and the voices appear here after a browser restart.
Yes, in Safari. iOS requires the first playback to be triggered by a user gesture, which the play button satisfies.
Not for local voices — synthesis happens on your device. Voices marked as non-local in the list are processed by the browser vendor, and the tool labels them so you can choose.