Apple releases iOS 26.5, introducing end-to-end encryption for RCS messaging in beta with supported carriers; the setting is enabled by default
iOS 26.5 is now available to everyone after six weeks of beta testing. The update adds fresh wallpapers, new features to Apple Maps, and more.
Context & Ripple Effects
Apple’s encrypted-RCS work progressed from limited developer-beta support in iOS 26.4 to a public iOS 26.5 release. The underlying cross-platform capability follows the GSMA standard’s addition of interoperable end-to-end encryption, which Apple had said it would support in a future OS update.
The change is notable because Apple had previously positioned RCS as distinct from iMessage, including through its separate green-bubble treatment. Encryption arriving as a default setting for supported carrier connections makes RCS a more capable fallback for conversations outside Apple’s proprietary messaging service.
First-order effects
- iPhone users on supported carriers receive end-to-end encryption for eligible RCS chats by default while the feature remains in beta, reducing the need to manually opt in.
- Apple moves its RCS implementation closer to the security model contemplated by the GSMA’s interoperable encryption standard, while retaining iMessage as a separate service.
Second-order effects
- Carrier support becomes a practical gating factor: operators that do not support the encrypted RCS path may create an uneven messaging experience across iPhone users.
- The rollout raises the baseline that cross-platform messaging implementations must meet, increasing pressure on ecosystem participants to support the interoperable encrypted RCS standard rather than treat RCS solely as an SMS/MMS replacement.
Third-order effects
- If carrier support broadens and the beta graduates, encrypted RCS could make secure cross-platform messaging less dependent on a single platform’s proprietary service, while leaving platform-specific features and branding intact.
- The episode points to messaging security being set increasingly through standards and deployment interoperability, not only by individual app providers; the pace will depend on carrier implementation and cross-platform execution.
The trend: RCS is evolving from a carrier-led SMS replacement into a standards-based cross-platform messaging layer where interoperability and end-to-end encryption are baseline competitive requirements.