The arrival of iOS 26.5 This marks a turning point in how iPhone users communicate with those who have an Android phone. Apple has finally activated the end-to-end encryption in RCS messages between both platforms, a feature that had been on the list of requests from users most concerned about privacy for years.
Until now, chats between iPhone and Android using RCS offered modern features like sending high-quality photos, typing indicators, and read receipts, but they lacked the key ingredient: a real content protection versus third parties. With iOS 26.5, that gap is filled and the system's native messaging is approaching what apps like WhatsApp or Signal already offered.
What has changed in RCS messaging with iOS 26.5
With the new version of the system, Apple introduces in beta phase the end-to-end encryption (E2EE) for RCS messages that are exchanged between iPhone and Android. This feature is available to those who update to iOS 26.5 and have a carrier compatible with the updated RCS standard, while on the Android side it is necessary to use the latest version of Google Messages.
RCS (Rich Communication Services) is the standard that aims to replace the old SMS and MMS. It allows Longer messages, sending high-quality photos and videos, improved groupsWrite indicators and read receipts, all using a cellular data or Wi-Fi connection. It's available on iPhone from iOS 18.1 onwards, but without end-to-end encryption Security was inferior to iMessage and many other messaging apps.
Apple acknowledges that the E2EE for RCS is being launched as a beta functionbut already usable on a daily basis. The rollout is progressive, both in New conversations as well as in existing chatsand will expand as more operators upgrade their networks and more users install the latest software versions.
In addition to this change in messaging, iOS 26.5 comes with other minor additions, such as the new wallpaper. Pride Luminance with dynamic effects, targeted improvements to the Reminders app, easier Bluetooth pairing of Magic Mouse, Magic Keyboard, and Magic Trackpad accessories after connecting via USB-C, and New features in Maps such as suggested places based on recent trends and searches.
In the regulatory sphere, the update also brings Specific adjustments for the European UnionThis includes changes to how Live Activities are handled with third-party accessories to align with local regulations. Outside of Europe, markets like Brazil are beginning to prepare for the installation of apps from sources other than the App Store with this same system version.
How end-to-end encryption works in RCS messages
End-to-end encryption in RCS ensures that only the sender and receiver can read the content of a conversation. Messages are encrypted on the sending device and only decrypted on the receiving mobile, so neither Apple, nor Google, nor the carrier can access the text or files while they are in transit.
To offer this protection, Apple and Google rely on the protocol Messaging Layer Security (MLS)The cryptographic standard that the GSMA included in Universal Profile 3.0 in 2025. It's the same system that Google Messages has long used to protect RCS chats between Android phones, but now it also applies to... cross-conversations between iOS and Android.
For the user, the experience is virtually seamless. End-to-end encryption is active by default when the technical conditions are met and no additional configuration is required. The only visible clue is the appearance of a padlock icon within the chat that indicates that the conversation is protected.
If you want to check it from your iPhone, you can go to Settings → Messages → RCS MessagingWithin this section you will see the switch for End-to-end encryption (Beta)which is enabled by default on compatible devices. If the carrier does not yet support the appropriate profile or the Android device does not meet the requirements, the conversation will still be RCS but without E2EE encryption, and the lock will not be displayed.
The key lies in the combination of three factors: having installed iOS 26.5 or later on iPhone, have the latest version of Google Messages on your Android device and have a operator who has deployed RCS Universal Profile 3.0 at both ends. If one of those elements fails, security is reduced to the previous level, with possible drops to unencrypted RCS or even SMS.
Apple, Google and the GSMA: a rare joint effort for privacy
For years, Apple and Google have openly competed on almost every front, and the mobile messaging This has been no exception. Google was pushing RCS as a replacement for SMS, while Apple was defending iMessage as its own platform with end-to-end encryption from day one.
Google even launched public campaigns such as “Get the message” to pressure Apple into adopting RCS, arguing that users suffered a worse experience in cross-platform chats between iPhone and Android. Apple resisted for years, until in 2024 it announced that it would integrate RCS into iOS, something that materialized with iOS 18, although without encrypted protection in the multiplatform section.
The missing piece was precisely the standardization of encryption. The GSMA, the association that represents the major operators, published the universal profile in 2025. U.P. 3.0 with official support for RCS encrypted using MLS, which opened the door to true interoperability between different apps and systems. Since then, both Apple and Google have worked to align your solutions with that standard.
Apple and Google have presented this launch as a joint effort of the sector led by both companiesThis is unusual between two direct rivals in consumer products. In practice, this collaboration also responds to regulatory pressures, especially in Europe, where the Digital Markets Act has been demanding for some time greater interoperability and security in the dominant messaging services.
Meanwhile, in the Android ecosystem, Google Messages has already featured end-to-end RCS encryption in individual and group chats for years. The announcement of iOS 26.5 therefore represents the the missing bridge between the two worldsallowing cross-platform conversations to enjoy the same level of protection as the native chats of each platform.
Situation in Spain and Europe: compatible operators and deployment
The implementation of RCS encryption doesn't depend solely on Apple and Google. Mobile operators play a crucial role, as they are responsible for Upgrade your infrastructure to RCS Universal Profile 3.0 and enable support for end-to-end encryption on their networks.
Apple has published an official list of carriers compatible with RCS messaging on iPhoneIn Spain, the main companies in the market are already listed: MásMóvil, Movistar, O2, Orange, Pepephone, Vodafone and YoigoAll of them announce support for RCS on their networks, although the effective deployment of encryption may progress at different rates in each one.
In the case of these operators, RCS messaging is added to other features such as 5G, VoLTE, Wi-Fi calling, eSIM or advanced emergency location (AML)RCS compatibility on iPhone is now considered a standard feature, especially in large groups with a greater presence in Europe.
For the Spanish user, the practical consequence is that, if their company is on the list of compatible operators and the contact they are talking to also uses a prepared network, RCS chat between iPhone and Android will work. It may be end-to-end encryptedIn those cases, the padlock icon will appear in the conversation indicating that protection is active.
In the broader European context, the evolution of RCS with E2EE encryption is seen as a further step towards a more secure and standardized messaging cross-platform integration, in line with the European Commission's requirements on privacy and competition. The combination of regulatory pressure and technical collaboration has accelerated a change that for years seemed stalled.
iMessage remains the safest option among Apple users
Although the new RCS encryption significantly improves the situation of the “green bubbles” (Android chats), Apple insists that iMessage remains its primary communication tool within its own ecosystem. The company's service features native end-to-end encryption Since its launch, it has been independent of operator networks and has additional layers of protection.
The move in iOS 26.5 is not intended to replace iMessage, but close the security gap This existed when an iPhone user spoke to someone on Android using the system's messaging app. Until now, these conversations lacked the end-to-end protection that chats between iPhones had, which is surprising for a company that has placed so much emphasis on privacy.
With the new rollout, the scenario is as follows: if both contacts use Apple devices, iMessage remains the recommended method by the company itself; if one of them is on Android, RCS with E2EE encryption becomes the most secure option within the system's integrated messaging, approaching the level offered by the most popular third-party apps.
In any case, the decision to use iMessage, encrypted RCS, or external applications like WhatsApp or Signal will depend on the environment of each user and their circle of contactsThe important thing is that, for the first time, native messaging between iPhone and Android offers a level of security in line with what many have been expecting for years.
Requirements, activation, and checks from your iPhone
For RCS end-to-end encryption between iPhone and Android to work correctly, several technical conditions must be met, and these should be clearly understood. Simply updating the phone is not enough, although it is an essential first step.
First, your iPhone must have iOS 26.5 installedYou can check it by going to Settings → General → Software Update and downloading the latest available version. Without this update, end-to-end encryption for RCS doesn't even come into play.
Secondly, the person you are talking to from Android must use the latest version of the Google Messages appThis app, and no other, is the one that integrates official support for RCS encryption according to the GSMA standard. If your contact uses another SMS/RCS messaging app, encryption may not be activated.
Finally, the two sides of the conversation must be connected through operators that support RCS Universal Profile 3.0 with encryptionApple indicates on its support website which carriers are compatible, and in Spain the list includes the major groups already mentioned. If either party's network is not ready, the chat will remain in RCS without E2EE or even via SMS.
When everything is in order, the system Enable default encryptionwithout the user needing to do anything special. However, if you want to check the status, you can go to Settings → Messages → RCS Messaging and verify that the option “End-to-end encryption (Beta)” It appears activated. Within the chat itself, the padlock icon is the visual confirmation that the protection is working.
It's important to note that the rollout is gradual. The option may be enabled on the system, but It took me a while to get to all the conversations as operators and devices are updated. In some European countries the process will be faster than in others, depending on the investment in each network.
Real impact on daily life and pending challenges
Activating end-to-end encryption in RCS has a clear symbolic component: it means that, for the first time, Apple and Google align on an open security standard for cross-platform messaging. But beyond the gesture, its practical impact will depend on how widely it spreads and whether users notice the change.
The clearest advantage is that the Conversations between iPhone and Android no longer go “half-protected”Until now, many users entrusted their sensitive information to third-party messaging apps, while native cross-platform messaging took a backseat. With RCS E2EE encryption enabled by default, the system offers a more secure alternative without requiring any user intervention.
However, there are obvious challenges. One of them is the dependence on operatorsUnlike iMessage, WhatsApp, or Signal, which operate directly between apps, RCS encryption requires the mobile network to be prepared for the appropriate profile. This means that the pace of implementation is not only determined by Apple and Google, but also by the telephone companies.
Another challenge is the user perceptionMany people don't distinguish between SMS, RCS, iMessage, or messages within other apps; they simply see a bubble on the screen. The small padlock icon and the communication provided by the companies themselves will be key for people to understand when their messages are truly secure and when they are not.
Despite these doubts, the movement reinforces the idea that the Integrated messaging in the operating system aims to regain relevanceRCS had already significantly improved the experience compared to traditional SMS; with end-to-end encryption between iPhone and Android, it gains a strong argument to compete in privacy and security with the major messaging apps that dominate the market.
Enabling end-to-end encryption for RCS messages with iOS 26.5 represents a profound change in communication between iPhone and Android: from now on, and provided the software and network requirements are met, cross-platform chats benefit from a layer of protection comparable to that of the most secure applications, strengthening the privacy of millions of users and finally aligning the two major players in the sector around a common standard.
