Apple on Monday shipped iOS 26.5 with a beta feature that brings end-to-end encryption (E2EE) to Rich Communication Services (RCS), marking a deliberate push to move cross‑carrier mobile messaging away from legacy SMS toward an encrypted, internet‑based alternative. The capability is rolling out to iPhone users running iOS 26.5 with supported carriers and to Android users running the latest version of Google Messages, and — by design — the encryption is turned on by default for both new and existing conversations across the two platforms.
Apple's iOS 26.5: what the rollout includes
The release makes E2EE for RCS available in beta on iOS 26.5. Apple’s announcement emphasizes that the feature applies when iPhone users are connected to carriers that support RCS and when the recipient is using Google Messages on Android up to date with the new capability. Apple notes the user-visible cue for encrypted conversations: a new lock icon that will appear in RCS chats.
Apple first trialed end‑to‑end encryption for RCS in iOS and iPadOS 26.4 Beta, where testing was initially limited to conversations between Apple devices. The iOS 26.5 release expands that scope to enable cross‑platform E2EE between iPhone and Android, subject to carrier and app support.
RCS and the Universal Profile: a richer SMS replacement
Rich Communication Services is a modern, internet‑based messaging protocol designed as a successor to traditional SMS. According to the announcement, RCS supports higher‑resolution photos and videos, typing indicators and read receipts — features typically associated with standalone instant messaging apps. Those capabilities are implemented on a common technical foundation known as the RCS Universal Profile, the industry specification that underpins the protocol's interoperability and feature set.
GSMA, Apple and Google: a coordinated, standards‑based effort
The move to enable E2EE for RCS is explicitly framed as a cross‑industry effort. In early 2025 the GSM Association (GSMA) announced support for end‑to‑end encryption to safeguard messages sent using the RCS protocol. Alex Sinclair, chief technology officer at GSMA, described the current progress as "the result of close, cross‑industry collaboration between the GSMA RCS Working Group, including Apple, Google, and the wider mobile ecosystem," adding that "the new secure services are being delivered on an open, globally recognised foundation."
Google, for its part, has said that Google Messages users on Android will see a padlock icon when a cross‑platform conversation is end‑to‑end encrypted, providing an immediate visual signal similar to Apple’s lock icon.
Visual indicators and default behavior: lock, padlock, and defaults
Both platform vendors have committed to visible indicators that a conversation is fully encrypted in transit: Apple will display a lock icon in RCS chats, while Google will display a padlock. The feature is enabled by default for both new and existing conversations on supported devices and apps, a design choice that removes the need for users to opt in to encrypted RCS once the software and carrier conditions are met.
What this means for iPhone users, Android users, and carriers
- iPhone users running iOS 26.5: will receive RCS E2EE in beta when their carrier supports the protocol; encrypted conversations will display a lock icon and apply automatically to both new and preexisting chats that meet the technical conditions.
- Android users on Google Messages: must run the latest version of Google Messages to participate in cross‑platform E2EE and will see a padlock icon indicating encryption; the feature hinges on both app version and carrier support.
- Carriers: must support RCS and the Universal Profile to enable the encrypted sessions described; the rollout depends on carrier adoption alongside device and app updates.
The iOS 26.5 beta release brings a technically specific but broadly consequential change: encrypted, cross‑platform messaging delivered by vendors and standards bodies working together, with user safeguards built into the client experience. The choice to enable E2EE by default and to use clear visual signals — distinct lock and padlock icons — reduces friction for end users, while placing the practical burden for interoperability on carriers and client software updates. For consumers the visible change will be simple: different icons and an assurance that, as Apple put it, messages "can't be read while they're sent between devices." For the ecosystem, the work now shifts to carrier rollouts and app updates to turn a standards pledge into day‑to‑day reality.
