Reading by ear: what this is good for
The single best use of text to speech is one most people discover by accident: proofreading. Your eyes glide over your own writing and auto-correct it; your ears cannot. Hearing a letter, essay or product description read aloud exposes repeated words, missing words, sentences that run out of breath, and punctuation that produces the wrong pause — which is why professional editors and novelists use read-aloud passes. Beyond editing, listening serves readers with low vision or dyslexia, language learners who want pronunciation modelled, drivers and cooks who need an article read hands-free, and anyone whose eyes are tired at the end of a screen-heavy day.
The voices are your device's voices
Unlike services that synthesize speech on a server farm, this tool uses the speech engine already inside your phone, tablet or computer — the same one behind its accessibility features. That design has three consequences worth understanding. First, the voice list varies: a Windows laptop offers Microsoft voices, an iPhone offers Apple's, a Chromebook offers Google's, and downloading extra voices in your device settings adds them here too. Second, quality varies for the same reason — newer devices sound markedly more natural. Third, your text stays off other people's servers as far as this page is concerned; it is handed to your own system. (One honest nuance, covered in the questions below: a few browser voices are themselves online services.)
Speed and pitch, set sensibly
Speed runs from half pace to double pace. Most listeners settle at 1× for new material and 1.25–1.5× for familiar text like their own drafts; audiobook veterans live at 1.5× and above. Slow the rate to 0.75–0.85× for language practice, poetry, or anything read to children. Pitch shifts the voice's character up or down without changing its identity — a small nudge down can make a shrill voice easier on the ear, and pitch plus a slower rate is the classic combination for a bedtime-story voice. Changes take effect the next time you press Play.
Long text: one honest limitation
Some browsers — Chrome on desktop is the known case — pause or stop partway through very long passages, a quirk in how they manage the speech queue. If a long document stalls, press Pause/Resume to nudge it, or split the text into a few chunks and play them in turn. And as the questions note, browsers give pages no way to save the spoken audio as a file, so for MP3s you will need a dedicated app — this page's strength is instant, private, live listening.
Frequently asked questions
Where do the voices come from?
From your own device and browser. This tool uses the speech system built into Windows, macOS, Android, iOS and Chrome, so the voice list is whatever your device already has — which is why it differs between a phone and a laptop, and why new voices appear after system updates, not website updates.
Can I download the speech as an MP3?
Not from a web page, unfortunately. Browsers can speak text aloud but offer no way for a page to record or save that speech as an audio file. If you need an MP3, desktop programs and phone apps with a save or share button are the route; this tool is for listening live.
Is my text sent to a server to be read?
This page sends your text nowhere — it hands it to your own device's speech system. One honest nuance: some browsers (notably Chrome with certain online voices) pass text to their own speech service as part of how those particular voices work. Choosing a voice marked as local, or using Edge or Safari voices, keeps everything on the device.
Why does long text sometimes stop partway through?
A known quirk in some browsers, especially Chrome on desktop, pauses or cuts very long passages. Splitting your text into paragraphs and playing them one at a time is the reliable workaround; the pause button also becomes a resume that unsticks most stalls.
Private by design: your text is handed to your own device's speech system by this page — never uploaded to our server, because we do not have one receiving it.