Text-to-Speech in Discord Group Chats and DMs: What Works and What Doesn’t

Text-to-speech in a Discord group chat or DM does not work the way most people hope: an ordinary server bot cannot read those messages at all, so no server TTS bot can speak into them. Discord only gives a guild-installed bot access to its own server’s channels. What actually works is Discord’s own per-user Text-to-Speech setting, which reads new messages aloud to you, on your device, with the built-in voice, wherever they appear, DMs and group chats included. On a server, the reliable broadcast path is a TTS bot connected to a voice channel. A handful of user-installable apps can follow your account into DMs, but they only answer commands you run there. Details and exact steps for each path below.

Can a Discord bot read DMs and group chats?

No, not a normal server bot. A bot you invite to a server is a guild-installed app, and Discord’s developer documentation is explicit about what that unlocks: access to “server channels, members, events”. Your direct messages and group DMs sit outside that server, so the bot has no rights there and sees nothing. The same documentation’s install table shows the only route that does reach DMs: a user-installed bot, which is available “in DMs, group DMs, and any server”. So the bot that reads aloud in your voice channel cannot also follow you into a private chat. That is a platform structure, not a product bug.

The TTS that does work in group chats: Discord’s per-user setting

Discord ships a native text-to-speech feature, documented in its official Text-to-Speech help article, and it is the one TTS mechanism that reaches a DM or group chat. The reading happens on each person’s own client, with the built-in voice, according to that person’s settings, so one user enabling it does not make the whole group hear anything.

On desktop, here is the exact path:

1. Click the gear icon (User Settings) at the bottom left of the app.
2. Open Notifications and scroll to the Text-to-Speech section.
3. Choose one of three options:
   * For all channels (which the help article describes as “any channel, across any server”): every message you can see is read aloud to you, whether or not the sender used /tts. The article warns you will hear “a fair amount of TTS” this way.
   * For current selected channel: only the channel you are looking at is read.
   * Never: nothing is read to you, unless you send a /tts message yourself.

To speak your own words, type /tts before a sentence in any chat and press Enter. Whether that plays for you is controlled under User Settings > Accessibility, where the Text-to-Speech option turns the /tts command on or off and a “Text to speech rate” slider sets the speed. The help article stresses one detail that trips people up: these two settings are separate. Other people hear your /tts line only if their own TTS notifications are on, and vice versa. Discord also notes that the voice itself depends on your system, because TTS follows the default system settings, so a browser reads with a different voice than the Windows or Mac app.

Delft Stack’s short explainer walks through why the built-in TTS is tied to text channels and permissions rather than to shared voice audio, which is the same distinction that decides what works in a group chat:

Why /tts in a text channel is not a group broadcast

Many people search for text-to-speech in a group chat expecting everyone in it to hear the same thing. Discord’s /tts never does that in a text channel. It plays in the channel where you typed it, and who hears it is decided by each listener’s own client and notification settings. On a server it can also be shut off entirely: Discord models it as the Send Text-to-Speech Messages permission (SEND_TTS_MESSAGES), a per-role, per-channel privilege, and its permissions documentation describes it as allowing “for sending of /tts messages”. A group DM has no such guild permissions to revoke (and no server admin to revoke them), which is precisely why the per-user route above is the one that works there.

What works on a server instead: a TTS bot in a voice channel

The shared-audio version of Discord text-to-speech exists only inside a server voice channel. A TTS bot connects to the voice room through Discord’s Gateway API, whose documentation covers managing voice state and connecting to voice channels, and it plays generated speech to everyone in that room. Typed text becomes a waveform like the one below, and the bot streams that audio into the room rather than into one listener’s earphones.

Our guide to Discord text-to-speech in voice chat walks through the full mechanics, and our step-by-step text-to-speech bot setup covers the invite, permissions, and configuration for a server. The honest limit stays the same: that bot cannot read DMs or group chats, because it cannot see them.

User-installable apps: the narrow route into DMs

The only apps that operate inside DMs and group DMs are user-installed ones. Discord’s tutorial on developing a user-installable app explains that a developer must explicitly configure a user-install context, and that context installs the app’s slash commands (the applications.commands scope) to your account, so they follow you wherever you go. That is how an app such as Interaction Bot shows an “Add App” button next to “Add to Server” on its App Directory listing, as our voice-chat guide notes. Two catches remain: most TTS bots on the directory are built for servers only, and even a user-installed app cannot broadcast spoken chat to the whole group, because there is no voice channel inside a DM for it to play into. It is command-response TTS, not group reading.

Which path fits your situation?

The short answer

An ordinary Discord server bot cannot read DMs or group chats, so there is no bot-based text-to-speech inside them. What works is Discord’s own per-user Text-to-Speech setting (User Settings > Notifications > Text-to-Speech), which reads messages aloud to you alone with the built-in voice, and, on a server, a TTS bot connected to a voice channel, which reads chat aloud to everyone in that room.