Apple has officially confirmed that the upcoming iOS 26.5 update will bring end-to-end encryption (E2EE) to Rich Communication Services (RCS) messaging within the Messages app. The confirmation came via the release notes for iOS 26.5 Release Candidate (RC), which is now available to developers and public beta testers. This marks a major step forward in cross-platform messaging security, as RCS has long lacked the robust encryption that Apple’s iMessage provides.
What is RCS and Why It Matters
RCS, or Rich Communication Services, is the modern industry standard for SMS replacement. It enables features like read receipts, typing indicators, high-resolution media sharing, and group chats, which have been standard on iMessage for years. For iPhone users, RCS makes conversations with Android contacts significantly richer than the old green bubble SMS experience. However, until now, one critical feature was missing: end-to-end encryption. While iMessage encrypts all messages end-to-end by default, RCS typically only encrypts messages in transit between the carrier and the user, not between the two endpoints. This left iPhone-to-Android chats vulnerable to interception by carriers or malicious actors.
Apple’s adoption of RCS in iOS 26 earlier this year was a landmark move, pressured by regulatory requirements and user demand. With iOS 26.5, Apple addresses the privacy gap by adding its own implementation of E2EE for RCS. The company has worked closely with the GSMA (the governing body for RCS) and major carriers to ensure the encryption protocol is interoperable and secure. The feature is currently labeled as a beta, meaning it may not be fully stable or available to all users immediately. Apple has stated that it will roll out over time and initially require compatible carriers.
History of RCS on iPhone
Apple’s journey with RCS has been cautious. For years, the company resisted adopting RCS, preferring to keep iMessage as the exclusive messaging service for Apple devices. This created the well-known “green bubble” stigma, where Android users experienced a degraded chat experience. In late 2023, Apple announced it would support RCS in 2024, following pressure from the European Union under the Digital Markets Act (DMA) and from competitors like Google. The initial implementation in iOS 26 brought most RCS features but notably lacked E2EE. During the iOS 26.4 beta cycle, Apple briefly included E2EE for RCS but removed it before the public release, citing technical issues or incomplete carrier support. The company promised it would return, and with iOS 26.5, that promise is fulfilled.
How End-to-End Encryption Works in RCS
End-to-end encryption ensures that only the sender and recipient can read the message. Even Apple or the carrier cannot decrypt it. Apple’s implementation leverages the same encryption technology used in iMessage, likely based on the Signal Protocol or a similar key exchange mechanism. The encryption applies to text messages, images, videos, and other media sent via RCS. It does not apply to SMS/MMS fallback messages, which remain unencrypted. Apple has also indicated that it will eventually support RCS Universal Profile 2.6 or later, which includes E2EE as a standard feature. The beta label suggests that Apple may still be fine-tuning the key management and interoperability with non-Apple RCS clients (such as Google Messages).
Carrier Support and Availability
Apple has announced that it plans to publish a list of carriers that support RCS E2EE on a dedicated webpage, but the page is not yet live. In the meantime, users can check with their carrier to see if they have enabled the necessary backend infrastructure. Major carriers like Verizon, T-Mobile, and AT&T in the United States are expected to support the feature, along with many international carriers. The rollout will be gradual, as carriers must update their RCS hubs to support the encryption protocol. Apple’s release notes explicitly state, “End-to-end encrypted RCS messaging (beta) in Messages is available with supported carriers and will roll out over time.” This indicates that even after installing iOS 26.5, users may not immediately see the encryption label on their green bubble conversations. It may take weeks or months for full global coverage.
Comparison with iMessage and Other Platforms
With this update, RCS on the iPhone will now match iMessage in terms of encryption, but not in all other aspects. iMessage remains Apple’s proprietary platform, offering features like Send Later, Message Effects, Digital Touch, and seamless Handoff across Apple devices. RCS, on the other hand, is a universal standard. By adding E2EE, Apple ensures that even conversations with Android users are private, which could reduce the incentive for users to pressure their friends to switch to iPhone for secure chats. Competitors like Google have been pushing for universal E2EE in RCS for years, and Apple’s move brings the entire ecosystem closer to that goal. However, it remains to be seen whether Apple’s E2EE will be compatible with Google’s own E2EE implementation in Google Messages, as that uses a different protocol (Signal-based). Both companies have historically collaborated on interoperability standards, so expect eventual alignment.
Impact on Users and Privacy Advocates
Privacy advocates have long criticized the lack of encryption in cross-platform messaging. The addition of E2EE to RCS on iOS 26.5 is a welcome development, particularly for users in sensitive professions or regions. It also aligns with Apple’s marketing emphasis on privacy as a fundamental human right. However, the beta label may worry some users who demand absolute reliability. Apple likely added the beta tag to manage expectations; if issues arise with key exchange or message delivery, they can be addressed without public backlash. The encryption is also optional from the carrier side—users should ensure their carrier supports it to benefit. For now, iPhone users can enable the feature by ensuring they have the latest iOS 26.5 RC or public release and by having a compatible SIM/eSIM from a supported provider.
Technical Details and Future Outlook
Under the hood, Apple employs a method called “key transparency” or “key directory” to verify that the encryption keys are genuine and not tampered with. This is similar to what Apple already uses for iMessage. The keys are generated on-device and shared with the recipient through a secure channel, often using carrier-grade identity verification. The beta period will likely focus on testing this key exchange at scale. Looking ahead, Apple is expected to remove the beta label in a future update, possibly iOS 26.6 or iOS 27, once the feature is stable and widely supported. The GSMA is also working on standardizing E2EE for RCS as part of the Universal Profile, which would make carrier interoperability mandatory. Apple’s early adoption could pressure smaller carriers to upgrade their infrastructure.
Additionally, Apple is rumored to be developing a dedicated RCS encryption protocol that could work even when the recipient’s device is offline, using encryption keys stored in the cloud. This would mirror iMessage’s behavior. Another potential improvement is encrypted group chats over RCS, which are currently not supported in iOS 26.5. Apple may add this in later iterations. The company has also hinted at integrating RCS E2EE into its broader privacy framework, such as iCloud Keychain, to allow users to manage their encryption keys across devices.
How to Prepare for iOS 26.5
Users eager to benefit from RCS E2EE should ensure their carrier is listed as supported once Apple updates the webpage. In the meantime, they can install the iOS 26.5 RC or wait for the final public release, expected next week. The update also includes other enhancements like improvements to Apple Intelligence, new emoji, and security patches. To check if RCS E2EE is active after updating, users can start a conversation with an Android contact and look for a lock icon or “Encrypted” label in the message bubble, similar to the iMessage lock icon. If the feature is not yet enabled, Apple recommends checking with the carrier or waiting for a carrier-side update. As always, users should back up their iPhones before installing the beta RC to avoid data loss.
The broader context of this update is Apple’s commitment to cross-platform compatibility under regulatory scrutiny. The European Union’s Digital Markets Act has forced Apple to open up its ecosystem, and RCS E2EE is a direct result of that pressure. While some users remain frustrated that iMessage is still exclusive to Apple devices, the E2EE upgrade for RCS significantly blurs the line between green and blue bubbles. For many, the privacy parity alone is worth the upgrade. As the rollout proceeds in the coming months, expect more carriers to jump on board, and for Apple to refine the implementation based on user feedback.
In related news, Apple has also published a support document detailing how RCS encryption works on iOS, though it is still sparse. The company is expected to provide more technical documentation once the feature leaves beta. Developers can test the E2EE capabilities in the RC build by using the Messages framework in the operating system. Third-party messaging apps like WhatsApp and Telegram already offer E2EE, but Apple’s integration of it into the default Messages app means that billions of iPhone users will now have access to encrypted conversations without needing to download extra software. This could push other messaging platforms to enhance their own security postures.
Source: 9to5Mac News