How to Listen to Google Docs Out Loud
6 min read
Google Docs does not have a read aloud button. People search for it constantly and come away confused, because the feature seems obvious and it simply is not there. What Docs has instead is screen reader support, which is a different thing and much clunkier than what most people want.
So if you want to hear a doc read back to you, whether to proofread it or to get through a long one without staring at the screen, here are the four routes that actually work.
Why this is harder than it should be
Google built accessibility into Docs by making it cooperate with screen readers rather than by adding its own voice. That is a reasonable engineering choice and a frustrating user experience. A screen reader announces menus, formatting, and cursor position alongside your words, because its job is to describe the whole interface to someone who cannot see it. If you just want to hear your paragraphs, that is a lot of noise.
Knowing this saves you time, because it explains why the built in path feels wrong. You are using an accessibility tool for something it was not designed for.
Option 1: the built in screen reader support
Open Tools, then Accessibility, then turn on screen reader support. Docs will then work with a real screen reader: VoiceOver on Mac, NVDA or Narrator on Windows, ChromeVox on a Chromebook.
Use it when: you genuinely need a screen reader, or you are checking that a document is accessible to someone who does.
Skip it when: you just want your writing spoken back. The interface chatter will drive you up the wall inside a minute.
Option 2: select the text and use your OS voice
Much simpler. Highlight the part of the doc you want to hear, then hand it to your operating system.
Mac: right click the selection, then Services or Speech, then Start Speaking. You can bind this to a key in System Settings under Accessibility, Spoken Content. This is the fastest proofreading trick on a Mac and almost nobody knows it. ChromeOS: enable Select to speak in Accessibility settings, then drag over the text. It is the cleanest version of this on any platform. * Windows: there is no neat equivalent for arbitrary selections, so paste into an app that reads text or use one of the options below.
Use it when: proofreading. Hearing your own sentence read flatly and literally is the single best way to catch a clumsy phrase or a missing word. The robotic voice is a feature here, not a bug, because it will not smooth over your mistakes the way your own eyes do.
Option 3: export and use a document reader
Download the doc as a PDF or Word file, then open it in a text to speech app built for documents. This preserves structure and page order, which matters for anything long or heavily formatted.
Use it when: the document is long, structured, and you want to work through it properly. The tradeoff is that you now have a second copy that will drift out of date the moment you edit the original.
We went through this path in detail in how to listen to a PDF out loud.
Option 4: send the text to a listening app
Highlight the doc text in your browser, send it to an app that converts it to audio, and play it like a podcast episode. No export, no second file, no interface chatter.
Use it when: you want to actually listen rather than proofread. This is the right choice for reading someone else's long doc, a shared spec, meeting notes, a draft you have been sent, or research you collected in Docs.
Which one to use
| | Screen reader support | OS voice on a selection | Export to a reader | Send to a listening app | | --- | --- | --- | --- | --- | | Setup effort | High | Low | Medium | Low | | Reads interface chatter | Yes | No | No | No | | Voice quality | Basic | Basic | Good | Best | | Good for proofreading | No | Yes | No | Sometimes | | Good for long reads | No | No | Yes | Yes | | Stays in sync with edits | Yes | Yes | No | No |
Two things that will trip you up
Comments and suggestions. Anything in suggesting mode, plus comment threads, can end up in what gets read, especially through screen reader support. If a doc is heavily marked up, accept or resolve first, or copy the text somewhere clean.
Very long docs. Selecting forty pages at once tends to fail or truncate silently. Work in sections. Chapter or heading sized chunks are also easier to navigate later, which you will appreciate when you want to re listen to one part.
Where Liso fits
Liso covers the fourth option. Open the doc in your browser, highlight the text, right click, and choose Listen with Liso. It comes back as natural sounding audio in your library, without exporting anything or installing a screen reader.
Because each listen is saved, a long doc becomes something you can work through across several sittings instead of one sitting you never finish. Pick a voice, set your speed, file listens into folders so work docs and research stay apart, and download for offline. Your place follows you between devices.
For quick proofreading, honestly, use your Mac's Start Speaking shortcut. It is free and instant. For everything you would rather listen to than read, that is what Liso is for. If you want the same thing for ordinary web pages, see read aloud Chrome extension.
Free to start, five listens a month, no card needed. Try it free.