Mac Has Eight Text Editors That Should Read Aloud. Here's How to Actually Make Them Listen-Friendly.

I write a lot on a Mac — code in BBEdit, rough drafts in Stickies, meeting notes in Apple Notes, shell output in Terminal that I need to skim back through an hour later. Every one of those apps has the same little gap. You can highlight text, press Option-Escape, and macOS reads it. A robotic voice, no pause, no highlight, no way to speed up or rewind, and the instant playback starts your eyes have nowhere to go. You drift. You miss the line you cared about. You look back up at the screen and you've lost your place. That's been true for twenty years on macOS and Apple hasn't fixed it.

This is the guide for fixing it across every native Mac editor — eight of them, free, one install.

Why Eight Editors, and Why Mac Has Never Been Great at This

You can argue that most Mac users only ever open TextEdit once. That's fair. But if you're a writer, researcher, or developer, your day is probably scattered across four or five text surfaces. A poet friend drafts in CotEditor because it launches in under a second. A tax accountant I know has 300 Stickies on her desktop with client notes. I personally have TextMate open for Ruby, Terminal for shell work, BBEdit for long-form essays, and Script Editor for the one AppleScript I've been maintaining since 2019 that backs up my blog drafts to iCloud. Every one of those apps handles text. Every one has the same hollow read-aloud story.

What macOS does give you is an AX API — Accessibility — that lets assistive apps read the currently selected text from any other app. This is how VoiceOver works. It's also how CastReader works, but for a different purpose: not reading the entire screen, just the specific selection you care about, with a highlight that glides word-by-word across your actual document. Same plumbing, different use case.

Here's the honest breakdown of each editor and what audio read-back actually unlocks.

TextEdit — The Default Nobody Uses Well

TextEdit is the macOS default text editor. Most people open it once to check if a file is really plain text, then never again. But if you write RTF letters, quick memos, or just paste text to strip formatting, TextEdit is the fastest path. Hearing a letter read aloud catches tone mistakes that reading it ten times never does — you wrote "I hope this finds you well" three times in two paragraphs and your eyes skimmed right past all three. Your ears won't.

Select the body, click the floating ▶ button that appears, and the highlight tracks each word inside the real TextEdit window. Full guide at Read TextEdit Aloud.

Stickies — Tiny Font, Giant Hidden Archive

I have 47 Stickies open right now. Most of them are grocery lists from 2024, but a few contain phone numbers I still need and a passage from a book I was trying to remember. The default Stickies font is 10 point, which is fine if your eyes are fifteen years old. For everyone else, listening to a sticky beats squinting at one.

Stickies works especially well for audio because the content is usually short, punchy, and action-oriented. Tick through your morning to-do list hands-free while making coffee. The app's read-aloud page is at Read Stickies Aloud.

Apple Notes — The Capture-Everything App

Apple Notes is where most Mac users actually do their thinking now. Scanned receipts, recipe steps, meeting minutes, book quotes, checklists, password hints, a draft apology to a friend. It's become Mac's universal scratchpad. And of course Apple has not shipped a word-level read-aloud experience for it on the Mac the way they have on iOS.

If you've ever walked between meetings wishing you could quickly run through the project notes you jotted this morning, that's the target use case. Select a section, click ▶, and listen on the walk. Full writeup at Read Apple Notes Aloud.

Script Editor — AppleScript Was Made for This

AppleScript's syntax reads almost like English — tell application "Finder" to make new folder at desktop with properties {name:"Archive"}. When you hear a well-formed AppleScript read in a natural voice, it actually sounds like prose. Which means bugs stand out. A misspelled handler name doesn't sound right. A missing parameter makes the sentence collapse mid-air. This is the single most underrated use case in the whole list.

Detail page: Read Script Editor Aloud. JavaScript for Automation (JXA) works the same way because it's just another text mode in Script Editor.

BBEdit — The Serious Mac Editor

BBEdit is the professional Mac text editor. It can open files that crash VS Code. It handles gigabyte logs without flinching. It's been around since 1992 and Bare Bones Software ships it from a small team in Massachusetts with the kind of meticulous care that feels increasingly rare. BBEdit has always had every feature a serious writer or developer needs — except a good read-aloud.

For long-form writers using BBEdit as their draft environment (there are a lot of them), listening catches redundancy. "This article has five paragraphs that all say the same thing in slightly different ways" is something your ears notice and your eyes don't. For developers, hearing a function plus its header comment read back before committing is faster than re-reading a wall of syntax. Full guide at Read BBEdit Aloud.

CotEditor — The Quiet Open-Source One

CotEditor is an open-source Japanese project that never quite caught on outside its home market but deserves to. It launches instantly. The UI is clean. It handles every text encoding you throw at it, which matters if you work with files that were last saved in 2008 on a Windows machine. No ads, no accounts, no telemetry. The entire ethos is "do one thing, well, forever."

CastReader pairs well with that — no account, free, local. Selection-read works identically to BBEdit's since both apps render standard NSTextView content. See Read CotEditor Aloud.

TextMate — The Classic Ruby Editor

TextMate 1 was the editor Ruby on Rails was built in. Literally — you can watch the original DHH Rails demo and see TextMate on screen. TextMate 2 is now open source under GPL and still beloved by a specific cohort of developers who never switched to Sublime, VS Code, or Cursor. Its bundle system is unmatched and its Command-T fuzzy finder is the thing every other editor tried to clone.

Hearing Ruby or Python comments read aloud is perfect for audio code review — especially on long functions where the eyes glaze after line 40. The selection API works in both TextMate 1 and TextMate 2. Full page at Read TextMate Aloud.

Terminal — The Unexpected One

This is the one I use most personally. When a kubectl describe spits out three pages of YAML, or a test run dumps a 60-line stack trace, I don't want to read that. I want to hear it while I stretch, or while I think about whether the test was actually wrong or the code was. Terminal.app exposes its scroll-back buffer to the AX API, which means selection-read works cleanly there too.

One caveat: this is Apple's Terminal specifically. iTerm2 and Warp have their own text renderers and don't currently expose text the same way. That's been raised as a feature request with both teams. For now, Terminal.app is where Mac audio shell-output review happens. Guide at Read Terminal Aloud.

One App, Eight Editors, Three Steps

Download CastReader for Mac. Grant Accessibility permission when prompted — that's the single step that unlocks all eight editors at once, because they all expose text through the same macOS AX plumbing. Select text in any of them, click the small ▶ that appears next to your selection, and listen. The same gesture, the same highlight behavior, the same voice picker, across your entire text workflow. There's nothing else to configure.

Speed control lives on the floating player — 0.5× for technical content you want to absorb, 1.5× for stuff you're just skimming. Click any paragraph to jump playback there. Switch voice mid-document if you change languages. The Accessibility permission is one-time. The app is permanently free — no account, no subscription, no daily limit. If you've been paying Speechify $140/year to read web articles, this is a straight swap for the editor side of your workflow.

The bigger picture is that macOS has had the plumbing for this for a decade. Apple just never made the experience good. Eight different editors, one missing feature, one day of work to implement it well. That's the project. See CastReader for Mac for the full feature list, or pick any of the eight pages above for a focused walkthrough of that editor specifically.