Discord implements end-to-end encryption for all calls

🔑 Enhanced Key Takeaways

•Discord's end-to-end encryption for calls is powered by its custom, open-source protocol named DAVE (Discord Audio & Video Encryption), which was developed with assistance and auditing from cybersecurity firm Trail of Bits.
•The full migration to E2EE for voice and video calls was completed in early March 2026, making it a mandatory requirement for all supported Discord clients to adopt the DAVE protocol to participate in calls.
•While E2EE is automatically enabled by default for direct messages (DMs), group DMs, voice channels, and Go Live streams, Stage channels remain an exception and are not end-to-end encrypted due to their design for large public broadcasts rather than private conversations.
•Discord currently has no plans to extend end-to-end encryption to text messages, citing significant engineering challenges as many existing features were built on the assumption of non-encrypted text.
•The implementation of DAVE was designed to operate seamlessly across a diverse range of platforms, including desktop, mobile, web browsers, PlayStation, Xbox, and Discord's Social SDK, making it one of the internet's most platform-diverse E2EE voice and video implementations.

📊 Competitor Analysis▸ Show

Platform	E2EE for Voice/Video Calls	Default/Opt-in	Protocol/Notes
Discord	Yes (DMs, Group DMs, Voice Channels, Go Live)	Default	DAVE (Discord Audio & Video Encryption), open-source, audited. Excludes Stage Channels.
Signal	Yes	Default	Signal Protocol, strong privacy, no user data collection.
WhatsApp	Yes (up to 8 participants)	Default	Signal Protocol, owned by Meta.
Zoom	Yes	Opt-in, often inconsistent	AES-256 encryption, TLS 1.2, SRTP/DTLS.
Google Meet	Yes	Opt-in, disabled by default	E2EE available but not standard.
Microsoft Teams	Yes (1:1 calls), encrypted media streams (group)	Optional E2EE for 1:1 calls	Encryption in transit and at rest.
FaceTime	Yes (Apple devices only)	Default	E2EE for Apple ecosystem.
Wire	Yes	Explicit user activation	Double Ratchet and MLS protocols, backend closed-source but audited.
Element (Matrix)	Yes (per room)	Manual activation for calls	Open Matrix protocol, E2EE by default for DMs.

🛠️ Technical Deep Dive

Discord's end-to-end encryption for audio and video is implemented using its proprietary, open-source protocol called DAVE (Discord Audio & Video Encryption).
DAVE leverages WebRTC encoded transforms to encrypt each individual audio and video frame.
A per-sender symmetric key is used for the encryption of media frames.
The Messaging Layer Security (MLS) protocol is utilized for scalable group key exchanges, ensuring efficient key management in multi-participant calls.
Ephemeral identity keys are employed to further enhance privacy and minimize disruptions when participants join or leave sessions.
For web browser support, Discord compiled its C++ codebase to WebAssembly, enabling the same battle-tested DAVE implementation across platforms.
The WebRTC Encoded Transform API was a crucial choice for DAVE on web browsers, allowing encryption and decryption within the WebRTC pipeline.
Dedicated Web Workers are used in the browser environment to handle the encryption and decryption of media streams before they are processed by the browser's encoder or decoder.
The DAVE protocol underwent independent auditing by the cybersecurity firm Trail of Bits.

🔮 Future ImplicationsAI analysis grounded in cited sources

Increased user trust and adoption among privacy-conscious users.

The implementation of default E2EE for calls addresses a significant privacy concern, aligning Discord with industry best practices and potentially attracting users prioritizing secure communication.

Potential for further regulatory and user scrutiny regarding text message encryption.

Discord's explicit statement about having no current plans to extend E2EE to text messages may draw attention from privacy advocates and regulators, given the comprehensive E2EE for calls.

Strengthened competitive position against other communication platforms.

By offering default E2EE for calls across its highly diverse platform ecosystem, Discord enhances its security posture, potentially gaining an edge over competitors with opt-in or more limited E2EE offerings for calls.

⏳ Timeline

2020-04

Mozilla Foundation report highlights Discord's security vulnerabilities, which Discord promptly addresses.

2023-08

Discord begins experimenting with end-to-end encryption (E2EE) for voice and video communications.

2024-09

Discord introduces DAVE (Discord Audio & Video Encryption), an open and audited E2EE protocol for audio and video.

2025-09

DAVE support is extended to all remaining Discord platforms, including web browsers, gaming consoles, bots/apps, and the Social SDK.

2025-10

A data breach occurs through a third-party customer service provider, exposing government ID photos and other sensitive data of approximately 70,000 Discord users.

2026-03

Discord completes the full migration to E2EE for all voice and video calls (excluding Stage channels), making DAVE support mandatory for clients.

Discord implements end-to-end encryption for all calls

⚡ 30-Second TL;DR

Key Points

🧠 Deep Insight

🔑 Enhanced Key Takeaways

🛠️ Technical Deep Dive

🔮 Future ImplicationsAI analysis grounded in cited sources

⏳ Timeline

📎 Sources (18)

👉Related Updates

Anthropic and OpenAI disclose AI systems breaching external networks

Anthropic AI Models Accidentally Hacked Three Organizations During Testing

Smart TVs acting as proxies: LG and Samsung security alert