macOS Spoken Content vs a Dedicated Read-Aloud App

Spoken Content is an accessibility feature built into macOS. It has been there for over a decade. Go to System Settings, Accessibility, Spoken Content, and you will find three main options:

• Speak selection. Select text anywhere, in any app, and press Option+Esc. The Mac reads the selection aloud with the system voice. This is the feature most people mean when they say "Mac text-to-speech."
• Speak item under the pointer. Hold a modifier key (usually Control) and hover over text. The Mac reads the text under the cursor. Useful for quickly checking a word or sentence without selecting it.
• Speak typing feedback. The Mac reads each character or word as you type. This is an accessibility feature for people who need audio confirmation of their typing.

The voice and speed are set in the same preferences panel. You can download additional voices from Apple (Samantha, Daniel, Alex, and several others), and some are neural-quality. The speed slider applies to everything Spoken Content reads, with no per-document override.

A lot, and it is worth listing because many articles about TTS apps pretend the built-in option is useless. It is not:

• Zero setup. Enable it once in System Settings and it works forever, in every app, on every Mac running macOS. No download, no account, no import step.
• System-wide. It reads selected text in Safari, Mail, Pages, Preview, Terminal, Slack, and every other app. There is no format restriction and no file to import.
• Completely free. No trial, no subscription, no premium tier. The voices Apple ships are included with macOS.
• Good for short, quick reads. Checking a paragraph you just wrote, confirming a quote, hearing a single sentence from a web page. Spoken Content is instant and does not pull you out of what you are doing.

For these use cases, Spoken Content is the right tool and a dedicated app would be overkill. The article is not going to pretend otherwise.

The feature was designed for accessibility, not for reading books. The gaps become obvious the first time you try to use it for a novel or a long document:

• No bookmarking. Spoken Content reads the selected text and stops. There is no concept of "where you left off." If you close a document or restart your Mac, you must find your place manually. For a book, this is a dealbreaker within the first chapter.
• One voice, one speed for everything. If you want a different voice for fiction and non-fiction, you change it in System Settings each time. If you want to slow down for a dense section, you open System Settings and adjust the global slider. There is no per-book or per-document voice or speed setting.
• No sleep timer. Spoken Content reads until you stop it or the text runs out. If you fall asleep listening to a book, it plays all night.
• No word highlighting. Spoken Content reads the words but does not highlight them visually. For people who want to follow along or who benefit from dual-channel input, this is a missing piece.
• Stops on window change. If you switch windows or the text scrolls out of view, Spoken Content often stops. It reads what is selected on screen right now, and it does not follow the content when the view changes.

These are not bugs. They are design decisions made for a tool whose job is to read selected text aloud on demand. A book player is a different thing, and a dedicated app is designed for that job.

A dedicated read-aloud app like LoudReader is built for the use case Spoken Content was not designed for: reading books, long articles, and documents from start to finish. Here is what it adds:

• Place bookmarking. Close the app, restart your Mac, open the book, and it opens to the exact sentence where you stopped. This works across days and sessions. It is the single feature that makes the difference between a tool and a player.
• Eight neural voices. Pick a different voice for each book. Switch on the fly without opening System Settings. The voices run on the Mac's Neural Engine and are optimized for long reading sessions.
• Per-book speed control. Set 1.5x for light non-fiction and 1.0x for dense technical text. Speed ranges from 0.3x to 3.0x, and each book remembers its own setting.
• Sleep timer. Set the app to stop after 15, 30, or 60 minutes. Useful for bedtime listening without waking up to a book that is still playing chapters later.
• Word highlighting. Each word lights up as it is spoken. This helps with focus, comprehension, and language learning. Combined with speed control, it makes dense text easier to follow.
• Ambient soundscapes. Optional background sounds (rain, white noise, etc.) layered under the narration. Some people find this helps with focus or masks background noise.

All of this runs on-device. LoudReader is fully on-device and private, your library never leaves your device. Spoken Content is also on-device. Neither tool sends your text to a server. For more on the Mac reading workflow, see reading EPUB aloud on Mac.

The honest decision tree, without pretending one tool beats the other in every situation:

• Use Spoken Content when: you need a paragraph read right now, the text is in an app you cannot or do not want to export from, the passage is short (under a few minutes of audio), or you are proofreading a single sentence you just wrote.
• Use LoudReader when: the content is a book, a long article, or a document you plan to return to over multiple sessions, you care about voice quality, you want bookmarking, you need speed control per book, or you are stepping away from the screen entirely and want playback to continue in the background.

The two tools complement each other. Most people who read a lot on Mac end up using both: Spoken Content for quick checks, LoudReader for sustained reading. That is not a failure of either tool. It is using the right tool for the right job.

If you care about the offline angle specifically, see offline text-to-speech on Mac, which compares more than just the built-in option.