Apple has officially launched end-to-end encrypted RCS messaging, built on an open industry standard and designed to work across both iOS and Android without requiring a third-party app.

Apple first added RCS support to the iPhone with iOS 18.1, bringing typing indicators, read receipts, and higher-resolution media to iPhone-Android conversations. But encryption was conspicuously absent. The reason was the absence of an agreed-upon cross-platform standard.

That standard arrived in March 2025, when the GSMA published RCS Universal Profile 3.0, incorporating Messaging Layer Security (MLS), an open protocol developed by the IETF. Apple and Google co-developed the MLS specification, ensuring that a single encryption standard could work across both platforms without either company controlling it.

Apple began testing E2EE for RCS during the iOS 26.4 beta cycle in February 2026, but pulled it back before the stable release. It returned in the iOS 26.5 beta and remained throughout testing, a signal that Apple was confident enough to ship it publicly, even under a beta label.

The technical implementation is straightforward in concept but demanding in practice. When both an iPhone user on iOS 26.5 and an Android user on a recent version of Google Messages are connected to carriers that have deployed RCS Universal Profile 3.0, the Messages app automatically negotiates end-to-end encryption using MLS. Neither user needs to do anything.

The feature is enabled by default and can be verified or toggled by navigating to Settings → Apps → Messages → RCS Messaging → End-to-End Encryption (Beta). If the toggle doesn't appear, it means your carrier hasn't activated support yet.

Apple's beta label is deliberate and specific: the underlying technology is tested and stable, but the rollout is incomplete. Carrier partnerships are still being activated, and Apple is staging the expansion over the coming months. The label signals that coverage is not yet universal, not that the feature is experimental.

For encryption to activate, both users must be on carriers that support RCS Universal Profile 3.0, on both the iPhone and Android sides. A single unsupported carrier in a conversation is enough to leave the entire thread unencrypted. This applies to group chats as well: one participant on an unsupported carrier may affect the encryption status of the whole thread.

It's worth being clear about what this update does and doesn't do. RCS encryption on iOS 26.5 is not the same as iMessage. iMessage has supported end-to-end encryption since 2011 and runs entirely on Apple's servers — encryption is consistent because carrier infrastructure is never involved.

Encrypted RCS is consistent only when every carrier in a given conversation has activated support. That dependency on telecom infrastructure means coverage will remain uneven for months as the rollout proceeds. For sensitive conversations where carrier support is uncertain, Signal or WhatsApp remain reliable alternatives — neither depends on carrier adoption.

Remaining RCS features on the roadmap, including message editing, undo send, higher image quality under Universal Profile 3.1, and cross-platform video calls under UP 4.0, are not included in this update. Those improvements are expected in future iOS releases, possibly alongside iOS 27, which Apple is expected to preview at WWDC 2026 on June 8.

Cross-platform encrypted messaging has long been a gap that regulators, researchers, and privacy advocates flagged as a systemic weakness. WhatsApp and Google Messages had long offered E2EE within their own ecosystems. iMessage had it for iPhone-to-iPhone conversations. But the moment an iPhone user texted an Android user over RCS, that protection vanished.

iOS 26.5 closes that gap, not through a proprietary solution, but through an open standard that required coordinated action from Apple, Google, the GSMA, and dozens of carriers worldwide. The rollout is staged, the beta label is honest, and the carrier dependency is real. But the foundation is now in place.