Discord has flipped the switch. Every voice and video call on the platform now runs protected by end-to-end encryption. No exceptions for direct messages, group chats, voice channels or Go Live streams. Stage channels remain the lone holdout. The change, finalized in early March and announced this week, marks the end of a multi-year push that began with cautious experiments in 2023.
Mark Smith, Discord’s vice president of core technologies, put it plainly in the company’s official blog post. “End-to-end Encryption is now standard for every voice and video call on Discord, outside of stage channels. No opt-in required.” The transition, he noted, demanded patience and exacting standards. It also delivers something rare at this scale: calls that even Discord cannot decrypt.
Users see a green lock icon when encryption is active. They can pull up a Voice Privacy Code or Stream Privacy Code and compare it out-of-band, preferably in another app such as Signal, to confirm no one has inserted themselves into the conversation. The mechanism draws on identity keys and an epoch authenticator exported from the underlying group protocol. Simple in concept. Hard in execution when millions of calls run simultaneously across wildly different devices.
The technical foundation is DAVE, short for Discord Audio and Video Encryption. Stephen Birarda, staff software engineer on audio and video infrastructure, introduced the protocol in a September 2024 post. “During E2EE A/V calls, no one but the participants can access the contents of ongoing audio and video conversations. Outsiders, including Discord itself, never know the media encryption keys.”
DAVE builds on Messaging Layer Security, the IETF standard published as RFC 9420 and already used by WhatsApp for group chats. It handles key exchanges as participants join or leave, ensuring fresh symmetric keys for each call segment. Media itself gets encrypted after encoding and decrypted before decoding through WebRTC encoded transforms. The selective forwarding unit still routes packets but sees only ciphertext. Old transport encryption between client and server stays in place for authentication.
That cross-platform reality defined the challenge. A single call might connect a Windows desktop, an iPhone, a PlayStation 5, an Xbox and a Chrome tab at once. Each expects low latency and high quality. Earlier efforts at end-to-end encryption in consumer apps often stumbled here. Discord chose to open the protocol and its reference implementation on GitHub. It invited external review from Trail of Bits, published the audit reports, and expanded its bug bounty to cover DAVE specifically. The company even collaborated with Mozilla to fix an upstream Firefox issue that blocked proper function in real-world conditions.
Clément Brisset led the push to bring support to web browsers, consoles, bots and the Social SDK throughout 2025. By the start of March 2026 the last gaps closed. Unsupported clients could no longer join calls. The fallback code that allowed unencrypted connections is now being stripped out. After that step, unencrypted calls simply will not happen. Discord’s support documentation spells out the deadlines and the green lock that confirms protection.
The timing carries weight. Meta walked away from default end-to-end encryption plans for Instagram messaging earlier this year. TikTok, after acquiring certain U.S. operations, signaled it would not pursue the feature for direct messages. Against that backdrop, Discord’s move stands out. It covers hundreds of millions of monthly users who treat the app as home for gaming squads, remote work huddles, activist coordination and late-night study groups. For many, voice channels function as always-on digital offices or living rooms. The content that once sat decryptable on Discord’s servers now stays locked to the participants alone.
Privacy advocates took notice years ago. The Electronic Frontier Foundation welcomed the initial DAVE announcement in 2024, calling it a strong step that put Discord ahead of Slack and Microsoft Teams on this front. It also urged further progress, particularly around text messages, which remain outside encryption for now. Smith acknowledged the gap directly. “We have no current plans to extend E2EE to text messages. Many of the features people use on Discord were built on the assumption that text isn’t end-to-end encrypted, and rebuilding them to work with encryption is a meaningful engineering challenge.”
Recent coverage echoes the finality of the rollout. Shacknews reported Monday that the lengthy process had reached completion, highlighting the DAVE protocol’s open and audited nature. Lowyat.NET noted the same milestone, stressing that text-based chats continue without encryption while calls gain default protection. On X, security observers pointed out the practical consequences: subpoenas for call content now hit a technical wall. One analyst wrote that “the last big unencrypted voice graph on the consumer internet” had gone dark.
Yet trade-offs exist. Console users and those on very old clients faced forced updates. Web versions required careful engineering to satisfy WebRTC constraints without leaking metadata that codecs expect. Stage channels, built for large broadcasts rather than intimate talk, stay unencrypted because their architecture and audience size make the current design impractical. And while call content is now shielded, metadata such as who spoke to whom and when still flows through Discord’s systems.
The company insists the quality bar held. Latency, audio fidelity and video performance show no measurable drop for most users. That matters. Gamers notice a 30-millisecond increase. Remote teams abandon tools that glitch during presentations. Discord bet it could deliver structural privacy without asking users to accept friction. So far the data says it succeeded.
Smith credited the engineering leads in his post. “DAVE was a multi-year effort that required patience, genuine craft, and a willingness to hold the bar, even when it would have been easier to ship something faster or cut scope. Stephen and Clément, the lead engineers behind this work, truly went above and beyond throughout.” He described the result as “an open, externally validated protocol running across every platform Discord supports.”
But this is not a finish line. The team continues to refine DAVE, monitor the bug bounty and explore protocol improvements. Future updates could tighten verification flows or reduce the computational cost on lower-end devices. Text encryption, if it ever arrives, would demand a ground-up rethink of features such as search, notifications and moderation that currently rely on server-side access.
For industry watchers the lesson sits in the details. True end-to-end encryption at Discord’s diversity of platforms and volume of concurrent calls required more than clever cryptography. It demanded open standards, external audits, browser-vendor cooperation and years of patient migration. Competitors eyeing similar features now have a working blueprint and a public warning: shortcuts tend to break either security or user experience.
Users don’t need to change behavior. They simply update their apps if they haven’t already. The green lock appears. The privacy code sits ready for verification when trust matters most. Behind the scenes the infrastructure quietly enforces a promise that once seemed distant. Calls on Discord are private by default. The company no longer holds the keys. And that changes the equation for everyone who relies on the platform to speak freely.
Discord Completes Rollout of End-to-End Encryption Across All Voice and Video Calls first appeared on Web and IT News.