RCS Messaging Between iPhone and Android: What Actually Changed With End-to-End Encryption

For more than a decade, texting between an iPhone and an Android phone meant falling back to old-fashioned SMS and MMS: no read receipts, no typing indicators, compressed and often blurry photos and videos, and no encryption of any kind. That finally started changing, and 2026 marks the point where the last major piece — real end-to-end encryption on cross-platform messages — actually arrived rather than just being announced.

What RCS Is, Briefly

RCS (Rich Communication Services) is a messaging standard designed as a modern successor to SMS, adding features that had long been standard in third-party apps like iMessage or WhatsApp: high-resolution photo and video sharing, typing indicators, read receipts, group chat improvements, and messaging over Wi-Fi or data rather than being limited to a cellular SMS connection. RCS itself isn't new — carriers and Google had been pushing it for years — but for most of that time it only worked reliably between two Android phones using Google Messages, since Apple simply didn't support it on iPhone at all.

Apple's 2024 Adoption — and What It Didn't Include

That changed when Apple added RCS support to iOS 18, iPadOS 18, watchOS 11, and macOS 15 in 2024, adopting version 2.4 of the GSMA's RCS Universal Profile — the industry-standard specification that defines how RCS is supposed to work across different carriers and device makers. This was a genuinely significant shift: for the first time, texts between an iPhone and an Android phone could carry proper read receipts, typing indicators, and full-resolution media without needing a third-party app on either end.

What that initial 2024 rollout did not include was end-to-end encryption. Universal Profile 2.4, the version Apple adopted at launch, didn't support it, meaning cross-platform RCS messages between iPhone and Android were readable in principle by carriers or other intermediaries in the delivery chain — a meaningfully weaker security posture than iMessage-to-iMessage or WhatsApp-to-WhatsApp conversations, which have both been end-to-end encrypted for years.

The Encryption Fix: Universal Profile 3.0 and MLS

The gap closed with the GSMA's Universal Profile 3.0 update. In March 2025, the GSMA announced that RCS Universal Profile 3.0 would add support for end-to-end encryption built on the Messaging Layer Security (MLS) protocol — an open standard designed specifically to allow secure, encrypted group and one-to-one messaging to interoperate across different apps and providers, rather than being locked to a single company's proprietary encryption scheme the way iMessage's encryption is locked to Apple's own ecosystem. Apple confirmed it would support this updated standard on Apple Messages, and both Google Messages and Apple Messages began actually rolling out MLS-based end-to-end encryption over RCS starting in May 2026.

The practical result: text conversations between a current iPhone and a current Android phone running up-to-date software can now be genuinely end-to-end encrypted for the first time, provided both people are on RCS (rather than one side having it disabled or being on an older software version that falls back to plain SMS). It's worth being precise about what "end-to-end encrypted" means here — MLS being an open, interoperable standard rather than a single vendor's closed protocol is specifically what makes cross-platform encryption possible at all, since iMessage's own encryption was never designed to talk to a non-Apple device's decryption keys.

Why This Took So Long

The multi-year gap between "Apple adds RCS" and "cross-platform RCS is actually encrypted" reflects how standards bodies work: GSMA's Universal Profile is a shared specification that many carriers, chipset makers, and phone manufacturers all have to implement consistently for encrypted messaging to actually interoperate reliably, rather than one company simply flipping a switch on their own app. Building an encryption scheme that two independently developed messaging apps — Google Messages and Apple Messages — could both implement correctly and interoperably took real coordination through the GSMA process, which is also why it arrived roughly a year after the encryption standard itself was finalized rather than immediately.

What This Means for Everyday Users

For most people, the visible change is subtle: greenbubble/blue-bubble conversations between iPhone and Android now show a lock icon or equivalent indicator when a conversation is encrypted, full-resolution photos and videos, and proper read receipts and typing indicators, none of which existed in cross-platform texting before 2024. The bigger, less visible change is that a text conversation between an iPhone and an Android phone finally carries the same baseline privacy protection that same-platform messaging (iMessage-to-iMessage, or WhatsApp-to-WhatsApp) has had for years — closing off casual interception by carriers or network intermediaries, though it's worth noting RCS encryption, like most messaging encryption, doesn't protect against either device itself being compromised, or against one participant simply forwarding or screenshotting a conversation.

This shift is part of a broader pattern of platform boundaries between iPhone and Android quietly narrowing over the past few years, alongside changes like how software support timelines compare between the two ecosystems. For readers specifically concerned about mobile privacy more broadly, our app permissions and tracking comparison covers how the two platforms' privacy controls differ beyond just messaging, and if you're deciding between ecosystems, the Pixel 10 and its full review reflect Google Messages' current RCS implementation directly.

What Still Doesn't Carry Over

It's worth being clear about the limits of this upgrade, because RCS still isn't a full replacement for a dedicated cross-platform messaging app in every respect. Some iMessage-specific features — full message editing and unsending with version history visible only within Apple's own ecosystem, certain sticker and Memoji effects, and deep integration with other Apple services — don't translate over RCS and likely never will, since they depend on proprietary Apple infrastructure rather than the shared GSMA standard. RCS also still depends on both parties having a live data or Wi-Fi connection and an RCS-capable messaging app actively enabled; if either condition isn't met, the conversation silently falls back to old-fashioned SMS or MMS without necessarily any prominent warning that encryption and rich features have quietly dropped away for that conversation. Carrier-level RCS provisioning has also historically lagged in some regions and on some prepaid or budget carrier plans, so availability isn't yet as universal as SMS itself, even though the underlying standard is now mature and encryption-capable on both major platforms.

The Bottom Line

RCS closed most of the cross-platform messaging gap with Apple's 2024 adoption, but the last and most important piece — genuine end-to-end encryption between iPhone and Android — didn't arrive until Universal Profile 3.0's MLS-based encryption rolled out across both Google Messages and Apple Messages starting in May 2026. If you're texting across platforms today, that gap is now closed on current software, but it's worth confirming both you and the person you're messaging are running up-to-date apps, since an outdated device on either end will silently fall back to unencrypted SMS instead.