699eee792235758e12e070c1
Discord Rolls Out End-to-End Encryption for Voice and Video Calls
Discord now provides end-to-end encryption by default for all voice and video calls across platforms, covering DMs, group DMs, voice channels, and Go Live streams, with stage channels excluded. Built on the extended DAVE protocol after extensive testing, there is no opt-in required and no plans to encrypt text-based messages.

Discord rolls out end-to-end encryption on voice and video calls
OverviewDiscord has announced that end-to-end encryption (E2EE) is now the default for all voice and video communications on its platform. The rollout, completed in March after extensive large‑scale testing, means that calls, whether one‑on‑one or in groups, are protected from eavesdropping by third parties. The move comes as part of a broader effort to enhance user privacy across the service, which counts hundreds of millions of active users worldwide.
What changed and how it works
- End-to-end protection is now standard for all voice and video interactions on Discord, with stage channels remaining the sole exception due to their design for large, public broadcasts.
- The encryption layer was built by extending the open-source DAVE protocol to run across all supported platforms, including desktop, mobile, web browsers, game consoles (PlayStation and Xbox), and Discord SDKs.
- The scope of encryption covers direct messages, group direct messages, voice channels, and Go Live streams.
- No opt-in is required; users automatically benefit from E2EE for these communications.
Technical underpinnings
- The updated protocol leverages WebRTC encoded transforms to secure media streams.
- For scalable group protection, Messaging Layer Security (MLS) is used to manage key exchanges.
- Ephemeral identity keys are employed to boost privacy while minimizing disruptions and latency when participants join or leave sessions.
- The engineering effort focused on maintaining low latency and a seamless user experience even as security was tightened, with attention to cross‑platform compatibility.
Platform coverage and notable considerations
- Availability spans desktop clients, mobile apps, web interfaces, and gaming consoles, along with integrations via Discord SDKs.
- A longstanding compatibility challenge highlighted by tests was with the Firefox browser, which required close collaboration with Mozilla to resolve rather than offering workarounds or restricting browser support.
Text communication plans
- At this time, there are no announced plans to extend end-to-end encryption to text-based communications. Discord explains that expanding E2EE to text would face significant architectural challenges because the platform’s text features were designed with non-encrypted messaging in mind.
Timeline and development context
- DAVE was first introduced in September 2024, created with auditing assistance from Trail of Bits to secure audio and video calls, group chats, voice channels, and Go Live streams.
- The encryption deployment reached completion in March of the reporting year, paving the way for the formal public announcement in May 2026.
- This transition involved removing unencrypted fallback code across supported clients to ensure a consistent encrypted experience.
Security and privacy implications
- End-to-end encryption ensures that only participants in a call can decrypt and access the media streams; even the service provider cannot decrypt the content of protected communications.
- The focus on low latency helps preserve the natural feel of conversations, a critical requirement for voice and video calls used in gaming, collaboration, and social communities.
- The staged exclusion (Stage channels) is a deliberate design choice reflecting their broadcast-oriented purpose rather than private conversations.
Related considerations and context
- In addition to core features, the rollout aligns with broader industry movements toward stronger user privacy protections in real-time communications.
- The move may influence how communities on Discord manage private discussions, collaborations, and live events going forward.
Related reads and supplemental material
- Context on other encryption enhancements in messaging and email services.
- Broader discussions around encryption implementations in modern communication platforms.
- Articles exploring best practices for securing real-time communications and mitigating latency impacts.
Notes on supplementary resources
- A companion piece discusses automated testing and validation practices in security domains, highlighting the need to assess threat-blocking controls and detection rules beyond mere connectivity.
Related topics
- Discord and E2EE
- End-to-end encryption and video conferencing
- Security considerations for real-time communications
- Cross-platform encryption implementations
End of post.


