iOS 26.5 Includes Beta Support for End-to-End Encrypted RCS Messaging

Apple Newsroom:

Starting today, end-to-end encrypted RCS messaging begins rolling out in beta for iPhone users running iOS 26.5 with supported carriers and Android users on the latest version of Google Messages. When RCS messages are end-to-end encrypted, they can’t be read while they’re sent between devices. Users will know that a conversation is end-to-end encrypted when they see a new lock icon in their RCS chats. Encryption is on by default and will be automatically enabled over time for new and existing RCS conversations.

I hope this leads to a future where all RCS messages are end-to-end encrypted, but I doubt it. Currently this E2EE RCS depends both on the carriers (of both parties) in a direct chat, and the software running on their devices. The carrier list is pretty broad, but as far as I can tell, it still doesn’t include Google’s own Google Fi.

But the indication for this is subtle. You have to read the small print metadata in each chat to see if it’s encrypted. The message text remains the same shade of green. If it’s a group chat and even one single member isn’t on a phone and carrier that supports E2EE RCS, the entire chat will not be encrypted.

With iMessage, all chats are always E2EE, and always have been. iMessage has been exclusively E2EE since it was created. With RCS you have to look in the metadata small print to check. That’s better than not supporting encryption at all, but my recommendation is to assume all RCS chats are not encrypted unless you double-check every time.

Other than bug fixes, encrypted RCS is the biggest new feature in iOS 26.5.

★ Monday, 11 May 2026