On 18 May 2026, Mark Smith, Discord’s VP of Core Technology, wrote that end-to-end encryption was now standard for every voice and video call on Discord outside Stage channels, with no opt-in required. He dated the completed migration to the beginning of March 2026. The path he recited is public: an August 2023 experiment, a 17 September 2024 launch of the DAVE protocol by Stephen Birarda, a 2025 expansion by Clément Brisset to browsers, consoles, bots, and the Social SDK, then a hard requirement that clients support DAVE before joining a call. Discord said it was removing unencrypted-fallback code so that fallback would become impossible. DAVE — Discord Audio and Video Encryption — was introduced in Birarda’s 17 September 2024 post as an open protocol with a public whitepaper and libdave library. Discord said Trail of Bits reviewed both design and implementation and that HackerOne rewards cover DAVE bugs. The 2026 post emphasises platform diversity: laptop, phone, PlayStation, Xbox, and browser in one call. Smith wrote that Discord worked with Mozilla to fix a Firefox issue rather than drop the browser. Call quality, he said, remained at the expected level and encryption is transparent to users. The documented exception is Stage channels, built for broadcasts, AMAs, and town halls. Discord says that architecture is not a personal conversation and stays outside E2EE. Go Live streams, DM calls, group DMs, and server voice channels are inside the completed migration according to the May 2026 post. Text is the other explicit limit. Smith wrote: “We have no current plans to extend E2EE to text messages,” because many Discord features assume the service can read text for search, moderation, and similar functions. That sentence is a non-announcement. This briefing therefore does not list Discord text encryption as upcoming work. Direct messages, server chat, and search remain in Discord’s existing service model. Encryption of voice does not stop Discord from seeing who joined a channel, for how long, or what was typed. Trail of Bits findings mentioned in the public protocol write-up include issues such as AES-GCM not being key-committing and a historical medium-severity note about unencrypted range offsets. Those are auditor observations on the protocol document, not a claim that production calls are currently breakable. Readers should look at the latest dave-protocol revision rather than treat a 2024 finding as unfixed forever. What this means in practice If you need confidential voice among friends or a small team, Discord now claims the media keys never leave the participants, including Discord itself, for the session types listed. Verify the in-client lock where Discord documents it. Do not discuss secrets in text channels or Stage events. Server owners still need moderation tools that only work because text is not E2EE. Cyber71 cannot add DAVE to a Stage, decrypt a past call, or obtain Discord’s internal keying material. What is still unclear Discord did not publish, in these two posts, the fraction of minutes still on fallback during the removal window, the current DAVE protocol version on every console SKU, or a user-visible identity verification story comparable to WhatsApp’s 60-digit codes. Whether bots that receive audio under E2EE are true ends of the conversation depends on how those bots are hosted — a point the 2026 post flags as supported but does not fully threat-model. Independent tests of whether Discord can still inject a silent recording bot are outside the announcement. Smith’s 2026 post is also a statement about what Discord will not rebuild soon. Search, moderation, and bots that read channel text are product features that assume Discord can see words. Communities that moved sensitive planning from WhatsApp to Discord text on the assumption that “Discord is encrypted now” have misread the announcement. Voice E2EE plus plaintext chat is a common pattern (Microsoft Teams documents a similar split). Users who need both voice and text confidentiality still need a different tool for the words, or to treat Discord text as organisationally visible.

Sources

  1. Discord Blog — Every Voice and Video Call on Discord Is Now End-to-End Encrypted2026-09-24
  2. Discord Blog — Meet DAVE: Discord’s New End-to-End Encryption for Audio & Video2026-09-24

Cyber71 links the primary material behind each report so readers can check it directly. External pages are not under our control and may change.

All research

Need help with a security issue?

Describe the situation and we will open a private case for follow-up.

Get Security Help