Apple and Google begin testing end-to-end encrypted RCS texts between iPhone and Android

Apple and Google are finally stress-testing the feature iPhone-and-Android households have been waiting for: end-to-end encryption for RCS texts that cross the platform divide.

In the latest betas, iOS 26.4 beta 2 on iPhone and a recent Google Messages beta on Android, some users can now send RCS messages that are encrypted from one device to the other. When it works, a lock icon appears in the conversation, signaling the messages are protected in transit.

This isn’t a nerdy footnote. RCS already brought iPhone-Android texting into the modern era with read receipts, typing indicators, and better-quality photos and videos. But without end-to-end encryption, it still lagged behind what Americans now expect from secure messaging.

What’s actually new here, and why it matters

RCS (Rich Communication Services) is the industry-backed upgrade to SMS, the old-school texting standard. Think of it as “texting, but with the features you’re used to in chat apps.”

Apple added RCS support to iPhones in 2024, easing years of friction between iMessage and Android texting. But the biggest gap remained privacy: iMessage chats between iPhones can be end-to-end encrypted, while iPhone-to-Android RCS chats generally weren’t, at least not in a way that worked reliably across both ecosystems.

This beta aims to close that gap by letting iPhone and Android negotiate encryption together, then clearly show users when it’s active.

How it works on iPhone: iOS 26.4 beta 2 adds an encryption toggle

On Apple’s side, the test lives iniOS 26.4 beta 2. In Settings under Messages and the RCS menu, Apple includes a plainly labeled option:“End-to-End Encryption (Beta)”.

In some cases, the setting appears to be enabled by default after updating, an unusually aggressive move for a security feature still in testing.

Users can confirm encryption inside the Messages app itself. RCS chats still show up as green bubbles (Apple’s long-running visual cue that a message isn’t iMessage), but the conversation can display “Text Message · RCS” alongside a lock icon when encryption is active.

On Android, Google Messages beta is the gateway

On Android, the setup is simpler: install the latestGoogle Messagesbeta and let the app handle the encryption “handshake” when it detects a compatible iPhone.

When the negotiation succeeds, Android users see the same kind of lock icon they’re used to in encrypted Google Messages chats.

The catch is the same one that haunts every messaging beta: instability. If messages lag, duplicate, or fail to deliver, it may not be your carrier or your signal, it may be the encryption test misfiring.

The tech behind it: a GSMA standard and a protocol called MLS

This test is built on the GSMA’sRCS Universal Profile 3.0, the telecom industry’s attempt to keep RCS from splintering into incompatible versions depending on which company built what.

For encryption, the profile relies onMessaging Layer Security (MLS), a standardized protocol designed to secure modern messaging at scale.

For everyday users, the promise is straightforward: if the chat is marked encrypted, the content shouldn’t be readable while it travels between devices. That’s the missing piece for iPhone-to-Android RCS, especially for people sharing family photos, addresses, or sensitive details over plain old texting.

The fine print: carriers, devices, and beta bugs can break the experience

Apple says the feature won’t be available on every device or every carrier, at least during testing. That matters because RCS itself can depend on carrier support and network configuration, even when the phone and app are up to date.

That means two people can be running the right iOS beta and still not see identical behavior, because the network layer underneath them isn’t the same.

There’s also the risk of silent fallback. If encryption negotiation fails, a conversation may revert to non-encrypted RCS behavior, or fail to label the status correctly. The lock icon is supposed to make that visible, but the whole point of the beta is to find out where the edges crack.

Some industry chatter suggests the test may not be available everywhere globally, with a few countries potentially excluded. Neither Apple nor Google has publicly locked down a definitive country-by-country list in release notes.

What this changes for Americans who text across the “green bubble” line

If Apple and Google can make this work reliably, and ship it turned on by default, it would be a major shift in how secure “normal texting” feels in the U.S., where iPhone dominance and iMessage culture have long shaped social and group-chat dynamics.

End-to-end encrypted RCS won’t erase the iMessage-vs-Android divide. Green bubbles will still be green, and iMessage-exclusive features won’t magically appear on Android. But it would remove one of the strongest technical arguments for staying inside a single ecosystem: that cross-platform texting can’t meet modern privacy expectations.

The next real test isn’t whether the lock icon shows up in a beta. It’s whether Apple and Google can deliver encryption that’s stable across carriers, devices, and real-world group chats, without users having to think about it at all.