After months of anticipation, Apple is expanding end-to-end encrypted (E2EE) RCS messaging to a broader audience. This feature allows iPhone and Android users to exchange texts with stronger security, ensuring messages remain private while in transit. Starting with iOS 26.5, Apple is rolling out the capability to a larger group of users, following successful testing on developer betas. Below, we answer the most common questions about this update, including requirements, benefits, and how it changes cross-platform texting.
1. What is the new encryption feature being introduced for RCS messaging on iOS?
Apple is integrating end-to-end encrypted (E2EE) RCS messaging into iOS. This means that when an iPhone user with iOS 26.5 sends an RCS message to an Android user running the latest version of Google Messages, the message content is encrypted from sender to receiver. No third party—including Apple, Google, or any carrier—can read the message while it's being transmitted. This marks a significant leap in cross-platform texting security, as traditional SMS/MMS lack encryption entirely.
2. When did Apple begin testing encrypted RCS, and what is the current status?
Apple started testing E2EE RCS a few months ago within iOS 26.4 developer betas. Those early tests were limited to developers and small groups. On Monday, Apple announced that the feature is now ready for large-scale public testing as part of the iOS 26.5 update. This broader rollout allows more iPhone users to experience encrypted cross-platform chats, though full availability may vary by carrier and region.
3. What are the requirements for iPhone users to access encrypted RCS messaging?
To use E2EE RCS on an iPhone, you need:
- iOS 26.5 or later installed on your device.
- A supported carrier that enables RCS with encryption. Carriers must implement Apple’s RCS profile; not all providers are compatible yet.
- Both the sender and receiver must meet their respective platform requirements (see next question).
If these conditions are met, your RCS messages automatically become end-to-end encrypted. No manual settings are needed—the system handles encryption in the background.
4. What are the requirements for Android users to participate in encrypted RCS chats?
On the Android side, users must have the latest version of Google Messages installed. Google has supported E2EE for RCS between Android devices for some time, but cross-platform encryption with iPhones requires this update. As long as both parties meet the requirements (iOS 26.5 + supported carrier on iPhone, and latest Google Messages on Android), messages will be encrypted end-to-end.
5. How does end-to-end encryption (E2EE) enhance security for cross-platform texting?
E2EE ensures that messages are scrambled at the sender’s device and only unscrambled at the receiver’s device. No intermediary—including Apple, Google, or your mobile carrier—can access the plain text. This protects against:
- Interception by hackers or surveillance.
- Data breaches at server farms.
- Unauthorized access by carriers.
Previously, RCS messages between iOS and Android were only encrypted in transit (TLS), but not end-to-end, leaving them readable by service providers. E2EE closes that gap.
6. Why is this rollout significant for cross-platform communication between iOS and Android?
This update bridges a long-standing security gap. While Apple’s iMessage and Google Messages (Android-to-Android) already offered E2EE, cross-platform texts relied on SMS or non-encrypted RCS, exposing conversations to potential eavesdropping. By adding E2EE to RCS, Apple and Google create a unified, secure messaging standard that works across both ecosystems. It also reduces pressure on users to switch platforms for better privacy—now anyone on a modern iPhone or Android can text securely.
7. Are there any limitations or conditions users should be aware of?
Yes. Encryption only works when both parties meet the requirements (iPhone requirements and Android requirements). If either side is using an older version of iOS, Google Messages, or an unsupported carrier, messages will fall back to standard RCS (encrypted only in transit) or SMS (no encryption). Also, some features like group chats or media sharing may have varying encryption support—Apple and Google are still refining these. Finally, encryption does not protect metadata (who sent the message and when), though the content remains private.
8. What steps did Apple take before the large-scale rollout?
Apple first introduced E2EE RCS in iOS 26.4 developer betas to test compatibility and security. During those months, engineers worked with Google and carriers to iron out issues. After successful small-scale tests, Apple moved to a public testing phase in iOS 26.5, making the feature available to more iPhone users. This gradual approach ensures that any bugs are caught before a final, stable release. Apple plans to continue monitoring feedback and may expand carrier support over time.