iOS 26.5 adds end-to-end encrypted RCS so iPhones can exchange E2EE chats with Android

Texting between iPhones and Android phones just got a lot less embarrassing. Not because the bubbles changed color — they didn’t — but because the actual privacy model finally caught up. Apple and Google have started rolling out end-to-end encrypted RCS chats across their default messaging apps, which means ordinary cross-platform texts can now be protected in transit instead of sitting in the weird half-modern, half-legacy world that SMS left behind. Apple tied the iPhone side to iOS 26.5, and both companies say the rollout began on May 11 in beta. ### What actually changed? Before this, iPhone-to-Android RCS chats were better than SMS — higher-quality media, typing indicators, read receipts — but they still lacked interoperable end-to-end encryption. Google had encryption inside Google Messages for Android-to-Android chats for years, but that did not extend cleanly across platforms. The new piece is cross-platform E2EE in the default apps people already use. (apple.com) ### Why did this take so long? Because RCS was never one app. It’s a carrier-linked messaging standard with phone makers, carriers, and messaging clients all touching different parts of the stack. Apple and Google needed a common spec for encryption that worked across vendors instead of inside one company’s silo. That spec arrived with GSMA’s Universal Profile 3.0, published in March 2025, which added interoperable E2EE requirements for RCS messages, files, and other user content. (blog.google) ### What’s powering the encryption? The key technical change is MLS — Messaging Layer Security. Basically, it’s an open standard designed for secure group and direct messaging, and Apple and Google are using it as the shared cryptographic language for cross-platform RCS. That matters because it avoids the old problem where one app’s encryption worked only inside that app’s own walls. (gsma.com) ### Does everyone get it right now? No — and this is the catch. Apple says the rollout is in beta, it requires iPhones on iOS 26.5, Android phones on the latest Google Messages, and supported carriers. Google also says encryption will be enabled by default over time for new and existing RCS conversations, which is another way of saying this is a phased rollout, not a switch that flipped everywhere at once. (glitchwire.com) ### What does “supported carriers” really mean? It means carrier support still matters even though this feels like an app feature. If your carrier hasn’t implemented the needed RCS profile pieces, you may still get ordinary RCS without interoperable encryption — or fall back further depending on the setup. That’s why the user experience may be messy at first. Two people can both have modern phones and still not see the same protections immediately. (apple.com) ### Why is this a big deal if Signal exists? Because most people do not move their entire contact list onto Signal. Default texting still matters. It’s the thing your dentist uses, your family uses, and the thing that catches messages from people you didn’t plan to chat with. So when default texting gets real encryption across iPhone and Android, the baseline privacy expectation for mainstream messaging moves up — not just for power users. (apple.com) ### What still doesn’t change? This does not magically unify iMessage and Google Messages into one seamless system. Bubble politics remain. Carrier dependency remains. And because the rollout is beta and support is uneven, some chats will be protected before others. But the old excuse — that cross-platform default texting simply couldn’t be encrypted — is basically gone now. (eff.org) ### Bottom line? This is one of those updates that sounds small until you notice how many people it touches. Apple didn’t just add another Messages feature — it helped close the biggest privacy hole in everyday phone texting. The win is real. The rollout will be messy. But cross-platform texting just moved a lot closer to what users already assumed it should be. (apple.com)