How to Disable Text to Speech on Any Device or App

Text to speech (TTS) is a helpful accessibility feature — until it isn't. Whether it's reading out every notification, narrating your screen unexpectedly, or creating awkward moments in public, knowing how to turn it off quickly is useful knowledge. The challenge is that TTS isn't controlled from one single place. It lives in operating systems, individual apps, browsers, and accessibility menus — sometimes all at once.

What Text to Speech Actually Is (and Where It Lives)

Text to speech is a technology that converts written text into spoken audio. It's built into every major operating system and is also embedded independently in thousands of apps and websites.

This matters for disabling it because there are effectively two layers of TTS:

  • System-level TTS — built into Windows, macOS, Android, iOS, and ChromeOS as part of accessibility settings
  • App-level TTS — enabled within specific apps like Google Chrome, Microsoft Word, Kindle, YouTube, or screen readers like NVDA or JAWS

Turning off one layer doesn't automatically disable the other. A reader who disables Windows Narrator may still find that their browser reads pages aloud if that feature was separately activated.

Disabling Text to Speech on Windows

Windows offers TTS through Narrator, its built-in screen reader, and through Speak functions in Office apps.

To turn off Narrator:

  • Press Windows key + Ctrl + Enter to toggle Narrator on or off
  • Or go to Settings → Accessibility → Narrator and switch it off

To prevent Narrator from launching at startup:

  • In the same Narrator settings panel, disable "Start Narrator before sign-in" and "Start Narrator after sign-in"

Some users accidentally trigger Narrator through keyboard shortcuts without realizing it's a TTS feature running at the OS level.

Disabling Text to Speech on macOS

Apple's equivalent is Spoken Content, found under System Settings.

  • Go to System Settings → Accessibility → Spoken Content
  • Turn off "Speak Selection" and "Speak Screen"
  • If VoiceOver is active, disable it via System Settings → Accessibility → VoiceOver, or press Command + F5

macOS also has a text-to-speech shortcut that can trigger accidentally. Check your keyboard shortcut settings if TTS keeps activating unexpectedly.

Disabling Text to Speech on Android 🔊

Android's TTS engine is a background service that apps draw on. Disabling it at the system level affects all apps that rely on it.

  • Go to Settings → Accessibility → Text-to-Speech Output
  • You can't fully "delete" the TTS engine here, but you can disable TalkBack (Android's screen reader) via Settings → Accessibility → TalkBack

To disable TalkBack quickly: press and hold both volume keys simultaneously (on most Android devices running Android 8.0 or later).

Individual apps like Google Maps, Google Assistant, or navigation apps have their own voice output settings that need to be disabled separately within each app.

Disabling Text to Speech on iOS and iPadOS

Apple's screen reader on iOS is VoiceOver.

  • Go to Settings → Accessibility → VoiceOver and toggle it off
  • To stop Speak Screen: Settings → Accessibility → Spoken Content → Speak Screen (toggle off)
  • To stop Speak Selection: same menu, toggle off Speak Selection

A common source of confusion on iPhone is that Siri, VoiceOver, and Speak Screen are three separate systems — disabling one doesn't disable the others.

Disabling Text to Speech in Browsers

Browsers can read pages aloud through built-in features or extensions.

BrowserHow to Disable TTS
Microsoft EdgeOpen Immersive Reader, click the stop button; or disable the Read Aloud feature in toolbar settings
Google ChromeRemove any TTS extensions via chrome://extensions; disable Select-to-Speak if using ChromeOS
FirefoxNo native TTS; disable any installed read-aloud add-ons
SafariGo to View menu → disable Reader; or turn off Spoken Content in macOS settings

Browser extensions are a frequent hidden source of unexpected TTS — checking your installed extensions is often the fastest fix.

Disabling Text to Speech in Specific Apps

Many apps bundle their own TTS independently of the operating system:

  • Kindle app: Settings → Accessibility → turn off VoiceView or disable text-to-speech playback
  • Microsoft Word: Review tab → Read Aloud → click stop or close the toolbar
  • Google Docs: Tools → Accessibility settings → uncheck "Turn on screen reader support"
  • GPS/navigation apps (Google Maps, Waze): Each has a voice guidance setting inside the app's sound or navigation settings

Variables That Affect How You Disable TTS

The right steps depend heavily on several factors:

  • Operating system and version — menu locations change between OS updates; older Android versions have different accessibility menu structures than Android 12+
  • Whether TTS was enabled at the system or app level — system-level changes won't silence app-level TTS engines
  • Screen reader vs. read-aloud features — full screen readers (VoiceOver, TalkBack, Narrator) behave differently from lightweight read-aloud tools in word processors or browsers
  • Whether TTS is tied to an accessibility profile — some devices have accessibility shortcuts or profiles that re-enable TTS features on restart
  • Third-party apps and extensions — TTS functionality installed by apps or browser add-ons operates outside OS-level controls entirely

The Layer Problem Most People Miss 🔍

The most common reason TTS keeps coming back after someone disables it: they turned off the wrong layer. System TTS and app TTS are genuinely independent. A user might disable Android's TalkBack but still hear voice output from their navigation app, podcast app, or Google Assistant — because those have separate audio pipelines.

Similarly, disabling a browser extension stops in-browser reading but has no effect on a system screen reader running simultaneously.

Understanding which layer is producing the audio — system, browser, or app — is what determines which setting to change. The same TTS symptom on two different devices, or even two different setups on the same device, can require completely different fixes depending on what's actually running underneath. ⚙️