Text to speech on Mac, from built-in voices to local apps
Your Mac can already read text out loud. This guide covers when the built-in option is enough, when cloud services help, and when a local voice app is the better tool for finished audio.
01 · Context
Your Mac already speaks text
macOS includes text-to-speech at the system level. Spoken Content can read selected text, documents, and web pages aloud, and the say command in Terminal can turn any string into speech. These options are free, already installed, and fine for listening and accessibility.
The limitation is not the voice. It is the workflow. Built-in speech is designed for playback, not production. There is no project view, no batch queue, no export pipeline, and no reusable custom voice for the work you are producing.
02 · Highlights
The three ways to do text to speech on a Mac
Every option on the Mac falls into one of three buckets. The right answer depends on what happens after the audio is generated.
Built-in macOS voices
Free and instant for reading text out loud. Best for accessibility, listening to drafts, and quick playback. Not designed to export project audio.
Cloud voice services
Hosted platforms give you browser access, team features, and APIs. You pay by usage or subscription, and your text is processed on their servers.
Local Mac voice apps
Apps like Murmur run the voice models on your own machine, then export finished WAV or MP3 audio. One-time cost, no per-word meter, and the text stays local.
03 · Highlights
When the built-in option is enough
You just need to hear the text
If listening is the whole job, Spoken Content and the say command cover it without installing anything.
You need accessibility, not assets
For screen reading and study workflows, system voices are the right tool and stay in sync with macOS shortcuts.
You are testing copy for rhythm
Reading a draft out loud is a fast editing trick. Playing it back through system speech is enough to catch awkward sentences.
04 · Context
When you need a real TTS app instead
The moment you need a file, the built-in workflow stops. You want a voiceover track for a video, a narration file for a course, or a batch of clips for a project, and system speech gives you playback instead of assets.
That is the boundary where a dedicated app takes over: choose a voice, generate the full script, manage retakes, and export clean audio you can drop into an editor or upload directly.
05 · Workflow
Text to speech for Mac: what a production workflow looks like
That is the difference between a system feature and a studio tool. The system feature reads. The tool produces.
06 · Highlights
Local generation vs cloud TTS on a Mac
If you are comparing a local app with a cloud subscription, these are the tradeoffs that matter in practice.
Cost model
Cloud tools meter characters or minutes. A local app is a one-time purchase, so long scripts and retakes do not cost more.
Privacy
Local generation keeps drafts and voice samples on your Mac. Cloud tools process text on their servers.
Workflow location
Cloud platforms are browser-first and good for teams and APIs. Local apps live in the desktop workflow you are already in.
Iteration speed
With no usage meter, you can regenerate a sentence, a paragraph, or a chapter as many times as the script needs.
07 · Context
How to choose the right text to speech setup for your Mac
Start with the output. If the goal is listening, use what macOS already provides. If the goal is a published or edited file, choose an app that exports audio.
Then decide where the text is allowed to go. Teams that need browser access and APIs will prefer cloud services. Creators, educators, and privacy-sensitive teams who work on a Mac tend to prefer local generation with a fixed price.
Murmur is built for that second group: local generation on Apple Silicon, a project workflow, voice cloning from a short sample, Voice Design, and export-ready audio for one-time $49.
FAQ
Common questions
Yes. macOS includes Spoken Content for reading selected text aloud, and the say command in Terminal can speak any string. Both are free but designed for playback rather than producing audio files.
Move from reading text to producing audio
If your Mac already reads text but does not produce finished files, Murmur adds the studio layer: local voices, projects, and exports for one-time $49.