iOS 26.5 Brings End-to-End Encrypted RCS Messaging

Apple has confirmed that iOS 26.5 will feature end-to-end encryption for RCS messages sent between iPhones and Android devices. This long-awaited security upgrade could roll out to the public as soon as next week.

What’s Actually Changing

Currently, when an iPhone user texts an Android user via RCS (Rich Communication Services, the modern messaging standard replacing SMS for most Android phones), those messages lack end-to-end encryption. This means your carrier or anyone intercepting the message could potentially read it. With iOS 26.5, Apple is addressing this issue.

End-to-end encryption, or E2EE, acts like a locked box, with only the sender and recipient having the keys. Even Apple and Google can’t access it. iPhone users already enjoy this security when messaging other iPhones via iMessage, indicated by the blue bubble. Android-to-Android messaging apps like Google Messages also provide E2EE for RCS conversations. The missing piece has always been cross-platform messaging, and iOS 26.5 finally adds that.

Apple confirmed this feature in the official iOS 26.5 release notes, making it clear that this isn’t just speculation.

Why This Took So Long

Originally, RCS as a standard didn’t include encryption. Apple introduced RCS support to the iPhone in iOS 18 back in 2024, but implementing cross-platform encryption required a new technical specification known as the GSMA’s E2EE standard for RCS, which both Apple and Google had to agree to adopt. Imagine two different banks finally settling on the same vault lock design so their customers can securely share transfers.

Apple confirmed to MacRumors that iOS 26.5 indeed delivers E2EE for RCS messages between iPhones and Android devices, as stated in the release notes published on May 4, 2026.

What About the Green Bubbles?

This is the question on everyone’s mind. No, your texts to Android users won’t turn blue. Apple has maintained the distinction between green and blue bubbles specifically for iMessage, not based on encryption status. So visually, things will stay the same. However, your conversation will be protected just like an iMessage.

There’s one caveat: Both users need to have updated software. The iPhone user must be on iOS 26.5, and the Android user needs a version of Google Messages (or another RCS app) that supports the same encryption standard. For most Android users with relatively recent software, that should already be in place.

What This Means for Everyday Users

If you’ve ever been advised to “just use Signal” or “just use WhatsApp” for secure messaging with Android users, that advice is about to become less necessary. The default texting experience between iPhones and Android phones will get a solid privacy upgrade without requiring anyone to download a third-party app.

This is particularly important in real-world situations, like texting your doctor, sharing sensitive personal information, or simply wanting to keep your conversations away from your carrier’s prying eyes. It’s a basic level of protection that many people expect, and now it will finally be there.

Businesses and organizations that have avoided certain communication tools due to compliance concerns may also benefit. Encrypted RCS could pave the way for broader use of native messaging in regulated sectors.

Community Reaction

“Finally. I’ve been explaining to my family for years why I use Signal for anything sensitive. Maybe now I can just tell them to update their iPhone and we’re good.”

— u/packet_ranger, r/apple

“Android had this for a while but it only worked Android-to-Android. Cross-platform E2EE is the actual win here. Both sides finally agreed on the same standard. Huge deal that nobody is talking about enough.”

— Comment on MacRumors YouTube coverage

What To Watch

• Next week: Apple is set to release iOS 26.5 to the public. Check Settings > General > Software Update to grab it when it goes live.
• Google Messages compatibility: Keep an eye out for Google to confirm which version of Messages supports the GSMA E2EE standard on the Android side, and if any older Android versions will be left out.
• Carrier responses: Some carriers have historically lagged in upgrading their RCS infrastructure. If encrypted RCS doesn’t work on certain networks at launch, that’s something to watch.
• What Apple does with the bubble colors: There’s been ongoing pressure, including regulatory interest in Europe, for Apple to enhance iMessage interoperability. Whether encrypted RCS influences that discussion will be interesting to see in the coming months.

Sources: CNET | MacRumors | MacRumors RCS Guide