Discord Defaults to E2EE for Video & Voice Messages

Discord has rolled out end-to-end encryption (E2EE) for all voice and video communications across its platform. This move represents a significant milestone in secure real-time communication.

The feature, now enabled by default as of March 2026, applies to direct messages, group calls, voice channels, and Go Live streams without requiring any user opt-in.

At the core of this deployment is the DAVE protocol, an open and externally audited encryption framework specifically designed for real-time audio and video.

First introduced in September 2024, DAVE was built to handle Discord’s unique infrastructure, which enables users to connect simultaneously from diverse environments, including desktops, mobile devices, web browsers, PlayStation, and Xbox consoles.

DAVE Protocol Powers Secure Communication

Key technical highlights include:

• Open-source implementation available via GitHub (libdave).
• External security audit conducted by Trail of Bits.
• Expanded bug bounty program covering protocol vulnerabilities.
• Cross-platform compatibility, including browser-based and console clients.

Unlike traditional messaging encryption systems, DAVE ensures low-latency performance while encrypting live communication streams, a significant engineering challenge at Discord’s scale.

Discord began experimenting with E2EE in August 2023. Over the next two years, the company gradually deployed the DAVE protocol across all supported platforms.

By 2025, encryption support had been extended to web clients, bots, and the Social SDK, eliminating compatibility gaps.

A notable technical hurdle emerged during browser integration, where Firefox presented compatibility issues.

Instead of bypassing support, Discord engineers collaborated directly with Mozilla to identify and patch the root cause in the browser’s codebase, demonstrating a commitment to ecosystem-wide security.

With full deployment complete, Discord now enforces encryption across all supported clients.

Systems that do not support DAVE are prevented from joining calls, and the company is actively removing legacy fallback mechanisms for unencrypted communication.

• E2EE is mandatory for all voice/video calls.
• No backward compatibility for unencrypted clients.
• Encryption occurs transparently with no user impact on performance.

Discord confirmed that call quality and latency remain unchanged despite the added encryption layer.

One notable exception is Stage Channels, which are designed for large-scale broadcasts such as events and AMAs. Due to their architecture, these channels do not support E2EE.

Additionally, Discord has stated that there are currently no plans to extend end-to-end encryption to text messaging.

Many existing platform features rely on server-side text processing, making such a transition technically complex.

This move positions Discord among a growing list of platforms adopting default E2EE for user communications.

By open-sourcing the protocol and enabling external audits, Discord aims to provide verifiable privacy guarantees while maintaining performance at scale.

Security researchers and developers can further analyze the DAVE protocol via its public documentation and repositories, contributing to ongoing validation and improvement efforts.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.