What Is End-to-End Encryption? A Plain-English Guide
Part of: Encryption basics, without the jargonChecked against protocol standards, app documentation and dated reporting.
Imagine posting a letter in a box that only your friend has the key to. The postman carries it, the sorting office handles it, but nobody on the way can open it. That is end-to-end encryption. Ordinary encryption is more like a sealed van: the letter is safe on the road, but the depot opens every box to sort it.
Most apps you use have the van. Fewer have the box. This guide explains the difference in plain words, so you can tell which one you are getting.
Short answer: end-to-end encryption (E2EE) means a message is locked on your device and can only be unlocked on the devices of the people you sent it to. The company that carries it cannot read it. It protects the content; it does not hide who you talk to or when.
What is end-to-end encryption?
End-to-end encryption is a way of sending messages where only the sender and the intended recipients hold the keys to read them. The message is encrypted on the sender's device and decrypted only on the recipients' devices. Servers in between pass along scrambled data they cannot read, even if they wanted to, or were asked to.
The "ends" are the devices: your phone, your laptop, your mother's tablet. Everything in the middle, including the app company, is outside the circle.
How does end-to-end encryption work?
Each device makes a pair of keys: a public key it can share, and a private key that never leaves the device. A sender uses the recipient's public key to lock a message; only the matching private key can unlock it. Modern apps also change keys constantly, so one stolen key exposes as little as possible.
A slightly fuller picture, without the maths:
- Your app creates keys on your device. The private part stays there.
- Your app fetches your contact's public keys from the server. The server is like a phone book: it hands out locks, never keys.
- The message is locked before it leaves your phone. What travels and what is stored is unreadable.
- Keys keep changing. Good protocols refresh keys as the conversation goes on, so an old key can't open new messages, and a stolen new key can't open old ones. Security people call these forward secrecy and post-compromise security.
- You can check you have the right lock. Apps offer "safety numbers" or codes you can compare in person, to make sure nobody slipped in a fake key.
What is the difference between encryption in transit and end-to-end encryption?
Encryption in transit protects data on its way between your device and the company's server; the company then decrypts it and can read it. End-to-end encryption protects data all the way from your device to the recipient's device, so the company in the middle never sees it readable. Both use strong maths; what differs is who holds the keys.
| Type | Protects against | Who can read your message |
|---|---|---|
| Encryption in transit (TLS, the browser padlock) | Strangers on the network, the café Wi-Fi | The app company, and anyone it shares with or is breached by |
| Encryption at rest | Someone stealing the company's disks | The app company (it holds the keys) |
| End-to-end encryption | The network, the company's servers, a breach of those servers | Only the people in the conversation |
What does end-to-end encryption not protect?
E2EE hides what you say, not everything about you. The service can still see metadata: who you talk to, when, how often, and from which IP address. It cannot protect a message once it is on a device, so a stolen unlocked phone, a screenshot or a cloud backup without E2EE can still expose it.
Four honest limits worth knowing:
- Metadata. Who, when and how often is often revealing on its own.
- The ends themselves. Malware on a phone reads messages after they are decrypted.
- Backups. A chat backup stored by a cloud provider without its own end-to-end encryption can be read there. WhatsApp, for example, offers end-to-end encrypted backups as an option you switch on (WhatsApp security).
- Where the keys are kept. If an app stores your private keys on its own servers behind a short PIN, the company is part of your security. Security researchers raised exactly this about X's XChat in April 2026 (CyberInsider, 25 Apr 2026).
Which apps use end-to-end encryption by default in 2026?
Signal and WhatsApp encrypt chats, groups and calls end-to-end by default. Messenger encrypts personal chats and calls by default since its December 2023 rollout. Telegram only does so in opt-in one-to-one Secret Chats and in calls. Instagram removed its optional encrypted DMs on 8 May 2026. Discord encrypts voice and video calls, not text.
| App (checked 5 Nov 2026) | Default E2EE for messages? | Notes |
|---|---|---|
| Signal | Yes, chats, groups and calls | Signal Protocol, open source (signal.org/docs) |
| Yes, chats, groups and calls | Personal messages "remain end-to-end encrypted" while ads run in the Updates tab (Meta, 16 Jun 2025) | |
| Messenger | Personal chats and calls | Default rollout announced 6 Dec 2023 (Meta); see our Messenger guide |
| Telegram | No (Secret Chats are opt-in, 1:1 only) | "Server-client encryption is used in Cloud Chats (private and group chats)" (Telegram FAQ) |
| Instagram DMs | No | Encrypted DMs "no longer supported as of 8 May 2026" (Malwarebytes, 15 May 2026) |
| Discord | Calls yes, text no | "No current plans to extend E2EE to text messages" (Discord, 18 May 2026) |
| iPhone ↔ Android texts (RCS) | Yes, with iOS 26.5, a supported carrier and the latest Google Messages | Built on MLS; shown with a small lock (MacRumors, 11 May 2026) |
Why does end-to-end encryption matter?
Because a readable copy of your conversations on someone else's server is a risk you never chose: it can be breached, demanded, misused by an insider or mined for ads. End-to-end encryption removes that copy. You don't need to have anything to hide; you only need things that are nobody else's business, like a parent's test results.
There is a quieter point too. When encryption is optional, few people switch it on. Meta said "very few people were opting in" before it removed encrypted Instagram DMs (9to5Google, 13 Mar 2026). Protection that has to be switched on mostly isn't. Look for default.
How can I tell if a chat is end-to-end encrypted?
Look inside the app, not in the advert. Most apps show a label or a lock in the chat itself, let you compare a security code with your contact, and explain the scope in their help pages. If the app's own documentation says group chats or backups are excluded, believe the documentation.
A three-question check for any app:
- Is it on by default for one-to-one chats and groups?
- Is the protocol named and public, for example the Signal Protocol or MLS (RFC 9420)?
- Has an independent firm audited it, and can you read the result?
What is Nadeemi doing?
Nadeemi is a social network in Arabic and English. Its private messages, group chats and Circles are encrypted on your device with MLS (RFC 9420) in the public beta, and the server refuses messages that aren't. We still label them "end-to-end encryption coming", because no independent expert has audited our code yet. Public posts are encrypted in transit and at rest, and our servers can read them, because they are public. The full list is on what we can and can't see, and our MLS explainer covers the protocol.
FAQ
What does end-to-end encrypted mean in simple words? Only you and the people you are talking to can read the messages. The app company carries them but cannot open them.
Can the police read end-to-end encrypted messages? Not from the company's servers, because the company does not hold the keys. Messages can still be read on an unlocked device, from unencrypted backups, or from a participant who shares them.
Is end-to-end encryption the same as being anonymous? No. It hides the content of messages, not your identity. The service usually still knows your account and who you talk to.
Are WhatsApp group chats end-to-end encrypted? Yes. WhatsApp encrypts personal and group chats and calls by default. More in our WhatsApp guide.
Can public posts be end-to-end encrypted? Not meaningfully, because they are meant to be read by everyone. Honest networks encrypt them in transit and at rest and say so.
Which protocol is best? The Signal Protocol and MLS are both open, well studied and widely used. MLS was designed to stay efficient in large groups. What matters most is default use, audits and where the keys are kept.
Sources (checked 5 November 2026)
- IETF, RFC 9420, The Messaging Layer Security (MLS) Protocol (July 2023): https://www.rfc-editor.org/rfc/rfc9420
- Signal, technical documentation (Signal Protocol): https://signal.org/docs/
- WhatsApp, security overview (E2EE, encrypted backups): https://www.whatsapp.com/security/
- Meta, WhatsApp Updates tab: ads in Status, promoted channels (16 June 2025): https://about.fb.com/news/2025/06/helping-you-find-more-channels-businesses-on-whatsapp/
- Meta, default end-to-end encryption on Messenger (6 Dec 2023): https://about.fb.com/news/2023/12/default-end-to-end-encryption-on-messenger/
- Telegram FAQ (cloud chats vs secret chats): https://telegram.org/faq
- Malwarebytes, Meta's confusing new approach to chat privacy (15 May 2026): https://www.malwarebytes.com/blog/news/2026/05/metas-confusing-new-approach-to-chat-privacy
- 9to5Google, Meta is killing E2EE for Instagram DMs (13 Mar 2026): https://9to5google.com/2026/03/13/meta-is-killing-end-to-end-encryption-for-instagram-dms-soon/
- Discord, every voice and video call is now E2EE (18 May 2026): https://discord.com/blog/every-voice-and-video-call-on-discord-is-now-end-to-end-encrypted
- MacRumors, iOS 26.5 RCS end-to-end encryption (11 May 2026): https://www.macrumors.com/2026/05/11/ios-26-5-rcs-e2ee-launch/
- CyberInsider, XChat standalone app, security concerns (25 Apr 2026): https://cyberinsider.com/xchat-launches-standalone-ios-app-as-security-concerns-remain/
Names of other apps are trademarks of their owners, used only for comparison. Nadeemi is not affiliated with any of them.
Drafted with AI help and checked by a person on the date above.