How to Turn Off Text-to-Speech on Any Device

It's 11:47 PM. The apartment is dead quiet. Your partner fell asleep twenty minutes ago. You pick up your iPhone to check one last email and suddenly a robotic voice announces, at full volume, INBOX, FORTY-THREE UNREAD MESSAGES. Your partner bolts upright. The dog starts barking. You're fumbling with the phone, tapping everywhere, and the voice just keeps going — SETTINGS, GENERAL, ACCESSIBILITY — narrating every single thing your finger touches like a commentator at a tennis match who refuses to shut up.

I've been there. Twice, actually. Once in a library, once during a work presentation where my laptop decided the entire room needed to hear my email subjects read aloud. The second time was worse because my manager was mid-sentence when my computer cheerfully announced YOU HAVE THREE NEW MESSAGES FROM LINKEDIN.

So yeah. Turning off text-to-speech. You'd think it would be obvious. One toggle. One switch. Done. But every operating system hides it in a different place, calls it a different name, and wraps it in enough menus that you start to wonder if the designers wanted you to keep it on.

Here's how to kill it on everything you own.

The iPhone is the worst offender and I will die on this hill. Apple has two separate text-to-speech systems and they're both easy to trigger accidentally. VoiceOver is the nuclear option — it takes over the entire interface. Every tap reads an element aloud, you have to double-tap to actually select things, and if you've never used it before the phone becomes borderline unusable because the gesture model changes completely. To turn VoiceOver off, you need to open Settings, then tap Accessibility, then tap VoiceOver, and flip the toggle. Except if VoiceOver is already running, tapping doesn't work normally — you tap once to select, then double-tap to activate. So you're sitting there jabbing the screen and nothing's happening and the voice keeps talking. If you have Siri enabled, the fastest escape hatch is saying "Hey Siri, turn off VoiceOver." If you set up the Accessibility Shortcut (triple-click the side button), that works too. But if you didn't set that up beforehand? You're stuck doing the tap-then-double-tap dance through four screens of settings while your phone narrates the journey.

Then there's Speak Screen, which is the sneakier one. VoiceOver at least changes how the phone behaves so you know something's wrong. Speak Screen just sits there, dormant, until you swipe down from the top with two fingers and suddenly Siri starts reading the entire page. I triggered this by accident while scrolling with greasy fingers making dinner. Thought my phone was possessed. To turn it off, go to Settings, then Accessibility, then Spoken Content, and switch off Speak Screen. While you're there, check Speak Selection too — that's the one that adds a Speak button when you highlight text, which is less alarming but still annoying if you didn't ask for it.

iPads follow the exact same paths, by the way. Same Settings, same Accessibility menu, same toggles. Apple kept that consistent at least.

Android is more straightforward but Google named their screen reader TalkBack, which sounds like a feature for arguing with your phone. To turn off TalkBack, pull down the notification shade, look for the Accessibility icon, and tap it. If TalkBack is active, same problem as VoiceOver — the gesture model changes. You tap to select, double-tap to confirm. The shortcut is holding both volume buttons simultaneously for three seconds, which works on most Android phones running 9 or later. If that doesn't work, open Settings, go to Accessibility, find TalkBack, and toggle it off. Samsung phones bury it one level deeper under Installed Apps or Downloaded Apps depending on the One UI version, because Samsung.

There's also Select to Speak on Android, which is the equivalent of Apple's Speak Selection. It puts a little floating button on screen and reads whatever you tap. Settings, Accessibility, Select to Speak, off. That one's less panic-inducing since you have to explicitly tap the button, but if you enabled it by accident during phone setup (Google asks about accessibility features during OOBE and it's easy to tap the wrong thing), it sits there on every screen looking like a tiny confused person icon.

