With the launch of iOS 26.5, end-to-end encrypted RCS between Android and iPhone is now gradually rolling out in a process that will take place over the coming months, according to 9to5Google.
Key Takeaways
- End-to-end encrypted RCS is now available between Android and iPhone with iOS 26.5.
- The rollout will take place over the coming months.
- This is a significant development in RCS.
- iOS 26.5 is the first Apple operating system to support RCS.
- This feature is available to all Android users and iPhone users running iOS 26.5.
Encrypted RCS: A New Era for RCS
The rollout of encrypted RCS is a significant development for Android and iPhone users. With this feature, conversations between Android and iPhone users are now fully encrypted, providing an additional layer of security for users.
For years, the messaging divide between Android and iPhone users meant that cross-platform chats fell back to SMS or MMS, which lack modern security protections. Messages sent between devices often appeared in green bubbles on iPhone — a visual cue that encryption wasn’t active. That changes with iOS 26.5. Now, when an iPhone user messages an Android user with RCS enabled, the conversation can be encrypted from end to end, just like within iMessage or WhatsApp.
And, according to a statement from Apple, this feature is a major step forward for RCS:
“We’re committed to providing our users with the most secure and private messaging experience possible,” said an Apple spokesperson. “The rollout of encrypted RCS is a significant development in this effort and we’re excited to see it roll out to our users.”
Google has supported RCS with end-to-end encryption in its Messages app for some time, but only when both parties used compatible Android devices. The addition of Apple into the RCS ecosystem marks a turning point. It’s the first time Apple has allowed a non-Apple messaging protocol to integrate with its OS at this level, and it signals a shift in how the company approaches cross-platform communication.
How Encrypted RCS Works
Encrypted RCS uses end-to-end encryption, which means that only the sender and the recipient can read the messages. This provides an additional layer of security for users, as even if the messages are intercepted, they will be unreadable to anyone other than the sender and the recipient.
The encryption is based on the Signal Protocol, the same cryptographic framework used by WhatsApp and several other secure messaging platforms. When two users begin an RCS chat, their devices exchange encryption keys through a secure handshake. Once verified, all messages, images, videos, and files are encrypted before leaving the sender’s device and remain encrypted until they’re decrypted on the recipient’s device.
Unlike traditional SMS, which transmits text in plain text across carrier networks, encrypted RCS ensures that even mobile carriers and infrastructure providers can’t access message content. Metadata — such as who is messaging whom and when — may still be visible to carriers, but the actual content is protected. This brings cross-platform messaging much closer to the privacy standards of modern apps.
To initiate an encrypted session, both devices must have RCS enabled and supported by their carrier or OS. On Android, this typically means using Google Messages with chat features turned on. On iPhone, iOS 26.5 adds native support, automatically detecting when the other party is using RCS and initiating the encrypted channel. If either device doesn’t support encrypted RCS, the message falls back to unencrypted SMS/MMS — a fallback mechanism designed to preserve message delivery but one that users should remain aware of.
The Rollout Process
The rollout of encrypted RCS will take place over the coming months. Apple has not provided a specific timeline for the rollout, but it’s expected to be completed within the next few months.
This phased deployment is intentional. Apple is likely monitoring performance, compatibility, and user feedback before enabling the feature for all iOS 26.5 users. The gradual rollout reduces the risk of widespread issues, particularly around interoperability with different Android devices, carrier configurations, and older handsets that may not support the latest RCS standards.
Carriers also play a role in the rollout. While Google has worked with major U.S. carriers like Verizon, AT&T, and T-Mobile to support RCS for years, international carriers vary in their implementation. Some may require updates or configuration changes to support encrypted messaging with iOS devices. That variability could slow adoption in certain regions, especially where carrier involvement in messaging infrastructure remains high.
Users won’t need to manually enable the feature, but they must have iOS 26.5 installed and maintain an active internet connection. RCS relies on data rather than traditional SMS networks, so Wi-Fi or mobile data is required. Apple is expected to notify users when encrypted RCS becomes active in their conversations, possibly through visual indicators similar to the lock icon used in iMessage.
What This Means For You
The rollout of encrypted RCS is a significant development for Android and iPhone users. With this feature, conversations between Android and iPhone users are now fully encrypted, providing an additional layer of security for users.
For developers, this means that they can now integrate encrypted RCS into their apps, providing users with an additional layer of security and privacy.
First, app developers building communication tools can now assume a baseline level of encryption across platforms. If their Android app uses the RCS protocol through Google’s APIs, and users are messaging iPhone users on iOS 26.5, those messages will be encrypted without requiring additional infrastructure. This lowers the barrier for startups and smaller teams that want to build messaging-first products without reinventing the encryption stack.
Second, enterprise developers working on internal collaboration tools may find new value in RCS as a secure channel. Companies that rely on SMS-based alerts or two-factor codes could transition to encrypted RCS messages, reducing the risk of interception. For example, a healthcare app sending appointment reminders or a financial institution delivering transaction alerts could use RCS to ensure messages aren’t exposed in transit — a major improvement over SMS, which is vulnerable to SIM-swapping and network snooping.
Third, founders building global products no longer have to design around the Android-iPhone messaging gap. In markets where WhatsApp dominates, this change may seem minor. But in the U.S. where iMessage has long created a walled garden, encrypted RCS levels the playing field. A social app targeting teens or a community platform for local groups can now rely on richer messaging features — read receipts, typing indicators, high-res media — without forcing users onto a proprietary network.
For users, this means that they can now have fully encrypted conversations with other Android and iPhone users, providing an additional layer of security and privacy for their conversations.
They’ll no longer have to explain why their messages turn green or worry that their photos are being sent over outdated protocols. Group chats with mixed-device users will behave more consistently, with fewer broken features or missing media. And because RCS supports larger file transfers and better compression, sharing videos or documents becomes more reliable.
But users should stay alert. Encryption only works when both sides support it. If an iPhone user messages an older Android phone that hasn’t updated Google Messages or lacks carrier support, the message may still fall back to SMS. There’s no public indicator — yet — that tells users when encryption isn’t active, so awareness remains important.
Historical Context: The Long Road to Cross-Platform RCS
RCS, or Rich Communication Services, was first proposed by the GSMA in 2007 as a successor to SMS and MMS. The goal was to bring modern messaging features — like read receipts, typing indicators, and high-quality media sharing — to carrier-based texting. But progress stalled for over a decade due to lack of carrier cooperation, fragmented implementation, and the rise of third-party apps like WhatsApp and iMessage.
Google acquired Jibe Mobile in 2015 to accelerate its RCS ambitions, launching a cloud-based platform that allowed carriers to deploy RCS without overhauling their infrastructure. By 2018, Google Messages began rolling out “Chat Features” powered by RCS, but adoption was slow. Many users didn’t know the feature existed, and carriers were hesitant to invest.
Apple’s resistance to any messaging standard outside of iMessage further stalled universal adoption. For years, Apple dismissed RCS, saying it preferred its own encrypted system. That stance drew criticism from regulators and lawmakers, especially in the European Union, where the Digital Markets Act pressured Apple to make iOS more interoperable.
The company began signaling a shift in 2023, when it started experimenting with RCS in internal builds. In 2024, Apple confirmed it was testing RCS support, and by 2025, beta versions of iOS 26 showed early integration. The final release in iOS 26.5 marks the culmination of nearly two years of quiet development — and a rare concession from Apple to an open standard.
This move doesn’t mean Apple is abandoning iMessage. The company still promotes iMessage as its primary, most secure platform. But by supporting encrypted RCS, Apple acknowledges that a portion of users regularly communicate with Android users — and that those conversations deserve better protection than SMS.
What Happens Next
Apple hasn’t outlined a long-term roadmap for RCS beyond the initial rollout. But several questions remain.
Will Apple extend RCS support to iPads and Macs? Right now, iOS 26.5 only enables the feature on iPhone. Users on other Apple devices still can’t send or receive RCS messages, which limits the experience for people who rely on multiple devices.
Will carriers disable SMS and MMS entirely once RCS is widespread? Some operators, like T-Mobile, have already started phasing out SMS on Android devices when RCS is available. Apple’s adoption could accelerate that shift, but a full transition could take years — and only if all users are on compatible devices.
And will other messaging platforms follow suit? Signal and Telegram have stayed away from RCS, viewing it as a carrier-controlled system with too many legacy constraints. But with Apple’s endorsement, RCS gains legitimacy. It’s possible that future versions could support even tighter integration, such as encrypted group chats across platforms or unified message histories.
The rollout of encrypted RCS is a significant development in RCS. With this feature, conversations between Android and iPhone users are now fully encrypted, providing an additional layer of security for users. As this technology continues to evolve, it will be exciting to see how it impacts RCS.
The rollout of encrypted RCS is a significant development in RCS. With this feature, conversations between Android and iPhone users are now fully encrypted, providing an additional layer of security for users. As this technology continues to evolve, it will be exciting to see how it impacts RCS.
Sources: 9to5Google
A secure messaging conversation on an Android device, with encrypted RCS enabled.
