Read Text Aloud on iPhone and Mac: When to Switch

Short answer: To read text aloud on an iPhone, use the built-in Spoken Content feature, which newer iOS versions call Read & Speak. Turn it on in Settings, then either highlight text and tap Speak, or swipe down with two fingers to hear the whole screen. It is free, it works without a network connection, and it is the fastest answer for short passages. The moment you need an audio file at the end, one voice repeated across many clips, or a long narration you can revise in sections, the job has outgrown the phone and belongs on a Mac.

What iPhone Spoken Content actually does

Even with VoiceOver turned off, an iPhone can read onscreen text out loud. Apple documents three related tools in the iPhone User Guide: Speak Selection reads the text you highlight, Speak Screen reads everything currently on the screen, and Accessibility Reader opens text in a full-screen reading view with its own audio controls. A Siri request such as “Speak screen” also starts reading on supported devices.

Spoken Content is about more than a single default voice. Apple's accessibility pages state that Speak Screen and Speak Selection cover more than 80 distinct voices across more than 60 languages and locales, with automatic language detection so a page that mixes languages can switch voices without help. You can change the speaking rate, set a default language, and add custom pronunciations for names or technical terms. This is a listening feature, so treat it as reading with your ears rather than audio production.

Turn on read-aloud on your iPhone

The path differs slightly by iOS version. On iOS 26 and later the panel is called Read & Speak; on iOS 18 and earlier it is called Spoken Content. Both live under Accessibility.

1. Open the Settings app and tap Accessibility.
2. Tap Read & Speak. On iOS 18 and earlier, tap Spoken Content.
3. Turn on Speak Selection to read highlighted text. Turn on Speak Screen to read a whole screen.
4. To hear a selection, highlight the text and tap Speak.
5. To hear the whole screen, swipe down with two fingers from the top of the screen.
6. Use the on-screen Speech Controller to pause, change the rate, or skip backward and forward. Turn on Show Controller to keep those controls visible.

A few settings are worth a minute. Set the Speaking Rate slider to a comfortable pace, choose a voice and dialect under Voices, and turn on Detect Languages if you read pages that mix languages. Typing Feedback can speak characters or words as you type, which helps when you proofread a keyboard-heavy draft. None of these settings writes an audio file to your phone: they change how text sounds while you are listening to it.

Listening or producing: pick the right device

The useful question is not which device reads text, but what you need when the sentence stops. If you want to hear a paragraph, a phone is enough. If you want to hand an editor a file, place narration under a video, or keep one voice consistent across a ten-part course, you are producing audio, and that is a different job with different tools.

Read the table as a size guide, not a verdict on quality. The built-in iPhone feature is genuinely good at what it does. It is simply not built to output files, manage chapters, or hold a project together for weeks. A short clip on a phone and a two-hour narration on a Mac are not competing tasks, so there is no need to feel that one replaces the other.

When a long job belongs on a Mac

A long job is anything you cannot finish in one listening session and may need to change later. Audiobook chapters, course modules, a stack of blog posts turned into audio, or the narration track for a long video all qualify. These jobs share three needs the phone does not meet: a deliverable file, a voice that stays the same from the first clip to the last, and the ability to fix one paragraph without re-reading the other nine.

There is also an attention problem. Reading a screen aloud holds your phone for the length of the text. Producing narration should run as a background job while you keep working, and it should let you line up many sections and export them together. That is a desktop workflow. If your material started as written posts, the blog to audio guide shows the conversion step, and the audiobook narration guide covers longer chapter-based work.

Five signs the job is a Mac job

• You need an audio file at the end, not just something you heard once.
• The text is longer than one screen or one sitting.
• The same voice has to run across many clips or chapters.
• You expect to revise one section and re-export it.
• You want a designed or cloned voice rather than a system voice.

Three times the iPhone is enough

• You are proofreading a paragraph by ear.
• You want a web page or email read to you while you do something else.
• You are checking how a sentence sounds before you commit it to a script.

If two or more of the first list are true, move the job to the Mac. If all three of the second list are true, stay on the phone and save the desktop work for later. This keeps you from buying or opening a production tool for a task that the built-in feature already handles.

The Mac side: built-in listening and production tools

macOS carries the same listening idea under a different name. Speak selection uses Option-Esc by default, and the settings live in the Accessibility panel. The Mac text-to-speech shortcut guide walks through enabling it, choosing a voice, and fixing silent playback. For a quick read aloud, that remains the cheapest option, and it costs nothing.

Production is where a Mac pulls ahead. A dedicated app can hold a project with multiple speakers, save reusable voices, queue many sections to render, and export finished audio. Murmur is one option built for this: it runs local models on Apple Silicon Macs running macOS 15 or later, keeps generation on the machine after setup, and exports WAV and M4A. The Mac narration workflow guide lays out a repeatable project pattern, and the Mac text-to-speech app comparison explains how reading tools and production tools differ. For work that must stay on the machine, the offline text to speech guide covers the privacy side. If you only listen and never export, you do not need any of this: the built-in feature is the right answer and no purchase is required.

A worked example: a 20 minute chapter

Suppose you have a 20 minute audiobook chapter, roughly 3,000 words. On the phone you can listen to it, but you cannot ship it. On the Mac you would keep the script in one file, split it at natural section breaks, generate each section with the same voice, listen to the exports on your phone as a proof pass, and then re-generate only the part you change.

1. Keep the full chapter in one editable script file, not inside the read-aloud tool.
2. Split the script at natural section breaks so a fix stays local.
3. Lock one voice and one pace for the whole chapter.
4. Generate the sections and export them.
5. Send the exports to your phone and listen with headphones for a proof pass.
6. Fix the script, regenerate only the changed section, and re-export.

The phone still earns its place in this workflow. It is the fastest place to hear the result as a listener would, on the same headphones or speaker that the final audience will use. The Mac does the producing; the iPhone does the checking. Keep the script and the voice choice documented so the next chapter starts from the same settings instead of a fresh guess.

Frequently asked questions