How to Do Text to Speech on Google Docs: 3 Methods

There are three ways to do text to speech on Google Docs, and most articles you'll find only mention one of them. That's why people end up writing search queries like "how to do text to speech on google docs" twice — once to find the basic answer, once to find out why the basic answer wasn't enough.

This guide covers all three: the native accessibility feature, the ChromeVox extension trick, and the easier alternative that most users move to within a week. Each has a job it's good at; the trick is matching the method to the job before you start.

Method 1: the native accessibility feature

Google Docs ships with a read-aloud command, but it's hidden behind the screen reader support toggle. Turn it on once and you're set: Tools → Accessibility settings → check "Turn on screen reader support" → OK. A new Accessibility menu appears in the top bar.

From there, highlight text and use Accessibility → Speak → Speak selection, or use the keyboard shortcut Cmd + Option + X (Mac) / Ctrl + Alt + X (Windows). This is the official Google Docs method, and it works in any browser.

What it's good at

• Proofreading your own writing — the flat voice doesn't add expression, so you catch every awkward phrase you wrote.
• Reading short chunks of a document — a paragraph at a time, a section at a time.
• Accessibility integration — if you already use a screen reader, the controls feel familiar.

Where it falls down

• The default voice is a 2018-era ChromeVox voice that gets tiring after about ten minutes.
• There's no "play the whole document" mode — you have to highlight chunks manually.
• No MP3 export, no playback queue, no mobile support.

For a quick proofread of something you wrote, this method is enough. For listening to a 30-page report while you're doing the dishes, it's the wrong tool.

Method 2: upgrade the voice via ChromeVox settings

The native method uses ChromeVox under the hood. ChromeVox's default voice is the one most people give up on, but you can swap it for a much better voice with one settings change.

Open chrome://settings/accessibility in a new tab. Find "Text-to-speech voice settings." Switch from the default voice to one of the Google neural voices or — on Windows — to one of the Microsoft natural voices. Save. Now go back to Docs and use the same Cmd + Option + X shortcut. The reading voice is dramatically better.

This is the underrated middle path. You keep the convenience of the native Docs feature, but the voice quality jumps to something close to what you'd get from a dedicated reader. Most people who stick with method 1 long-term are using this voice upgrade behind the scenes.

The catch

The neural voices in chrome://settings depend on what your OS and browser have downloaded. On a fresh ChromeOS install, the options are limited to the older voices. On Windows or Mac with Edge or Chrome installed, you'll usually find at least a couple of high-quality neural voices already available. If you don't see any, install Edge — it bundles the Microsoft natural voices and they show up as options across other Chromium-based browsers.

Method 3: the easier alternative outside Docs

The third option — the one most users end up using when they want to listen to a whole document — is to move the content out of Docs into a dedicated TTS reader. This sounds like extra work; in practice it's faster than highlighting chunks in Docs all afternoon.

The workflow takes 30 seconds: select all (Cmd + A), copy (Cmd + C), open Read Aloud Reader in a new tab, paste, hit play. You get a polished neural voice (OpenAI Nova or similar), continuous playback without highlighting, adjustable speed, and the option to download an MP3 if you want offline audio.

For long documents and long listening sessions, this is the path that holds up. The flat ChromeVox voice doesn't scale past about ten minutes; a polished neural voice — the kind Read Aloud Reader uses by default — scales to hours. Our listen to Google Docs out loud guide has the longer version of this same workflow with screenshots.

Why not just stay in Docs?

Three reasons. First, no continuous playback. Second, no MP3. Third, no mobile — the mobile Docs apps don't have the accessibility read-aloud at all, so the moment you leave your laptop you've lost the feature entirely. A browser-based reader works on phone, tablet, and laptop with the same interface.

How to do text to speech on Google Docs: picking the right method

Quick decision tree:

• Proofreading your own writing → method 1 (native, flat voice is a feature here).
• Listening to a doc for ten minutes → method 2 (native + upgraded ChromeVox voice).
• Listening to a long doc, on the move, or wanting MP3 → method 3 (move it to a dedicated reader).
• Reading on phone or tablet → method 3 (the others don't work on mobile).

Almost everyone uses two of these in rotation. Method 1 for editing their own drafts, method 3 for listening to long documents from other people. Method 2 is the bridge between the two for users who haven't moved their listening out of Docs yet.

The PDF angle

If the content you're trying to listen to is a PDF inside Google Drive rather than a native Doc, you have one extra option. Right-click the PDF in Drive, choose "Open with → Google Docs." Docs will OCR the PDF into a regular document, and from there you can use any of the three methods above. The conversion isn't perfect — line breaks and table structure usually get mangled — but for prose-heavy PDFs the OCR is good enough to listen to.

For PDF read-aloud without the OCR step, the dedicated tools handle native PDF parsing better. Our read PDFs aloud guide covers the options.

How to use text to speech on Google Docs on mobile

Mobile is where the native Docs read-aloud is weakest, because the mobile Docs apps don't include it. On Android, the closest equivalent is Google's Select to Speak feature (Settings → Accessibility → Select to Speak). Turn it on and you get a floating button that reads any selected text in any app, including Google Docs.

On iOS, the equivalent is Speak Selection in Settings → Accessibility → Spoken Content. Same idea — highlight text, hit the popup Speak button, listen. Both are operating-system features rather than Docs features, but they fill the gap until Google ships a real mobile Docs reader.

The fastest possible answer in 60 seconds

If you searched how to do text to speech on Google Docs and just want the one-line answer, this paragraph is it. Everything above is the longer version for people who hit a wall with the basic method and need to know why.

If you just want to make a Google Doc talk in the next sixty seconds: turn on screen reader support in Tools → Accessibility, then use Cmd + Option + X on the text you've highlighted. That's the answer to text to speech in google docs at its simplest. If the voice sounds bad, swap to a neural voice in chrome://settings/accessibility. If you want to listen to the whole document hands-free, paste it into a browser-based reader and let it run.

Three methods, three jobs. Pick the one that matches what you're actually trying to do, and the Docs read-aloud question stops being annoying.

One small habit that pays off

If you take only one habit away from this guide, make it the keyboard shortcut. Cmd + Option + X (or Ctrl + Alt + X on Windows) turns a five-click chore into a reflex. Most people who use the native feature for more than a week never click into the menu again — the shortcut becomes muscle memory and the rest of the workflow follows.

The second habit worth building: stop trying to make Docs do every job. The native reader is great for editing your own writing. A dedicated reader is great for long-form listening. Recognising which is which is the trick most readers eventually internalise, and after that the read-aloud question stops being something you have to think about.