Discord has used its official blog to underline that, since March 2026, every voice and video call on the service has been protected by its own end-to-end encryption protocol, DAVE (Discord Audio and Video End-to-End Encryption)[1]. The company had announced in September 2025 that "starting March 1, 2026, clients and apps without DAVE support will no longer be able to participate in Discord calls,"[2] and following the forced cutover on March 2, every direct message, group message, voice channel, and Go Live stream has been running with E2EE turned on by default[3][4].

DAVE becomes the default for every call

Discord's pivot to running DAVE in full production traces back to a roadmap post in September 2025. That Engineering and Developers blog laid out the plan to bring DAVE to every remaining platform — browsers, consoles, and the Social SDK — and set March 1, 2026 as the cutoff date after which older clients would be disconnected[2]. Discord noted at the time that DAVE was already protecting "tens of millions of calls every single day," so the March transition was less a staged rollout than a switch flipped for the entire user base[2].

The support documentation now spells out that audio and video in direct messages, group messages, voice channels, and Go Live streams have required E2EE since March 2, 2026[3]. Text chat is unchanged, still using server-side encryption and remaining subject to Discord's content moderation policies[3][4].

A VP of Core Tech reflects on years of work

According to a March 3 explainer from US tech outlet PiunikaWeb, Discord's VP of Core Tech, Mark Smith, marked the completion on X (formerly Twitter), writing, "Took a few years to solve the edge cases and wait out deprecation times for older clients, but we're here," and adding that he was "really proud of the team today"[4].

The piece also restated how DAVE works under the hood. Every frame is encrypted with a per-sender symmetric key that only the call participants can access, and Discord itself does not hold a copy[4]. The company has stated that "external parties, including Discord, are never privy to the media encryption keys"[2]. On the user side, a lock icon and a Voice Privacy Code in the call view let participants confirm that E2EE is active and that they are talking to the people they expect[3][4].

Stage channels remain outside the E2EE perimeter. They use a different architecture geared toward large-audience broadcasts and continue to rely on transport encryption between clients and Discord's servers rather than per-frame E2EE[2][3].

Browsers, consoles, and the cutoff line for old clients

To bring DAVE to browsers, Discord paired the WebRTC Encoded Transform API with Web Workers, implementing the cryptographic core in WebAssembly[2]. Discord's own benchmarks show that audio frames run roughly 28 percent faster than with SubtleCrypto, while larger video frames are about 192 percent slower — a trade-off the team accepted in order to protect low-latency audio[2].

On Firefox, Discord ran into a deadlock when WebRTC script transforms were invoked too early. The team patched Firefox itself, with the fix landing in Firefox 142.0[2]. On consoles, Xbox One and Xbox Series S|X are picking up DAVE support in stages, and PlayStation is set to follow after its next system update[2]. Because the Discord Social SDK ships with DAVE built in, third-party apps that rely on it inherit E2EE calling without extra integration work[2].

On the audit side, Trail of Bits — which reviewed the original DAVE design and implementation in 2024 — went back in June 2025 to audit the new browser integration, with the report published openly[2]. The DAVE protocol also remains in scope for Discord's bug bounty program[2]. The flip side is that long-stale clients and unmaintained third-party implementations are now locked out of calls, so users who had let updates lapse need to refresh their app before they can connect again[2][4].

Summary

With the March 2, 2026 enforcement behind it, Discord has settled DAVE in as the standard transport for voice and video calls. A design in which Discord itself does not hold the keys, ongoing audits by Trail of Bits, and broad coverage that spans browsers and consoles together give the non-text side of the platform a steady, properly framed E2EE posture.

Source [1]: https://discord.com/blog/every-voice-and-video-call-on-discord-is-now-end-to-end-encrypted

Source [2]: https://discord.com/blog/bringing-dave-to-all-discord-platforms

Source [3]: https://support.discord.com/hc/en-us/articles/25968222946071-End-to-End-Encryption-for-Audio-and-Video

Source [4]: https://piunikaweb.com/2026/03/03/discord-enforcing-end-to-end-encryption-voice-video-calls/