iPhone-to-Android Texts Are Now Encrypted: Turn On RCS E2EE
iOS 26.5 brings end-to-end encrypted RCS between iPhone and Android. Here's how to check it's on and what the green padlock means.
The blue-bubble, green-bubble divide just got a lot less risky. With iOS 26.5, Apple added end-to-end encryption to RCS messages between iPhone and Android, finally closing the gap where the most ordinary kind of text, the one between two people on different phone brands, was not protected the way iMessage chats always have been. The feature is in beta and needs both sides to be up to date, so here is how to confirm it is working and what to actually look for.
Quick answer
Update to iOS 26.5 or later, then go to Settings, Apps, Messages, tap RCS Messaging, and confirm the End-to-End Encryption (Beta) toggle is on. Once enabled, RCS chats with a compatible Android contact are encrypted so only you and the recipient can read them. Encryption only applies when both ends support it, so a chat with an old phone or a carrier that has not enabled encrypted RCS falls back to unencrypted RCS or SMS. iMessage-to-iMessage chats were already encrypted; this fixes the cross-platform case.
Key takeaways
- iOS 26.5 adds end-to-end encryption (E2EE) for RCS messages between iPhone and Android.
- It is currently a beta toggle, found under Messages' RCS settings.
- Both devices must support and enable encrypted RCS for a conversation to be protected.
- The update also brought RCS-adjacent improvements, new wallpapers, and minor refinements.
- iMessage-to-iMessage chats were already encrypted; this fixes the cross-platform case.
Why this matters
Until now, a text between an iPhone and an Android phone fell back to RCS or SMS, and RCS as deployed was not end-to-end encrypted across platforms. That meant the most everyday kind of message, the one between two people on different phone brands, lacked the protection iMessage users took for granted. iOS 26.5 closes that hole by encrypting the message contents so only the sender and recipient can read them.
It is the kind of change that does not look like much in a release-notes bullet but quietly improves the security of billions of ordinary conversations. The encryption is built on the GSMA's updated RCS Universal Profile, which added a cross-platform end-to-end encryption standard using the MLS (Messaging Layer Security) protocol. That standardization is why an iPhone and an Android phone can now share encryption keys at all, something that was technically impossible in the older RCS deployment.
Here is what the change does and does not cover at a glance:
| Conversation type | Before iOS 26.5 | After iOS 26.5 |
|---|---|---|
| iMessage to iMessage | Encrypted | Encrypted (unchanged) |
| iPhone to Android (RCS) | Not end-to-end encrypted | Encrypted when both sides qualify |
| Fallback to SMS | Not encrypted | Still not encrypted |
| Old Android or unsupported carrier | Not encrypted | Falls back, not encrypted |
How to check RCS encryption is on
First, make sure you are running the right version.
- Open Settings > General > Software Update and install iOS 26.5 or later.
- Go to Settings > Apps > Messages.
- Tap RCS Messaging.
- Confirm the End-to-End Encryption (Beta) toggle is on.
Once enabled, a conversation with a compatible Android contact can carry encrypted RCS. As with iMessage, encryption only applies when both ends qualify, so a chat with an old phone or a carrier that has not enabled encrypted RCS will fall back.
Note
Because the feature is labeled beta, behavior can vary by carrier and by the Android side's update status. If a chat is not showing as encrypted, confirm the other person is also on a recent build with encrypted RCS support.
Why "Beta" and what it means in practice
The toggle is labeled "Beta" not because the encryption is shaky, but because the cross-platform ecosystem around it is still filling in. Encrypted RCS depends on three parties all being ready: your iPhone (iOS 26.5+), the other person's Android phone and messaging app (a recent Google Messages build with encrypted RCS support), and both carriers having rolled out the updated RCS Universal Profile. Any weak link and the chat quietly falls back to unencrypted RCS or plain SMS.
In practice this means encryption will be inconsistent for a while. A chat with a friend on a flagship Pixel on a major US carrier is likely to be encrypted; a chat with someone on an older Android phone, a smaller regional carrier, or a third-party SMS app may not be. The fallback is silent by design, so the only reliable way to know is the encrypted indicator in the conversation. If protecting a specific conversation matters, the safest move is still a dedicated encrypted app like Signal, where both ends are guaranteed to use the same protocol.
What else iOS 26.5 included
The encryption headline shipped alongside a handful of smaller items: new wallpapers, additional proximity-pairing options for third-party wearables in the EU, and assorted refinements. It sits within the broader iOS 26 release defined by Apple's Liquid Glass design overhaul, which you can read more about in our macOS Tahoe Liquid Glass features piece for the desktop side of the same redesign.
If your battery took a hit after updating, our walkthrough on fixing iPhone battery drain after iOS 26 covers the usual culprits.
A note on what encryption does and does not cover
End-to-end encryption protects the contents of your messages in transit so carriers and intermediaries cannot read them. It does not hide who you are talking to or when (that metadata still exists), and it does not protect a message once it is sitting decrypted on a device someone else can unlock. So the encryption is only as strong as your phone's lock. Keep a strong passcode, and on iPhone, turn on Stolen Device Protection so a thief who knows your passcode cannot trivially open your conversations. For account-level protection, passkeys remain the strongest option, as covered in our passkeys setup guide.
What to do right now
- Install iOS 26.5 or later under Settings, General, Software Update.
- Confirm the toggle at Settings, Apps, Messages, RCS Messaging, End-to-End Encryption (Beta) is on.
- Tell key contacts on Android to update too, since both sides must qualify for encryption to apply.
- Watch for the encrypted indicator in a chat; if it is missing, the message is falling back and is not protected.
- Lock down the device itself with a strong passcode and Stolen Device Protection, since encryption only protects messages in transit.
Frequently asked questions
Do both people need iPhones for encrypted RCS?
No, that is the whole point. The feature specifically encrypts RCS messages between an iPhone and an Android phone. Both devices just need to support and have enabled encrypted RCS.
Why is it labeled "Beta"?
Apple shipped the encryption capability while the broader cross-platform encrypted-RCS ecosystem is still maturing across carriers and Android versions. The beta label signals that coverage and reliability may vary until support is more universal.
How do I know a specific message was encrypted?
Encrypted conversations indicate their protected status in the Messages interface. If a chat falls back to unencrypted RCS or SMS, it will not show the encrypted indicator, which is your cue that the other side does not yet qualify.
Will this drain my battery or use more data?
Encryption overhead is negligible. The everyday cost of encrypted RCS is effectively the same as regular RCS messaging.
Bottom line
This is one of the most consequential security additions iOS 26 has shipped, and it costs you nothing but an update. Install iOS 26.5 or later, confirm the End-to-End Encryption toggle is on under Messages' RCS settings, and your cross-platform texts finally get the protection iMessage chats have always had.
