End-to-end encrypted RCS chats arrive between iPhone and Android in iOS 26.5 rollout

Texting between iPhone and Android has had a weird split for years. iMessage chats were encrypted. SMS wasn’t. RCS made cross-platform texting look and feel more modern, but the privacy story still lagged. That changed on May 11, when Apple said end-to-end encrypted RCS messaging started rolling out in beta for iPhone users on iOS 26.5 and Android users on the latest Google Messages. ### What actually arrived? The new thing is simple to describe — some iPhone-to-Android RCS chats can now be end-to-end encrypted, meaning the message content can’t be read in transit between devices. Apple says the rollout starts in beta for iPhones on iOS 26.5, and the Android side needs the latest version of Google Messages. This is not a blanket switch for every phone on day one. Carrier support matters. (apple.com) ### Why is this different from regular RCS? RCS already fixed a bunch of old SMS annoyances. You got typing indicators, better media sharing, read receipts, and group chat features. But standard RCS between platforms did not automatically mean the same privacy level people associate with Signal, WhatsApp, or iMessage. The gap was that the transport got smarter, while the encryption story across ecosystems stayed incomplete. (apple.com) ### How will people know it’s working? Apple says there’s a new lock icon in RCS chats when the conversation is end-to-end encrypted. That matters because RCS status can be messy — sometimes a thread falls back to SMS or MMS, sometimes a carrier doesn’t support the needed features, sometimes activation takes a while. Apple’s support pages also note there can be a delay of a few hours before RCS activates. (support.apple.com) ### Why did this take so long? Because cross-platform encryption is the hard version of messaging. Apple and Google had to align with the broader mobile industry on a shared spec instead of each company just doing its own thing inside its own app. The GSMA’s RCS encryption spec now uses Messaging Layer Security, or MLS, which is designed for secure one-to-one and group messaging. Basically, the industry finally had a common blueprint both sides could implement. (apple.com) ### What’s the catch? The catch is availability. Apple is calling this a beta rollout, not a universally live feature. You need iOS 26.5 on the iPhone side, the latest Google Messages on the Android side, and a carrier that supports end-to-end encrypted RCS. So the headline is real, but the experience will land unevenly at first — more like a phased network feature than a clean app update. (gsma.com) ### Why bundle this with iOS 26.5? Because iOS 26.5 is also a security release. Apple published a dedicated security advisory for iOS 26.5 and iPadOS 26.5 on May 11, 2026, covering a long list of fixes across system components. So even if someone doesn’t care about cross-platform texting, this is still the kind of update you install promptly. The encrypted RCS rollout is the visible user feature, but the security patches may matter more day to day. (apple.com) ### Why does this matter beyond Apple and Google? Because it chips away at the old idea that secure messaging only works cleanly inside one company’s walled garden. If this rollout sticks, iPhone and Android users get a more private default texting layer without having to persuade friends and family to move to a separate app. That doesn’t erase the platform divide, but it does make the baseline experience a lot less broken. (support.apple.com) ### Bottom line This is a small-looking update with a big practical effect. iPhone and Android users have been able to text each other with richer features for a while, but now those chats can finally get real end-to-end encryption too — at least where carriers and apps support the beta rollout. That’s the part worth remembering. (apple.com)