Apple Expands Encrypted RCS Messaging to More Users in iOS 26.5
Apple has taken a major step toward securing cross-platform text messaging. After months of testing behind the scenes, the company is now rolling out end-to-end encrypted (E2EE) Rich Communication Services (RCS) to a larger audience with the release of iOS 26.5. This update means iPhone and Android users can finally enjoy the same level of privacy when texting each other that they've come to expect from iMessage or WhatsApp. Here's everything you need to know about this new feature, from how it works to when you can start using it.
What exactly is end-to-end encrypted RCS, and why does it matter?
End-to-end encrypted RCS (Rich Communication Services) is a modern messaging protocol that replaces the old SMS/MMS standard. With E2EE, messages are scrambled on the sender's device and can only be unscrambled on the intended receiver's device. This means not even Apple, Google, or your mobile carrier can read your conversations. For iPhone and Android users, this is a game-changer. Previously, texts between the two platforms were sent as SMS or MMS, which lack encryption and are vulnerable to interception. Now, with E2EE RCS, cross-platform chats get the same privacy protections that already exist within iMessage or Google Messages. It reduces the risk of snooping by hackers, marketers, or even government surveillance, giving users peace of mind that their conversations remain truly private.
Who can use the new encrypted RCS feature on iOS 26.5?
To send and receive encrypted RCS messages on an iPhone, you must be running iOS 26.5 and have a supported mobile carrier. On the Android side, the other party needs to be using the latest version of Google Messages. Apple hasn't published a full list of compatible carriers yet, but major providers in the US and Europe are expected to be included. Additionally, both users must have RCS enabled in their messaging settings. If either device falls back to SMS (for example, if the Android user doesn't have the latest Google Messages), the encryption will not work. So for now, the feature is limited to those who meet these criteria, but as more carriers and Android devices update, the coverage will expand.
How does the encryption work when messages travel between iPhone and Android?
The encryption process relies on cryptographic keys exchanged between the two devices at the start of a conversation. When you send an RCS message from your iPhone to an Android phone, the text is encrypted using a public key from the receiving device. It travels through your carrier's network and Google's RCS infrastructure while still scrambled. Only the Android device's private key can unlock it, and that key never leaves the phone. Apple and Google have collaborated to ensure the encryption protocols are interoperable, meaning the same standards apply whether you're on iOS or Android. This is different from end-to-end encryption in apps like Signal, where both users must be on the same platform. Here, the encryption works seamlessly across different operating systems, so you don't need a third-party app to get protected chats.
When will this feature be available to everyone?
Apple has started what it calls “larger public testing” with the iOS 26.5 release. This is a gradual rollout, meaning not every iPhone user will see it immediately. Typically, such features are enabled server-side or through carrier updates, so you may need to wait a few days or even weeks after updating to iOS 26.5. Google has already been testing E2EE RCS on Android for a while, so the Android side is ready. The next major milestone will be when all major carriers enable the necessary backend support. Apple hasn't announced a firm date for full availability, but based on previous rollouts, we can expect it to become widely accessible within a month or two of the iOS 26.5 release. Keep an eye on your messaging settings – you may see a notification or a new toggle for encrypted RCS.
Do I need to turn anything on to use encrypted RCS, or does it work automatically?
In most cases, encrypted RCS is enabled by default once your device meets the requirements. You don't need to install extra apps or manually turn on a switch – but it's good to verify. On your iPhone, go to Settings > Messages > RCS Messaging and make sure the toggle is green. On Android, open Google Messages, tap your profile picture, go to Messages settings > RCS chats, and confirm that “Turn on RCS chats” is selected. If both sides have these settings enabled and are using compatible carriers, the encryption will apply automatically to all RCS conversations. You'll know it's working if you see a lock icon or a note like “End-to-end encrypted” in the conversation. If a message shows as SMS instead, encryption is not available for that chat.
What does this update mean for the future of cross-platform messaging?
This update is a huge leap toward making cross-platform messaging as secure and feature-rich as platform-specific services. For years, iMessage kept iPhone users in a “blue bubble” while Android conversations remained in green bubbles with fewer features and no encryption. By standardizing encrypted RCS, Apple and Google are effectively blurring that line. We can expect other advanced RCS features – like read receipts, typing indicators, and high-resolution media sharing – to also become encrypted over time. This move puts pressure on carriers to upgrade their networks fully, and it may reduce reliance on third-party messaging apps. In the long term, encrypted RCS could become the universal standard for secure texting, much like how HTTPS became standard for web browsing. It's a win for user privacy and a more connected digital world.