What is end-to-end encryption?

Published 31 August 2026 by Nyra

End-to-end encryption (E2EE) is a method of securing messages so that only the sender and the intended recipient can read them. The message is encrypted on the sender's device and decrypted on the recipient's device, so relaying servers and network eavesdroppers see only unreadable ciphertext.

You have seen the phrase on WhatsApp, Signal, and half the apps on your phone. End-to-end encryption is the single most important idea in private messaging, and it is one of the most misunderstood. Here is what it actually means, and what it quietly does not do.

What end-to-end encryption means

End-to-end encryption, usually shortened to E2EE, protects a message so that only the two ends of a conversation can read it. The sender's device scrambles the message into ciphertext using keys that only the sender and recipient hold. The recipient's device is the only place it is turned back into readable text. Everything in the middle, including the company that runs the service, ever only handles the locked version.

The important word is ends. The protection is anchored to the devices at each end of the conversation, not to a server in between. That single detail is what separates true E2EE from the weaker encryption most of the internet runs on.

How it works, in plain terms

You do not need the mathematics to understand the shape of it. When you first message someone, the two apps quietly exchange public keys, the half of a key pair that is safe to share. Each device keeps its matching private key to itself and never sends it anywhere.

From those keys, each side derives a shared secret that an eavesdropper cannot reconstruct, and messages are encrypted with it. Because the private keys never leave the devices, a server can pass billions of messages back and forth without ever being able to open one. Modern messengers also rebuild the encryption keys for almost every message, so cracking one does not unlock the rest. If a term here is new, our glossary defines the building blocks one line at a time.

E2EE versus transport encryption

Many people confuse end-to-end encryption with the padlock in a browser address bar. They are not the same thing. The padlock is transport encryption, which protects data only while it travels to a server. The server then decrypts it, reads it, and often stores it. Ordinary email works this way, and so do Telegram's regular cloud chats. End-to-end encryption removes the server's ability to read anything at all. The table makes the difference concrete.

Put simply, transport encryption asks you to trust the server. End-to-end encryption does not have to.

What end-to-end encryption does not protect

This is where honest guides part ways with marketing. E2EE is powerful and narrow: it protects the contents of your messages, and only that. Three things it does not cover matter a great deal.

• Metadata. Encryption hides what you said, not that you said it. The server still has to route each message, so it can see which account talked to which, when, how often, and roughly how large each message was. That pattern alone can be revealing. We cover it in depth on our metadata guide.
• The person on the other end. E2EE delivers your message safely to the recipient's device, but it cannot control what happens next. A recipient can screenshot it, forward it, copy it, or simply show someone the screen.
• A compromised device. If a phone is unlocked, stolen, or infected with spyware, the messages are already decrypted on it. Encryption in transit does nothing once an attacker is reading the screen, which is why a device passcode and disappearing messages matter alongside it.

Forward secrecy: a stronger property

A basic E2EE system can rely on one long-lived key. If that key ever leaks, every message ever sent with it can be unlocked. Forward secrecy is a stronger design that avoids this. The app derives a fresh key for each message or session and discards the old ones, so a key captured today cannot decrypt yesterday's conversations. When you compare messengers, forward secrecy is one of the properties that separates a serious tool from one that merely ticks the encryption box.

The messengers that get this right tend to share a lineage. Most build on the Signal Protocol, which combines X3DH for the initial key agreement with the Double Ratchet that supplies forward secrecy message after message.

Which apps use it by default

Supporting E2EE and switching it on for everyone are two different things, and the difference is the whole game. Most people never change a default, so a protection that is off by default protects almost nobody.

• On by default: Signal encrypts every chat end-to-end and is widely treated as the reference standard. WhatsApp and Apple's iMessage also apply it to all conversations automatically.
• Optional or off by default: Telegram only encrypts end-to-end inside Secret Chats, which are not the default and are unavailable in groups. Its ordinary chats are transport encrypted, so Telegram's servers can read them.

Where Nyra fits, honestly

Nyra is an anonymous, end-to-end encrypted messenger currently in development. It uses the same well-studied construction as the reference standard, X3DH for the initial handshake and the Double Ratchet for forward secrecy, built on the independently audited @noble cryptographic primitives. Messages are encrypted on your device and decrypted on your contact's device, so Nyra's server relays sealed envelopes it cannot open.

Two honest notes belong here. First, those underlying primitives are independently audited, but Nyra itself has not yet had an independent audit, so treat this as a design description rather than a track record. An audit of Nyra is planned before launch. Second, Nyra never asks for a phone number or email, so there is no real-world identifier attached to your account in the first place. You can read how the encryption is built on our security page, and exactly what a server can still see on our metadata guide.

Frequently asked questions