iOS 26.5 adds RCS end-to-end

Texting is finally getting one of the obvious missing pieces. Apple and Google have started rolling out end-to-end encrypted RCS chats between iPhone and Android users, with Apple putting the feature into iOS 26.5 and Google enabling it in the latest Google Messages app. That matters because RCS was supposed to be the modern replacement for SMS, but cross-platform privacy still lagged behind apps like iMessage and Signal. Now the default phone-texting layer is getting a lot closer. ### What actually changed? Starting May 11, Apple says iPhone users on iOS 26.5 can begin using end-to-end encrypted RCS in beta, as long as their carrier supports it and the Android side is on the latest Google Messages. Google announced the same rollout from its side the same day. This is not just “RCS is on now” — Apple already added basic RCS support earlier. The new part is encryption for the messages traveling between the two platforms. (apple.com) ### Why is that a big deal? Because plain RCS fixed features, not privacy. It gave iPhone-to-Android chats better media sharing, typing indicators, read receipts, and higher-quality group messaging than SMS. But carriers or intermediaries could still potentially access message contents in transit. End-to-end encryption changes that — the messages are scrambled on the sender’s device and only unscrambled on the recipient’s device. Apple says users will see a lock icon when an RCS conversation is encrypted. (apple.com) ### What is RCS, basically? RCS stands for Rich Communication Services. Think of it as the telecom industry’s attempt to replace SMS with something that behaves more like a modern chat app. The catch is that RCS has always been messy because carriers, phone makers, and app makers all had to line up. Google pushed it hard on Android. Apple resisted for years, then added baseline RCS support later — but without the same privacy level people were used to inside iMessage. (apple.com) ### How are Apple and Google making it work? They are using a GSMA standard for RCS end-to-end encryption built on MLS — Messaging Layer Security. That matters because this is not Google’s old proprietary encryption layer inside Google Messages. It is a cross-industry spec meant to let different clients and networks interoperate securely. Apple says both companies helped drive that effort, and the GSMA specification spells out MLS as the foundation. (gsma.com) ### Why is it still called beta? Because rollout is conditional. Apple is explicit that it starts with iPhones on iOS 26.5, Android phones on the latest Google Messages, and supported carriers. So even after you update, you may not see it immediately in every chat. Apple’s developer documentation also shows that apps and services can check whether an RCS service supports end-to-end encryption before sending protected content. In other words, the plumbing is there, but the network side still has to cooperate. (apple.com) ### Wasn’t this already in beta before? Sort of. Apple had shown end-to-end encrypted RCS in earlier iOS 26.4 and 26.5 beta builds, but it did not make the final 26.4 release. That made the feature feel half-announced for a while. The stable iOS 26.5 release on May 11 is the first time Apple has publicly tied the feature to a shipping version and a same-day rollout with Google. (apple.com) ### What does this not fix? It does not make iMessage and Google Messages identical. Blue bubbles and green bubbles still exist. Carrier support still matters. And “beta” means edge cases are still possible. But the biggest practical hole — that normal iPhone-to-Android texting was modern in features but weaker in privacy — is finally getting patched. That is the real shift here. (9to5mac.com) ### Bottom line This is less flashy than a new app, but more important. Apple and Google just made the default texting path between their phones meaningfully more private — and they did it with a shared standard instead of a one-off workaround. (apple.com)