Discord Just Did What Meta Just Undid—End to End Encryption Is Now Default on Every Voice and Video Call, With One Big Exception

What Discord Announced

On May 19, 2026, BleepingComputer reported that Discord had completed the rollout of its end to end encryption protocol, DAVE, across every voice and video surface on the platform. The wording in the announcement was uncharacteristically definitive: "End to end Encryption is now standard for every voice and video call on Discord, outside of stage channels."

No opt in. No advanced settings menu. No "experiment" flag for power users. Voice and video are encrypted by default for every user on every platform, including the Discord clients on Xbox and PlayStation.

The scope of what is now protected:

• 1:1 voice calls in DMs.
• 1:1 video calls in DMs.
• Group DM voice and video calls.
• Voice channels inside servers.
• Go Live screen shares.
• Group calls launched from a server.

The one explicit exclusion is stage channels, which Discord designed for large public broadcasts where the audio is supposed to be observable by anyone in the room. End to end encrypting a one to many broadcast does not buy anything useful, so leaving it out is reasonable.

DAVE, Briefly

DAVE is Discord's open source end to end encryption protocol for real time audio and video. It is built on three primitives that are individually well understood:

• WebRTC encoded transforms. The media frames are encrypted at the encoded layer—after the codec compresses them but before they go onto the wire. The server still sees the encrypted blobs and the metadata it needs to route them, but it cannot decode the audio or video content.
• Messaging Layer Security (MLS). The group key exchange standard that came out of the IETF in 2023. MLS lets a group of participants agree on a shared key that rotates whenever someone joins or leaves, without any single participant being able to decrypt traffic from before their key was added.
• Ephemeral identity keys. Per session keys that get thrown away when the call ends. There is no long lived private key that can be subpoenaed and used to decrypt every call you have ever had.

DAVE was first introduced in September 2024 as a limited rollout. The full deployment took until March 2026 to complete across every supported platform—desktop, mobile, web, Xbox, PlayStation, and the Discord SDKs that game developers use to bundle voice chat into their own titles. May 2026 is the announcement that the rollout is done and the flag is flipped for everyone.

The Text Chat Hole

Here is the thing Discord did not bury: text messages are not encrypted, and "there are currently no plans" to change that. The company's explanation is straightforward: text features were built around the assumption that the server could read the content. Search, link previews, custom emoji, server moderation tools, automoderation rules, slash command integrations, and the entire bot ecosystem depend on the server having plaintext access to every message.

Retrofitting end to end encryption onto that architecture is technically possible but practically enormous. Signal manages it because Signal does not have a bot ecosystem. WhatsApp manages it because Meta accepts that link previews and search are degraded on encrypted devices. Discord has explicitly chosen not to make that tradeoff, which means every text message on the platform—every DM, every server channel, every announcement, every spoiler tagged paragraph—is plaintext to Discord and to whoever gets access to Discord's infrastructure.

For most users that does not change much. They already assume Discord can read their messages. For users who picked Discord because they thought encryption was on, the gap is real, and the May 19 announcement makes it sharper. The headline "Discord now end to end encrypted" is true for voice and video, and false for everything that gets typed.

The Meta Contrast

The Discord rollout lands exactly eleven days after Meta removed the Instagram DM end to end encryption feature it had spent four years promising. Both companies were operating in the same regulatory environment, with the same engineering literature available, and with the same trade offs to make. They reached opposite conclusions in the same fortnight.

Meta's argument for removing Instagram DM encryption was that users were not turning it on. Discord's solution to the same problem was to make encryption non optional. There is no setting to flip, no toggle to enable, no advanced menu to find. If your client is current, the call is encrypted. That is the only configuration anyone is allowed.

The two approaches reveal which company actually believes encryption is a feature and which one believes it is a checkbox. Defaults are policy. The default on Discord is now privacy. The default on Instagram, twice in five years, has been the opposite.

What Discord Can Still See

End to end encryption is not invisibility. There are several things Discord still has access to during an encrypted call:

• Who is calling whom. The metadata of which user IDs are connected to which call is necessary for routing and is in the clear.
• When the call started and ended. Session lifecycle timestamps are server side.
• How many participants are in the call. Group composition is visible to the server because the server has to deliver the encrypted media to every participant.
• The IP addresses of participants. Discord's voice servers see your connection metadata, just like any voice provider does.
• Bitrate, codec, and quality statistics. These are calculated server side from the encrypted frame envelopes.

None of this is exotic for an end to end encrypted system. It is roughly the same metadata Signal exposes, the same metadata WhatsApp exposes, and the same metadata your phone carrier exposes for a regular call. But it is worth being explicit about, because "end to end encrypted" gets conflated with "completely private" in marketing copy, and the two are not the same thing.

What This Means for the Platform

Discord's announcement is a real win for users who use the platform for voice chat, which is most of the gaming community. A teenager hopping on a voice channel with friends after school is now in a session whose audio cannot be retroactively retrieved by anyone, including Discord, including Discord's parent company, including whoever subpoenas Discord, and including whoever breaches Discord.

For voice chat users with elevated threat models—journalists, activists, sources, organizers—the change makes Discord a meaningfully better tool than it was a week ago. The voice and video layer is now in a category with Signal calls and WhatsApp calls. The text layer is still in a category with Slack and Discord 2024, which is to say a server with logs.

For everyone else, the change is mostly invisible. Calls work. They work the same way they did last week. The audio quality is the same. The lag is the same. The lobby music is the same. What is different is that Discord and any future attacker can no longer eavesdrop on the audio. That is a quiet but real privacy upgrade for a hundred and fifty million people.

The bigger story is the one Discord did not say out loud: that defaults shape behavior, and that a platform can choose to make encryption the path of least resistance instead of the path of greatest configuration. Google made the opposite choice on Gmail—mobile end to end encryption shipped, but only behind the enterprise paywall. Discord made the choice on voice and video. The text choice is still open.