Messenger begins default end-to-end encryption rollout

Meta has started upgrading personal conversations on Messenger to use end-to-end encryption (E2EE) by default. The company describes this as the most significant milestone in a project that began with Mark Zuckerberg's 2019 vision statement, and one that required rebuilding large parts of the application's protocols to preserve existing features while improving privacy and security.

Messenger first offered E2EE in 2016 through its Secret Conversations feature. The new default rollout extends that capability to all personal one-to-one messages, with group messaging and Instagram Direct still in testing phases. Two whitepapers accompany the announcement: one describes the core cryptographic protocol for message transmission between clients, and the other details Labyrinth, a protocol for encrypting stored message history across a user's devices.

Two goals, eight design principles

Meta frames its E2EE work around two primary objectives: only the sender and intended recipients can read message contents, and nobody—including Meta itself—can forge messages that appear to come from someone else. From those goals, the company derives eight overlapping concepts that guide the implementation:

  • Confidentiality in transit: Message contents must be authentically and securely transmitted between endpoint devices, building on protocols like Signal (used in WhatsApp, Messenger, and Instagram Direct) and the IETF's recently standardized Messaging Layer Security protocol.
  • Confidentiality in storage: Messenger has long stored message history server-side. Rather than forcing local-only storage, Meta designed Labyrinth so ciphertexts can live on its servers while decryption keys remain under user control.
  • Control over endpoints: Users need visibility into and management over the set of devices receiving their messages, plus awareness of when that set changes.
  • Private feature designs: Features must work device-to-device without relying on server-side access to content. Much of Messenger's functionality historically depended on server-side processing, making this a substantial engineering effort.
  • Logging limitations: Telemetry is essential at Messenger's scale, but it must not inadvertently leak message content back to Meta's systems.
  • Application security: E2EE expands the threat model to include the service provider and reduces the provider's ability to protect users from attacks. Meta cites work on memory safety and E2EE surface coverage under its bug bounty program.
  • Deliberate protection boundaries: Defining "message content" is less straightforward than it seems in a complex messaging app. Meta focuses on setting clear boundaries and user expectations without compromising usefulness.
  • Third-party scrutiny: External verifiability matters. The two whitepapers join prior publications including a safety whitepaper, a human rights impact assessment, and a security principles document. Meta also supports the Code Verify browser extension so researchers can confirm the code they assess is what users actually receive.

Four major technical challenges

Building from WhatsApp's and Secret Conversations' prior E2EE experience, Meta identified four challenges that required new approaches:

  1. Multi-device capability: WhatsApp's model requires a single primary device to authenticate companions. Messenger's model reflects the Facebook network, where users authenticate with username and password on any device. Meta adopted the Secret Conversations approach to multi-device while ensuring it works across its user base.
  2. Feature support: Messenger includes features that don't exist or work differently in WhatsApp. Some required rebuilding from scratch; others needed new privacy technology. For sticker searches, Meta used OHAI (Oblivious HTTP Application Intermediaries) and Anonymous Credentials so users can search Facebook's first-party sticker library without revealing what they search for.
  3. Message history: Messenger clients traditionally operate from a small local cache backed by a server-side database. Neither WhatsApp nor Secret Conversations worked this way. Labyrinth, the new encrypted storage system, supports server-side ciphertext storage, on-demand client loading, multi-device operation, and key rotation when devices are removed.
  4. Web support: E2EE had to work within existing web surfaces, including the main Facebook site. Web platforms carry different constraints than native apps, and web users tend to add and remove devices in different patterns than mobile-only users.

Ongoing rollout

Default E2EE for personal one-to-one messages on Messenger is now launching globally, but the work continues. Group messaging on Messenger and Instagram Direct remain in testing. On Instagram, Meta is testing disappearing messages for one-to-one Direct conversations in select countries—these expire 24 hours after sending, consistent with Messenger's ephemeral messages, and are built on the same E2EE infrastructure. Further expansion and testing on Instagram are planned over the next year.