# Discord Completes End-to-End Encryption Rollout Across All Voice and Video Calls


Discord has announced the completion of its end-to-end encryption (E2EE) deployment across all voice and video communications on its platform, marking a significant milestone in protecting user privacy at one of the world's largest communication platforms. The implementation, finalized in March 2026, now covers approximately 200 million monthly active users and represents an industry-leading commitment to encrypted communications infrastructure.


## What Happened: Discord's Encryption Implementation Complete


As of May 2026, all voice and video calls on Discord are protected by default with end-to-end encryption, with no user opt-in required. The rollout represents the culmination of an extensive engineering effort that extended the company's DAVE (Discord Audio/Video Encryption) protocol across Discord's entire supported platform ecosystem.


The encryption layer now protects:

  • Direct Messages (DMs)
  • Group Direct Messages
  • Voice channels
  • Go Live streams
  • Desktop, mobile, web, and console clients (PlayStation and Xbox)
  • Discord SDKs

    • The only exception is Stage channels, which remain unencrypted by design since they function as large public broadcasts rather than private conversations. Discord confirmed it has already begun removing legacy client code that supported unencrypted fallback options.


    ## Background and Context: The Road to End-to-End Encryption


    Discord's journey toward comprehensive E2EE began in September 2024 with the introduction of the DAVE protocol, developed in collaboration with renowned security firm Trail of Bits. The initial implementation secured audio and video calls, but the company faced significant technical challenges in extending this protection to all platforms and maintaining the low-latency performance users expect.


    Why this matters for Discord:

  • Discord serves as the primary communication platform for gaming communities, content creators, businesses, and interest-based groups
  • With 690 million registered users globally, Discord has become a critical infrastructure for remote collaboration
  • The platform processes millions of concurrent voice and video connections daily
  • Privacy-conscious users have long advocated for encrypted communications across all modalities

    • The decision to implement E2EE across the board represents a recognition that audio and video communications are as sensitive as text messages, containing intimate conversations, business discussions, and personal information that deserves protection.


    ## Technical Details: How DAVE Works at Scale


    The DAVE protocol leverages several sophisticated encryption technologies working in concert:


    | Component | Purpose |

    |-----------|---------|

    | WebRTC Encoded Transforms | Encrypts audio/video at the codec level before transmission |

    | Messaging Layer Security (MLS) | Manages scalable group key exchanges for large channels |

    | Ephemeral Identity Keys | Ensures forward secrecy without disrupting session continuity |


    Key technical challenges Discord solved:


    1. Cross-Platform Compatibility: Extending DAVE to web browsers, desktop applications, mobile platforms, and gaming consoles required reimplementation across different technical stacks. Discord engineers worked directly with Mozilla to resolve Firefox compatibility issues rather than implementing workarounds, ensuring all users receive the same privacy protections.


    2. Latency Management: E2EE encryption adds computational overhead. Discord engineered DAVE to maintain the sub-100ms latency thresholds required for natural conversation, ensuring the migration was "unnoticeable" to users during calls.


    3. Group Dynamics: Voice channels can have hundreds of concurrent participants. Managing encryption keys for dynamic group membership (users joining and leaving mid-call) without introducing noticeable delays required careful implementation of MLS protocols.


    4. Platform Fragmentation: Supporting PlayStation and Xbox alongside traditional computing platforms meant navigating different security models, processing constraints, and network conditions—each requiring distinct implementation approaches.


    ## Implications: What This Means for Users and Organizations


    ### For Individual Users

  • Default Privacy: Users now have strong encryption protection without taking any action or understanding cryptography
  • No Performance Trade-off: The implementation is transparent, with minimal latency impact
  • Comprehensive Coverage: Privacy extends across all communication modes on the platform

    • ### For Organizations Using Discord

  • Data Protection: Sensitive business discussions on Discord voice channels are now protected from network-level eavesdropping
  • Compliance Alignment: E2EE strengthens Discord's compliance posture for industries with privacy regulations
  • Reduced Interception Risk: Attackers on the same network cannot capture unencrypted voice or video data

    • ### For the Broader Industry

    Discord's deployment of mandatory E2EE across such a large platform sets a new expectation. Competing platforms—including Microsoft Teams, Slack, and others—will face increased user pressure to implement similar protections.


    ## What About Text? And Why Not?


    Notably, Discord has explicitly stated there are no current plans to extend E2EE to text-based communications. The company cited significant engineering challenges: Discord's text features were architected from the ground up with non-encrypted messaging assumptions, making retrofit encryption substantially more complex than extending DAVE to audio/video.


    This represents a pragmatic trade-off. While text encryption remains valuable, the architecture changes required would necessitate a near-complete rewrite of Discord's core messaging system—a multi-year effort with significant risk. Discord prioritized delivering robust E2EE for voice and video rather than attempting both simultaneously.


    ## Recommendations: What Organizations Should Do


    For IT Security Teams:

  • Update risk assessments to reflect that Discord voice/video communications are now encrypted in transit
  • Verify employee awareness that voice channel conversations benefit from this protection
  • Conduct security awareness training emphasizing that E2EE still requires endpoint security (e.g., malware on user devices can capture plaintext before encryption)

    • For Privacy-Conscious Teams:

  • Evaluate whether Discord now meets organizational communication policies for sensitive discussions
  • Document the E2EE implementation in security controls inventories
  • Continue monitoring for text encryption announcements

    • For All Users:

  • Understand that E2EE protects against network eavesdropping but not local device compromise
  • Remember that Discord server owners and admins may still log or record conversations (E2EE doesn't prevent that)
  • Recognize this as a net privacy improvement without becoming complacent about endpoint security

    • ## HackWire Analysis


    Discord's E2EE rollout is significant not for technical novelty—Signal and WhatsApp have offered similar protections for years—but for scale and default enforcement. With 200 million monthly active users, Discord has now placed mandatory encryption on one of the internet's largest communication pipelines. This matters for three critical reasons.


    First, it normalizes encryption as a baseline expectation. Prior to this announcement, users of many mainstream communication platforms accepted unencrypted voice and video as inevitable trade-offs for convenience. Discord's framing—"end-to-end encryption is standard for every voice and video call"—resets user expectations and will pressure competitors to match this standard within 12-24 months.


    Second, it demonstrates that encryption at scale does not require sacrificing performance. Discord maintained sub-100ms latency while extending DAVE across PlayStation, Xbox, browsers, and mobile. This directly refutes the "encryption is too slow" argument that security skeptics have wielded for years. Organizations that cite latency concerns when resisting encryption now have a harder argument.


    Third, the implementation reveals what's actually difficult in modern security: not cryptography, but infrastructure. Discord's engineering challenges weren't about the math—MLS and WebRTC transforms are well-understood. The friction came from Firefox compatibility issues, cross-platform key management, and architectural constraints built into a decade-old text platform. This pattern repeats across enterprise security: encryption is easy; retrofitting it into legacy systems is hard.


    One important caveat: E2EE is not a silver bullet. Discord users should understand that encryption protects against network eavesdropping but not against local compromise (malware on a user's device can capture audio before encryption). Additionally, Discord's ability to moderate content, detect abuse, and comply with law enforcement requests may be more constrained once traffic is encrypted. The company should be transparent about these trade-offs.


    What to watch: The text encryption silence is telling. Expect this to become a user demand within 6-12 months. If Discord delivers text E2EE, it will accelerate adoption of encrypted messaging across the platform. If they don't, it will become a competitive weakness as competitors (Slack, Teams) eventually offer it.


    — HackWire Editorial


    ## Related Coverage


  • Read more in our [Vulnerabilities](https://www.hackwire.news/category/vulnerabilities) coverage
  • Cross-reference with [Breaches](https://www.hackwire.news/category/breaches) and [Malware](https://www.hackwire.news/category/malware)
  • Stay current via the [HackWire homepage](https://www.hackwire.news/)