iOS 26.5 introduces end-to-end encryption (E2EE) for RCS messages exchanged between iPhone and Android devices. The feature, now available in the public release, marks Apple’s first implementation of E2EE for cross-platform messaging outside iMessage.
Overview
Apple’s iOS 26.5 update enables E2EE for RCS conversations between iPhones and Android devices, a feature previously announced but delayed. The encryption is active by default but can be disabled in the Messages section of the Settings app. Encrypted messages are identified by a lock symbol in the conversation thread.
The feature is currently in beta and requires carrier support. Both sender and recipient must use carriers that support the latest RCS Universal Profile 3.0, which Apple co-developed with the GSM Association. The protocol is built on Messaging Layer Security (MLS), ensuring messages remain encrypted in transit and cannot be intercepted by third parties.
Requirements and rollout
- Carrier support: Only conversations between users on supported carriers will be encrypted.
- Device compatibility: The feature is included in iOS 26.5, iPadOS 26.5, macOS Tahoe 26.5, and watchOS 26.5.
- Rollout: The update is being released gradually and may not be available to all users immediately.
Additional RCS improvements
Alongside E2EE, iOS 26.5 adopts RCS Universal Profile 3.0, which introduces several cross-platform messaging features:
- Message editing and deletion: Users can edit or delete sent RCS messages.
- Tapback support: iPhone-style reaction emojis (Tapbacks) now work in Android-iPhone chats.
- Inline replies: Users can reply to specific messages within a conversation.
Tradeoffs
While E2EE improves security for cross-platform messaging, its adoption depends on carrier support. Users on unsupported networks will continue to send unencrypted RCS messages. Additionally, the feature remains in beta, meaning stability and compatibility may vary.
Bottom line
iOS 26.5’s E2EE for RCS messages brings iPhone-Android conversations closer to the security level of iMessage. However, its effectiveness relies on carrier adoption and may take time to become universally available. Users should check for the lock symbol in their Messages app to confirm encryption status.