For years, Discord held the same uncomfortable position as every other major communication platform: it could technically access your voice and video calls if asked.
Today, Discord has now completed the full rollout of end-to-end encryption (E2EE — where only the people in a call can decrypt it, not even the platform itself) across every voice and video call on the platform, no settings toggle required.
The change affects DMs, group DMs, server voice channels, and Go Live streams — essentially everything except Stage Channels, which are designed for large broadcast-style audiences where E2EE isn't architecturally suited.
What DAVE actually does under the hood
The system is built on a custom protocol called DAVE — Discord's Audio and Video End-to-End Encryption — developed with input from cybersecurity firm Trail of Bits, using WebRTC encoded transforms and Message Layer Security (MLS) to protect calls even from Discord's own servers. In plain terms: each audio and video frame gets encrypted using a per-sender symmetric key that only the people on the call can access. External parties, including Discord, are never privy to the media encryption keys.
What makes DAVE technically remarkable isn't just what it does — it's where it has to do it. DAVE has been providing E2EE for tens of millions of calls on Discord every single day, spanning users simultaneously on laptops, phones, PlayStations, Xboxes, and web browsers in the same call. Getting a single encryption protocol to work seamlessly across that device diversity, without audible lag or call quality regressions, is genuinely non-trivial.
At one point, extending DAVE to Firefox exposed a browser-level bug that Discord couldn't simply work around. Rather than ship a patch or quietly drop Firefox support, the team went upstream — collaborated directly with Mozilla, identified the root cause in Firefox's codebase, and helped get a fix merged. That's a level of commitment to "doing it right" that most platform teams don't bother with.
How to verify your call is actually encrypted
On the desktop app, a green lock icon labeled "End-to-end encrypted" now appears in the Voice/Video Details panel, along with a new Privacy tab containing a Voice Privacy Code. That code can be compared out-of-band with other participants — on a different platform or in person — to confirm no one is being impersonated on the call. Privacy codes update whenever participants join or leave. It's an optional but meaningful layer for high-stakes conversations.
Each Go Live stream also has its own Stream Privacy Code accessible via the right-click context menu, letting streamers verify the encrypted state of their broadcast independently from the voice channel.
This E2EE rollout landed in the middle of a period of significant trust turbulence for Discord. The platform simultaneously introduced "teen-by-default" settings globally, requiring age verification via face scan or government ID — a move that drew backlash, especially after a 2025 breach at Discord's third-party verification vendor exposed at least 70,000 government ID photos. Completing call encryption — where even Discord cannot listen in — is a direct response to exactly that kind of trust problem.
It's a notable split: Discord is simultaneously expanding what it can't access (your calls) while navigating controversy over what users are being asked to hand over (government IDs). Call encryption doesn't resolve that tension, but it does represent a structural, verifiable privacy guarantee that no policy document can replicate.
What's still not encrypted: text
Discord has confirmed it has no current plans to extend E2EE to text messages. The reason is engineering scope, not reluctance: text-based features like message search, moderation, bots, and content filtering are all built on the assumption that messages are readable server-side.
Re-architecting that for E2EE would require rebuilding significant platform infrastructure. For now, if a conversation needs full end-to-end security — text and audio — Signal remains the better choice.
What this means for users
If you're on a current version of the Discord app, your voice and video calls are now encrypted by default, with no action required on your part. Third-party applications and bots that connect to Discord voice must now implement DAVE support to continue functioning, which means some niche bots may have already broken or require updates from their developers. If a bot in your server abruptly dropped out of voice channels around March 2026, this is likely why.
The DAVE protocol is open-source, and the implementation has been publicly audited — which means the encryption claim isn't one you have to take on faith. That's rarer than it should be.