Apple is preparing an end-to-end encrypted RCS upgrade for iPhone messaging that the company calls its biggest change to texting in 15 years, and public betas this week show how the system will behave when it arrives.
Apple’s documentation in the beta describes the new RCS messages as still appearing as green bubbles on iPhones, but encrypted end-to-end so “your conversations are encrypted end-to-end, so they can’t be read while they’re sent between devices.” The same notes also make clear that encrypted RCS can fall back to unencrypted RCS and then to SMS depending on whether every carrier and endpoint in a chat supports the latest standards.
The scale of the move is notable because iMessage has been end-to-end encrypted since 2011 and has only worked between Apple devices; Apple calls that protection out explicitly as it builds standards-based RCS support. Apple also tells users in the beta that “Apple’s implementation of RCS is based on the industry’s standard. RCS messages aren’t end-to-end encrypted, which means they’re not protected from a third-party reading them while they're sent between devices.” The phrasing makes both the change and the remaining limits plain.
The beta rollout is visible now. iOS 26.5 entered beta in late March, and this week public beta 3 for iPadOS 26.5, watchOS 26.5, tvOS 26.5 and other 26.5 software became available, according to 9to5mac. Another site reporting on the betas says iOS 26.5 also lays groundwork for ads in Apple Maps and other minor changes.
Apple’s move arrives after a year of public pressure and federal warnings. The FBI issued a 2024 warning urging U.S. citizens to stop texting on encrypted platforms, and Apple has positioned this messaging upgrade as a response to warnings from the FBI and CISA. That positioning frames the upgrade not just as a product change but as a security and policy answer to regulators and law enforcement.
The technical design means this will be unlike Apple’s iMessage or WhatsApp in important ways. Apple’s encrypted RCS is built on the industry standard, which also makes it carrier-dependent: if any carrier or device along the path does not support the new standard, the message can fall back to unencrypted RCS or to SMS. Google’s Messages product runs RCS over Google’s own servers as an over-the-top platform, while WhatsApp already offers cross-platform end-to-end encryption — “Messages and calls are end-to-end encrypted,” WhatsApp says — between iPhones and Android phones.
That layered architecture creates a familiar trade-off: a standards-based, widely supported cross-platform messaging format that depends on carriers and servers for delivery, versus closed ecosystems that can guarantee end-to-end protection because the company controls both endpoints. Apple’s new RCS will be standards-based and carrier-dependent; it will also still render Android-to-iPhone chats differently from native iMessage threads, the company warns.
The practical result for users is straightforward and uneasy at the same time. When every carrier and endpoint involved supports the new specifications, Apple’s RCS layer will deliver end-to-end encryption between iPhones and Android phones. When they do not, conversations can slip back into unencrypted RCS or legacy SMS. That reality is baked into the design as described in the beta: the green bubble will remain a visual signal, but it will no longer be a reliable indicator of the level of protection across platforms.
The biggest unresolved question is whether real-world messaging will stay encrypted once the upgrade goes live. Apple’s implementation is standards-based by design, but standards only help if carriers and third-party endpoints adopt them in lockstep. Google’s over-the-top approach and WhatsApp’s already universal end-to-end encryption present two alternative ways the industry has solved the cross-platform problem, and neither removes the risk that mixed-carrier threads will default to unencrypted paths.
Apple’s encrypted RCS upgrade is described by the company as the most significant change to texting in 15 years, and it is expected to go live imminently as the company moves through the 26.5 beta cycle ahead of larger seasonal releases. The question that will determine whether the change keeps its promise is no longer technical alone: it is whether carriers, platforms and endpoints across the ecosystem adopt and enforce the new standard when it matters most.
