Encrypted RCS texting between iPhone and Android: requirements, rollout, and limits

The new step is standardized end-to-end encryption for RCS between iPhone and Android. Google and Apple describe it as a cross-industry effort to make RCS more secure and private across platforms, rather than a proprietary feature limited to one company’s ecosystem ^[3][5]. Google says eligible Android-iPhone RCS chats are secured by default as the feature rolls out ^[3].

Requirements: who gets encrypted iPhone-Android RCS

For users, the practical checklist is simple but strict:

Apple’s rollout is described as beta, even though support is included with the public iOS 26.5 release ^[5][8]. That means two users can both update their phones and still not see encrypted RCS immediately if their carrier or rollout status is not yet ready ^[4][8].

How the encryption works

The cross-platform encryption is tied to the GSMA RCS Universal Profile 3.0, which adds a standardized path for encrypted RCS rather than relying on a platform-specific approach ^[2][4]. That standard incorporates Messaging Layer Security, or MLS, an open protocol developed through the IETF and designed for secure messaging at scale ^[2].

In plain terms, eligible RCS messages between iPhone and Android are protected so they cannot be read by others while traveling between devices ^[4][5]. The goal is to make secure default texting possible without requiring users to move that specific conversation into a separate messaging app ^[2][3].

How to tell whether a chat is encrypted

Do not guess based only on the bubble color. The reliable signal is the encryption indicator.

On iPhone, reports say the Messages app can show an RCS encrypted label with a lock icon for eligible conversations ^[4]. On Android, Google Messages users should see the familiar lock icon for encrypted RCS chats ^[4]. If that indicator is missing, users should not assume the thread has end-to-end encryption.

Why it matters for cross-platform texting security

Before this rollout, Apple’s adoption of RCS improved iPhone-Android texting features, but cross-platform RCS encryption was still being tested separately ^[12][13]. The May 2026 rollout narrows that gap by bringing end-to-end encryption to the default RCS path between the two dominant mobile platforms when the requirements are met ^[3][5].

That matters because texting is often the default communication channel for ordinary users. A security improvement in the built-in Messages and Google Messages flow can protect more everyday conversations than a feature that requires every participant to install and use the same third-party app ^[2][3].

Still, the word “RCS” is doing important work here. Apple and Google’s announcements are about encrypted RCS messages, not a blanket upgrade that encrypts every legacy SMS or MMS exchange ^[3][5].

How the rollout developed

The rollout followed several steps:

• September 2024: Apple introduced RCS support with iOS 18, improving iPhone-Android messaging features such as typing indicators and read receipts ^[12].
• March 2025: The GSMA published RCS Universal Profile 3.0, which incorporated MLS as the standardized encryption mechanism for RCS ^[2].
• February 2026: Apple and Google began testing encrypted RCS between iPhone and Android in iOS 26.4 beta releases and Google Messages updates ^[11][12][13].
• May 11, 2026: Apple and Google announced the beta rollout for iPhone users on iOS 26.5 with supported carriers and Android users on the latest Google Messages ^[3][5].
• After launch: The rollout is gradual, with availability expected to expand over time rather than appear for every user immediately ^[4][8].

Limits and gotchas users should remember

The upgrade is real, but it has boundaries.

First, availability is phased. Apple calls the feature beta, and coverage depends on supported carriers ^[5][8]. 9to5Google reported that the rollout would take place over the coming months ^[4].

Second, Android support is specifically tied to the latest version of Google Messages in the rollout announcements ^[3][5]. Users on other Android messaging apps should not assume they are covered unless they see the encrypted RCS indicator.

Third, the protection applies to RCS conversations that meet the requirements. If a thread is not using encrypted RCS, the announcements do not indicate that the same end-to-end encryption applies ^[5].

Fourth, end-to-end encryption should not be confused with total anonymity. Apple’s published description says encrypted RCS messages can’t be read while they are sent between devices; it does not claim that every piece of messaging metadata is hidden ^[5].

What users should do now

Update the iPhone to iOS 26.5, update Google Messages on Android, and make sure RCS is active with a supported carrier ^[3][5][8]. Then check the conversation itself for the encrypted RCS label or lock icon before sending anything sensitive ^[4].

The bottom line: encrypted RCS between iPhone and Android is a major improvement for everyday cross-platform texting, but it is not universal yet. Treat the lock icon, not the promise of the rollout, as the sign that a particular conversation is protected.