Windows has Narrator. Narrator has been shipping with Windows since XP and Microsoft has made it progressively harder to trigger accidentally, which I appreciate, but if you've managed to turn it on anyway the keyboard shortcut to kill it is Windows key plus Ctrl plus Enter. Same combo turns it on, same combo turns it off. Toggle. If that doesn't work, Settings, Accessibility, Narrator, switch it off. Windows 11 also has a secondary TTS engine buried in the old Control Panel under Speech Recognition — this one controls the system voice used by apps that call the Windows Speech API. You probably don't need to touch it unless some third-party app is reading things to you and you can't figure out why.

I genuinely forgot Windows still had Control Panel until I went looking for that setting. It's like finding a VHS player still plugged in behind your TV.

Mac is the one I deal with most because I write on a MacBook. VoiceOver on macOS is Command plus F5, or if you have a MacBook with Touch ID, triple-press the Touch ID button. Same shortcut toggles it off. You can also go to System Settings, then Accessibility, then VoiceOver, and uncheck it. There's a spoken content feature under System Settings, Accessibility, Spoken Content that controls whether the Mac speaks selected text when you press a key combination (the default is Option plus Escape). I accidentally set that up once, forgot about it, and three weeks later hit Option-Escape while reaching for something else and my Mac started reading a legal document out loud in an open office. My coworker turned to me and said, "Is your computer okay?" No. No it was not.

Chrome the browser has its own text-to-speech layer that's separate from your operating system. If a website is speaking to you and it's not your OS-level screen reader, it might be the Web Speech API — which means the website itself is generating speech and the only way to stop it is to close the tab or mute it. Right-click the tab, click Mute Site. If you installed a Chrome extension that reads pages aloud and you want it to stop, click the puzzle piece icon in the toolbar, find the extension, and either disable it or remove it. Chrome's built-in accessibility features live at chrome://settings/accessibility — Screen Reader is the relevant toggle, but it only activates if ChromeVox (Chrome OS's screen reader) or your OS screen reader is detected.

Now for the apps that ambush you.

Kindle has a text-to-speech feature in the mobile app that starts when you tap the screen, tap the Aa icon or the three-dot menu, and somehow land on the Read Aloud option. Or on Kindle e-readers with VoiceView, you might enable it during setup without realizing it. On the Kindle app, just tap the screen to bring up the reading controls and hit the pause button or close the audio player bar. On a Kindle device, hold the power button for nine seconds to restart if you can't figure out the menu, which sounds aggressive but honestly sometimes it's the fastest path.

Discord reads messages to you if you enable the /tts command or if someone in your server sends a message starting with /tts. That's not your device's text-to-speech — that's Discord's own feature. To stop it, go into Discord's settings (the gear icon by your username), then Accessibility, and toggle off Allow Playback and Usage of /tts Command. This prevents both sending and hearing TTS messages. If someone's abusing /tts in a server you moderate, server settings, then Integrations or Permissions depending on your Discord version, and revoke the Send TTS Messages permission.

Google Maps will announce turn-by-turn directions and some people mistake this for text-to-speech being enabled. It's not a system setting. Tap the speaker icon in the top right during navigation. Tap it until you see the speaker with a line through it. Muted. You can also go into Maps settings, Navigation, and adjust the Guidance Volume to silent. Though at that point you might miss your exit, which is its own kind of annoying.

I want to say something that might sound contradictory after seventeen hundred words about silencing robot voices.

Text-to-speech, when you actually want it, when you choose to turn it on deliberately for a specific purpose, is genuinely useful. I read long articles with TTS while cooking. I listen to documentation while commuting. The difference between TTS that assaults you from nowhere and TTS you intentionally activated is the difference between someone grabbing your arm on the street and a friend tapping your shoulder. When done right, with a good Chrome extension, it's a completely different experience. Same physical action, completely different experience.

That's actually why we built CastReader. It's a Chrome extension that reads web articles aloud with paragraph-by-paragraph highlighting so you can follow along. But here's the thing — it only runs when you click it. It never speaks unless you ask it to. No accidental activation, no mysterious voice at midnight, no narrating your settings menu. You open an article, you click the icon, it reads the article. You close the tab, it stops. The way TTS should work. You can try it free if you're curious, and if you ever want to turn it off, you click the button again. One click. That's it. Finally quiet.