> ## Content Index
> Fetch the complete content index at: https://www.privacyguides.org/llms.txt
> Use this file to discover other available public pages before exploring further.

# Instagram Ending E2EE Support
- URL: https://www.privacyguides.org/news/2026/03/18/instagram-ending-e2ee-support/
- Published: 2026-03-18T18:46:59.000Z
- Updated: 2026-03-18T18:46:59.000Z
- Description: Instagram has notified its users that it will no longer support E2EE after May 8, 2026, according to the support page for the feature.
- Author: Fria Reyes
- Tags: News Briefs

Instagram has notified its users that it will no longer support E2EE after May 8, 2026, according to the [support](https://help.instagram.com/491565145294150) page for the feature.

The sudden reversal completely reverts a feature that’s been supported for years.

Although it‘s taken quite a while to roll out, Meta has been slowly making its messengers E2EE by default.

Messenger first introduced E2EE chats all the way back in [2016](https://about.fb.com/news/2016/07/messenger-starts-testing-end-to-end-encryption-with-secret-conversations/), although it was optional and not on by default, calling it “Secret Conversations.” 

They then began rolling out E2EE by default in Messenger in [2023](https://engineering.fb.com/2023/12/06/security/building-end-to-end-security-for-messenger/), among other security upgrades. 

Famously, Facebook [bought](https://about.fb.com/news/2014/02/facebook-to-acquire-whatsapp/) WhatsApp back in 2014\. They didn’t remove the E2EE; in fact, they [worked](https://signal.org/blog/whatsapp/) with Signal to bring the Signal Protocol to WhatsApp, with the work completing in [2016](https://signal.org/blog/whatsapp-complete/).

Despite their reputation, Meta seemed to be on the right track with supporting E2EE in its messengers. They published [multiple](https://engineering.fb.com/wp-content/uploads/2023/12/MessengerEnd-to-EndEncryptionOverview%5F12-6-2023.pdf) [whitepapers](https://engineering.fb.com/wp-content/uploads/2023/12/TheLabyrinthEncryptedMessageStorageProtocol%5F12-6-2023.pdf) on their E2EE protocols and bragged about the verifiability of their code via their [Code Verify](https://engineering.fb.com/2022/03/10/security/code-verify/) browser extension. They even helped design the [Messaging Layer Security (MLS)](https://datatracker.ietf.org/doc/rfc9420/) IETF protocol.

This move marks a sudden shift in their strategy with messaging. Instagram has made not public statement as to why they’re removing E2EE. It’s not clear whether Meta plans to remove E2EE in its other products in the future as well.

Meta already offers simple ways to [report](https://faq.whatsapp.com/414631957536067/?cms%5Fplatform=web) [messages](https://www.facebook.com/help/instagram/568100683269916/) on its platforms including [Instagram](https://help.instagram.com/753893408640265/?helpref=uf%5Fpermalink&parent%5Fcms%5Fid=3490194014566528), so the excuse that it’s needed to protect users doesn’t work.

They also offer easy [backup](https://help.instagram.com/766857281395358/?helpref=uf%5Fpermalink&parent%5Fcms%5Fid=3490194014566528) solutions for their platforms as well, so convenience isn‘t an issue either.

Whatever the reason, Meta is reversing a years-long trend of positive progress and I hope they revert it. There’s no excuse for a messenger not to be E2EE by default anymore, we have secure encryption, backup solutions, device sync, group chats. Encrypted messaging is just as convenient as unencrypted messaging these days.

A sudden reversal of a feature like this also erodes confidence that features you rely on will still be available in the future.

At least for now, there’s no indication that Meta intends to reverse E2EE in WhatsApp or Messenger, but we’ll need to keep a close watch.