iOS 26.5 Turns On RCS End-to-End Encryption by Default
With the release of iOS 26.5, Apple has finally enabled RCS end-to-end encryption for messages exchanged between iPhones and Android devices. Until now, any cross-platform chat typically fell back to SMS, which lacks modern features and offers minimal protection against interception. Now, when Apple’s Messages app talks to Google Messages using RCS, the content of those chats is protected so only the sender and recipient can read it. This upgrade relies on the GSMA’s RCS Universal Profile 3.0 and the Messaging Layer Security protocol, the same standard Google already uses. Crucially, users don’t have to toggle anything on: once both sides have compatible software and a supporting carrier, encryption becomes the default for these richer chats. It marks a major shift in iPhone Android messaging security, moving basic texting closer to the privacy people already expect from dedicated encrypted apps.
Closing the Long-Standing iPhone–Android Security Disparity
For years, iPhone users enjoyed end-to-end encrypted iMessage conversations with other iPhones, while chats with Android contacts dropped to unencrypted SMS. Android users, meanwhile, gained RCS end-to-end encryption in Google Messages, but only when talking to other Android phones. The result was a fragmented landscape: secure blue-bubble chats on one side, fully encrypted Android-only RCS on the other, and a vulnerable gap in between. Third-party workarounds tried to bridge this divide, but several efforts were withdrawn after encryption and privacy concerns. Apple’s gradual RCS rollout started in 2024 without encryption, so cross-platform texts still lagged behind. With iOS 26.5, that gap finally narrows. Both major ecosystems now support cross-platform message encryption in their default apps, meaning everyday mixed-device conversations can gain strong protection without forcing people to move to separate services like WhatsApp or Signal for basic texting.
How to Get Encrypted RCS Chats Working on Your Phone
Most users won’t have to change any settings to benefit from iOS 26.5 encrypted texts, but a few conditions must be met. On the iPhone side, you need to install iOS 26.5, which adds RCS end-to-end encryption to the Messages app. On Android, you’ll need the latest version of Google Messages with RCS enabled. Your mobile carrier must also support RCS and its encrypted mode for cross-platform conversations. Because the rollout is phased and carrier-dependent, RCS encryption might not appear immediately. When it is active, Apple shows a lock icon and an “Encrypted” label in eligible RCS chat threads. RCS will switch on automatically for supported carriers and will be applied to existing and new conversations over time. Until you see that lock and label, assume the chat is not protected by cross-platform message encryption and avoid sharing sensitive details there.
What RCS Encryption Protects—And What It Doesn’t
RCS end-to-end encryption protects the contents of your messages in transit: texts, images, and other media sent over RCS between iPhone and Android devices cannot be read by Apple, Google, or carriers. This is a substantial privacy improvement for mixed-device conversations and aligns default texting with modern security expectations. However, some data remains outside this encrypted envelope. Messaging metadata—such as who you talk to and when—may still be collected or retained. Backups are another important caveat. On iOS, chats may be stored unencrypted in the cloud unless you enable features like Advanced Data Protection, while Google Messages currently encrypts message text but not media in backups. For highly sensitive conversations, dedicated apps such as Signal still offer stronger, more comprehensive protections. Still, for everyday iPhone Android messaging security, RCS encryption is a major and welcome leap forward.