Apple's RCS Encryption: A Step Forward, But Not Quite There Yet
Apple has quietly introduced a significant security feature in its latest iOS 26.4 developer beta: end-to-end encryption (E2EE) for RCS (Rich Communication Services) in its Messages app. This development brings Apple's phone-number-based texting up to par with Google's RCS and Apple's own iMessage in terms of security.
The journey began with the iOS 26.3 Beta 2 release, where Apple added a setting to enable encryption for RCS between iPhone and Android devices. However, the current implementation has a catch: it only works between iPhones. You can enable RCS E2EE and see the new padlock icon in chats, but it doesn't secure texts with Android devices yet.
Since iOS 18.1, RCS has enhanced Apple's texting capabilities with features like typing indicators, read receipts, and improved media quality. Yet, a crucial feature was missing: cross-platform encryption. Android devices have offered secure RCS chats for a while, but Apple's initial implementation lacked end-to-end protection outside its ecosystem.
This limitation stems from the use of RCS Universal Profile 3.0, a newer standard that includes E2EE and modern messaging features. Initially, Apple introduced RCS on iPhone with version 2.4, which lacked these protections.
With iOS 26.4, Apple is testing encryption rather than fully launching the feature. The new toggle in Settings is enabled by default for developers and allows compatible carriers and devices to experiment with E2EE. Even with the switch on, you'll only get encrypted chats with other iPhone users who have iMessage disabled.
Apple confirms that full RCS E2EE will arrive in a future software update across iOS, iPadOS, macOS, and watchOS. While this may disappoint those eager for secure Apple-to-Android texting, it represents significant progress. Stay tuned as Apple continues to refine this feature, bringing us closer to a more secure messaging experience.
