How RCS End-to-End Encryption Works on iPhone in iOS 26.5

Photo by Maccy on Unsplash

Most coverage of RCS end-to-end encryption on iPhone frames it as the moment green bubbles finally caught up to blue ones. That framing is wrong. The encryption Apple started rolling out on May 12, 2026 is a carrier-dependent, beta-labeled feature built on a different protocol than iMessage, and Apple itself is careful to say iMessage is still the safer choice between two Apple devices.

The practical effect for most people is simple: a text from your iPhone to your sister's Pixel can now be unreadable in transit, provided both of your carriers are on the right software. The mechanics underneath, and the things the lock icon does not cover, are where this gets interesting.

The Protocol Apple Picked Is Not the One iMessage Uses

iMessage has run on Apple's own proprietary encryption stack since 2011. RCS does not. According to MacRumors, the new encryption is part of RCS Universal Profile 3.0 and uses the Messaging Layer Security (MLS) protocol, an IETF standard finalized as RFC 9420 in 2023. That distinction matters because MLS was designed from the start for cross-vendor group messaging, where the participants might be on different operating systems, different apps, and different servers.

MLS solves a problem the Signal Protocol handles awkwardly at scale: efficient key updates in large groups. Instead of pairwise ratchets between every member, MLS uses a tree-based key schedule that lets a group of thousands rotate keys in logarithmic time. For a two-person SMS replacement that sounds like overkill, but the GSMA needed a protocol that could survive group chats spanning carriers, OEMs, and messaging clients without anyone having to trust a single vendor's server.

That is the architectural reason Apple, Google, and the carriers could agree on MLS at all. No one had to adopt anyone else's house protocol.

What Actually Happens When You Send an Encrypted RCS Message

Think of it like sending a sealed envelope through a postal service that has historically read every postcard. The post office still routes the envelope. It still knows who sent it, who is receiving it, and when. It just cannot read the contents anymore.

That analogy is close to literal here. E2EE applies when messages are in transit between devices; the standard does not prevent either endpoint from having messages accessible on the device itself, and metadata such as sender, recipient, and timestamp is not covered by MLS encryption under the current RCS Universal Profile 3.0 spec, as The Hacker News noted in its launch coverage. Apple's own description is narrower than the marketing language suggests: "When RCS messages are end-to-end encrypted, they can't be read while they're sent between devices", the company wrote in its newsroom announcement.

The iOS 26.5 Messages app gives you a visible signal that the protection is active. According to 9to5Google, an encrypted RCS conversation shows the label "Text Message · RCS | [lock icon] Encrypted" at the center of the screen. No lock, no encryption.

The Carrier Catch That Breaks the Default-On Promise

Apple says iOS 26.5 RCS encryption is on by default. That phrasing hides the most important constraint of this rollout.

For a conversation to be encrypted, both the sender and receiver must use a carrier that supports the latest version of RCS. If either party's carrier does not support it, messages fall back to unencrypted RCS, MacRumors confirmed. In the US, 9to5Google lists 23 supported carriers at launch including AT&T, Verizon Wireless, T-Mobile USA, Boost Mobile, Cricket, Metro by T-Mobile, Mint Mobile, Consumer Cellular, TracFone, Straight Talk, Visible, US Cellular, and Xfinity Mobile. Internationally, the list is thinner. The rollout is gradual and will take place over the coming months, not instantly for all users even on supported carriers.

The consequence is a UI signal that depends on infrastructure neither user controls. You can be on the latest iOS 26.5 build, your recipient can be on the latest Google Messages, and the chat can still silently degrade to plain RCS because one of your carriers has not finished updating its backend. There is no in-app warning that explains why the lock disappeared on a given thread. You just have to notice.

That is the single biggest weakness of this launch, and it deserves more attention than the celebratory framing has given it.

RCS vs iMessage Privacy: Why Apple Still Pushes Blue Bubbles

Read Apple's announcement carefully and you can see the company hedging. Apple explicitly maintains that iMessage has always been end-to-end encrypted and remains the best way to communicate between Apple devices, a qualifier the newsroom post repeats more than once. The framing positions RCS E2EE as a fallback for when you must talk to Android, not a replacement for iMessage.

There are real reasons for that hedge beyond marketing. iMessage's encryption covers messages, attachments, FaceTime, group threads, and increasingly cloud backups under Advanced Data Protection. RCS E2EE in this release covers transit only, with metadata left exposed and the feature still carrying a beta label. The feature remains labeled beta even in the shipping iOS 26.5 release; users can toggle it at Settings > Messages > RCS Messaging.

The practical RCS vs iMessage privacy comparison breaks down like this:

