The Google Doc was forty-seven pages long. A quarterly business review that someone on the strategy team had been writing for three weeks. Charts, bullet points, executive summaries of executive summaries, and a section called "Key Takeaways" that was itself four pages.
I had to read it before a meeting in two hours. On screen. After already spending six hours reading on screen.
My eyes said no.
Google Docs Doesn't Have a Read-Aloud Button
This genuinely surprises people. Google — the company that built Google Translate, which will read any text aloud in 40 languages — never put a "Listen" button in Google Docs.
You can use Chrome's built-in accessibility features. Go to Settings, find Accessibility, enable "Select-to-speak," highlight text, click the play button that appears. The voice is your operating system's default. On a Mac, it's the same voice that reads your notification alerts. On Windows, it's the same voice that tells you "You have no new items" in Cortana. Flat. Mechanical. Zero intonation.
It also doesn't track where you are in the document. No highlighting. No progress bar. You highlight a section, it reads that section, and then it stops. If you want the next three paragraphs, you highlight those too. It's like reading a book by pointing at each sentence individually and asking someone to recite it.
That's not reading. That's a chore on top of a chore.
What I Actually Wanted
Take the entire Google Doc — all forty-seven pages of it — and read it to me with a voice that sounds like an actual human. Show me which paragraph it's reading. Let me pause. Let me speed it up to 1.5x because honestly the first ten pages are context I already know. Let me click any paragraph to jump there directly.
Basically: turn Google Docs into a podcast.
CastReader does exactly this. Free. No login.
Why Google Docs Is Hard for TTS Extensions
Here's something most people don't know: Google Docs doesn't render text the way a normal webpage does.
A normal website puts text in HTML elements — paragraphs, headings, spans. A screen reader or TTS tool can walk through those elements and extract the text. Simple.
Google Docs uses a canvas-based rendering system. The text you see on screen is painted onto a canvas element. The actual DOM underneath contains transparent placeholder spans positioned where letters appear — but these spans aren't structured as readable paragraphs. They're layout artifacts. A generic "read this page" extension would either grab nothing useful, or grab everything including the toolbar text, menu labels, comment threads, and the names of everyone who has the doc open.
CastReader has a dedicated Google Docs extractor that understands this canvas architecture. It uses Google's own annotation API to access the rendered text rectangles, reconstructs the paragraph structure, strips out the editor chrome, and preserves the document's actual reading flow — headings, body paragraphs, list items, in order.
The highlighting works too. When CastReader reads a word, it highlights that word in the document — positioned precisely over the canvas rendering. Not a generic block highlight. The actual word, on the actual line, following the text as it goes.
Step by Step
Install it. Chrome Web Store. Click "Add to Chrome." No account. No signup. No trial period.
Open any Google Doc. A report, a spec, meeting notes, a thesis draft, a 200-page employee handbook that HR keeps telling you to read.
Click the CastReader icon in the toolbar. Or just look for the small "Listen" label that appears near your document title — click that. Playback starts immediately.
A floating player appears at the bottom of the screen. Pause, resume, adjust speed, skip to any paragraph by clicking on it. Each paragraph highlights as it's read. Each word highlights within the paragraph.
That forty-seven-page QBR? Listened to it in 28 minutes at 1.5x while walking to get coffee.
Where This Makes a Real Difference
Proofreading your own writing. You know that thing where you read your own draft five times and miss the same awkward sentence every time? Your brain autocorrects what it expects to see. But your ears don't lie. Hearing "the team has proactively synergized the deliverables" read aloud in a human voice makes you physically cringe in a way that reading it silently never does. It's the single best editing trick nobody talks about.
Reviewing someone else's document. Your teammate sent a 12-page product spec and asked for feedback by EOD. You've been in meetings since 9am. You have a 30-minute commute home. Listen to the spec on the drive. Arrive with feedback already forming in your head.
Studying and lecture notes. Students who type their notes in Google Docs can listen to them while doing laundry, cooking, or lying on the couch with their eyes closed. It's not just convenience — research consistently shows that alternating between reading and listening improves retention.
Accessibility. Some people have dyslexia. Some have eye strain. Some have been staring at spreadsheets for eight hours and literally cannot focus on another block of text. This isn't an edge case — it's most knowledge workers by 4pm on a Wednesday. A natural-sounding text-to-speech tool turns a visual task into an audio one, and sometimes that's the difference between "I'll read it later" and actually reading it now.
Long collaborative documents. Google Docs is where teams dump everything. Meeting notes that grow to 30 pages. Wiki-style reference documents. Project postmortems. The kind of documents that are important enough to exist but too long for anyone to actually sit down and read. Now you can listen while doing something else.
Browser TTS vs. CastReader
Your browser has built-in text-to-speech. On Chrome, it uses your system's default voices — "Samantha" on Mac, "David" on Windows. These were state-of-the-art around 2014.
CastReader uses AI-generated voices. Neural TTS trained on natural speech patterns. The difference is immediately obvious: proper sentence rhythm, natural pauses, emphasis on the right words. Long documents don't become monotonous because the voice actually reads the way a person would.
Browser TTS also has no understanding of Google Docs' page structure. It either reads nothing (because the DOM has no real text nodes) or reads everything (toolbar labels, sidebar chat, "Share" button text). CastReader's specialized extractor gives you just the document content, in order, clean.
Works on Notion Too
Same idea, different extractor. Notion has its own unique DOM structure — block-based content with [data-block-id] elements, toggle blocks, inline databases, callout boxes. CastReader's Notion extractor understands all of it.
And it works on ChatGPT, Claude, Gemini, Medium, Substack, academic papers, and basically any webpage with readable text. Each platform gets a specialized extractor that understands its specific structure. You don't configure anything — CastReader detects the site and handles it automatically.
The Cost
Free. No word limit. No daily cap. No "premium voices" tier. No account creation.
Every other TTS tool I tried had some version of "free for 500 words, then $9.99/month." Five hundred words is about two paragraphs of a Google Doc. That's not a tool — that's a teaser.
CastReader is the whole thing. For nothing.
Install CastReader from the Chrome Web Store and turn your Google Docs into something you can listen to.