• Transit encryption: Both protocols now encrypt messages in motion. Parity.
• Metadata exposure: iMessage minimizes metadata visible to Apple. RCS routes through carrier infrastructure that sees sender, recipient, and timing.
• Backup encryption: iMessage backups can be E2EE through iCloud Advanced Data Protection. RCS backup protection depends on the device platform and is not part of Universal Profile 3.0.
• Group membership integrity: MLS provides strong guarantees for group state. iMessage groups have historically been weaker here, so RCS actually wins this one on paper.
• Maturity: iMessage has 15 years of cryptographic scrutiny. RCS E2EE is days old at scale.

If you care about privacy and security as the primary axis, iMessage to iMessage is still the safer default when both parties have iPhones. The new RCS encryption closes the gap for cross-platform chats. It does not eliminate it.

The Quiet Path From iOS 26.4 Beta to Shipping in 26.5

Apple did not get this right on the first try. Testing of E2EE for RCS began in iOS 26.4 beta in mid-February 2026, but Apple removed it before iOS 26.4 shipped. The retreat was not announced loudly, and the company has not detailed publicly what went wrong.

AppleInsider's reporting on the early beta cycle adds a strange detail. The very first iOS 26.4 test build limited E2EE RCS exclusively to iPhone users with iMessage disabled, and cross-platform iPhone-to-Android E2EE was only unlocked in the second iOS 26.4 developer beta roughly one week later. That sequencing suggests Apple was treating the feature as an internal RCS test first and a cross-platform interoperability feature second, which lines up with how cautiously the company has approached RCS since adding the base protocol in iOS 18 in September 2024.

The timeline also matters because it explains the beta label. Apple announced plans to add E2EE RCS support in March 2025; beta testing started February 2026. A full year of development, three months of internal testing, and the feature still ships as beta. That is not normal for an iOS point release, and it signals Apple is hedging against carrier-side bugs it cannot fully control.

Does RCS Encrypt Messages in Every Group Chat? Not Quite

A detail buried in the standard that most launch coverage missed: MLS encryption in Universal Profile 3.0 requires every participant in a group to support the protocol. One member on an older Android build, an older carrier provisioning, or a non-RCS SMS fallback can downgrade the entire conversation.

This is the predictable trade-off of cross-vendor encryption. Signal and iMessage can enforce protocol uniformity because they control every endpoint. RCS cannot. The result is that a five-person group chat with four iPhones on iOS 26.5 and one Pixel on an older Google Messages build is unencrypted for everyone, not just the lagging participant.

Universal Profile 3.0 also introduces non-encryption features that work independently of MLS support. RCS Universal Profile 3.0 adds editing and deleting messages, cross-platform Tapback support, and replying to specific messages inline during cross-platform conversations. Those features can light up without the lock icon, which will create user confusion about what is and is not protected.

The Industry Politics Hiding Behind the Lock Icon

This release would not exist without three groups agreeing simultaneously, which almost never happens in mobile. Apple worked with Google and the GSM Association to implement E2EE for RCS, a cross-industry collaborative effort. GSMA CTO Alex Sinclair told The Hacker News the work came out of "close, cross-industry collaboration between the GSMA RCS Working Group, including Apple, Google, and the wider mobile ecosystem."

The regulatory pressure that pushed this forward is worth naming. The EU's Digital Markets Act and similar antitrust scrutiny in the US have spent two years framing iMessage's exclusivity as anticompetitive. Apple's response, broadly, has been to make RCS good enough that the green-bubble grievance loses its political weight without giving up iMessage's structural advantages. Encrypted RCS does exactly that.

It is also why Apple's announcement language is so careful to keep iMessage above RCS on the privacy hierarchy. The company is meeting regulators where they live while making sure the upgrade path for Apple-to-Apple users stays inside Apple's stack.

What Else Shipped in the Same Update

iOS 26.5 is not a single-feature release, though E2EE RCS is the headline. iOS 26.5 also patches over 50 security vulnerabilities in iOS and iPadOS, including flaws in AppleJPEG, ImageIO, Kernel, mDNSResponder, and WebKit. Installing the update is justifiable on the patch list alone, encryption aside.

iOS 26.5 is also laying groundwork for ads in Apple Maps and Apple Intelligence in China, but contains no AI model upgrades, making E2EE RCS the headline feature of this release cycle. That ordering tells you what Apple wants the press cycle to focus on. The Maps ads groundwork has gotten almost no coverage, which is its own story for another article.

What to Actually Do With This Information

If you have an iPhone running iOS 26.5, update tonight for the security patches and check Settings > Messages > RCS Messaging to confirm RCS is toggled on. When you next text an Android user, look at the center of the conversation for the encrypted label. If it is not there, the limiting factor is almost certainly one of the two carriers, not your device.

For anything truly sensitive, the calculus has not changed. iMessage between two iPhones, or Signal between any two devices, is still the answer. Encrypted RCS is a meaningful upgrade over the SMS-and-MMS status quo that has lasted since the 1990s. It is not a replacement for purpose-built secure messaging, and Apple is not pretending it is.

The lock icon is a starting line, not a finish line.