Messages now shows a lock icon in encrypted RCS threads, letting you verify, chat by chat, which conversations are protected. Apple restored end-to-end encryption for RCS in iOS 26.5 and added an explicit End-to-End Encryption toggle inside Messages. To get the safeguard you need an iPhone on a build that includes iOS 26.5, carrier and network support, and an Android contact using a compatible RCS client such as the updated Google Messages app. Follow the four practical steps below to update, check settings, and confirm the lock appears in cross-platform chats.

1. What changed in iOS 26.5 and why it matters

End-to-End Encryption for RCS is back in Apple’s software with the iOS 26.5 rollout. Multiple outlets describe the feature as a beta-level setting inside Messages that applies to conversations with Android users as well as iPhone-to-iPhone threads. Apple presents the control in Messages under the RCS settings as an End-to-End Encryption toggle, and encrypted threads show a visible lock symbol in the chat view so users can verify protection on a per-thread basis.

Reports say Apple first tested RCS E2EE in early developer betas, removed it before the iOS 26.4 stable release, and then returned the control in the iOS 26.5 beta while testing continued. One account of the rollout notes Apple’s developer documentation and third-party coverage flag the feature as beta in iOS 26.5, and that the encrypted indicator won't appear for every conversation immediately because carrier and device support must match on both ends.

Worked example. Imagine you and a friend swap messages between an iPhone and an Android phone. If both phones and the network support encrypted RCS, Messages will show a lock icon in the thread. You can confirm that the messages are encrypted without having to dive into cryptographic details.

2. Update to iOS 26.5 and find the RCS encryption control

Start by checking whether your iPhone can install the iOS 26.5 build. One report shows the standard Software Update path: open Settings, tap General, select Software Update, and follow the prompts to install an available iOS 26.5 build.

Sources describing the feature across beta coverage say some users saw the control during developer or public beta testing and that distribution method differed between outlets, so your device may or may not show the update immediately.

Once your phone runs a build with iOS 26.5, open Messages and look for an RCS submenu in the app’s settings. The End-to-End Encryption toggle appears under RCS settings. Multiple outlets noted the switch is presented as a simple on/off control and that in the beta it's switched on by default. If you see the option, the software side is present on your iPhone.

  • Checklist to follow: 1) Open Settings. 2) Tap General. 3) Tap Software Update. 4) Install iOS 26.5 if it’s available. 5) Open Messages and look for RCS or RCS Messaging in settings. 6) Confirm an End-to-End Encryption toggle.

Worked example. You open Settings, find Software Update, and install iOS 26.5. In Messages settings you find RCS Messaging, and a labelled toggle reads End-to-End Encryption. The toggle is on by default. That tells you the iPhone side is configured to support encrypted cross-platform chats, subject to carrier and contact support.

Mastheads

3. Carrier, device and contact compatibility in Canada

Encrypted RCS depends on more than just software on your iPhone. Apple and multiple reports emphasize that the feature requires support on both ends and on the network. That means the iPhone model, the carrier, and the Android contact’s client and carrier must all support encrypted RCS for the lock icon and protection to appear.

A Canadian compilation lists which providers Apple identifies as participating in the encrypted RCS beta and which aren't yet listed. The participating Canadian providers include Rogers, Bell, Telus, Freedom Mobile, SaskTel, Videotron, Fido, Koodo, Virgin Plus, Lucky Mobile, Public Mobile, and Chatr. The compilation lists Fizz, Eastlink, PC Mobile, Cityfone, Shaw Mobile, Tbaytel, and Xplornet as not listed as supporting the encrypted beta. That information comes from the single-source Canadian summary at iPhoneInCanada, which treated carrier participation as part of Apple’s rollout notes for the encrypted RCS beta.

  • Eligibility checklist for encrypted RCS: your iPhone must run a build with iOS 26.5; your carrier must be listed as participating in the encrypted RCS beta; the Android contact must use a compatible RCS client and have carrier-side support for encrypted RCS.

Here's the thing, worked example. You install iOS 26.5 and your carrier is on the participating list. Your Android friend is on a participating carrier and uses the updated Google Messages client. In that case, Apple is reported to enable encryption by default for supported carriers and to roll protection into conversations over time on supported networks and devices, so your cross-platform chats should display the encrypted indicator when the network updates have propagated.

4. What Android users must do and how to verify in a thread

On the Android side, encrypted cross-platform RCS requires an updated client and carrier support. One source states that the rollout is coordinated with Google Messages and that Android users need the latest Google Messages update to take part in encrypted RCS with iPhone users. Reporting across the beta coverage also stresses that RCS between Android users already supported E2EE in many cases, while iMessage has long used E2EE for iPhone-to-iPhone messaging. This change brings cross-platform parity where network and client support exist.

To verify encryption after updating, open Messages, locate the RCS Messaging section in Messages settings, and confirm that an End-to-End Encryption control is present. If a thread is encrypted, look for the lock icon or an encrypted label inside the chat view. Multiple accounts describe the lock symbol appearing in encrypted threads as the main in-chat verification mechanism.

  • Thread verification checklist: 1) Confirm your Messages settings include RCS Messaging and the End-to-End Encryption toggle. 2) Ask your Android contact to update Google Messages. 3) Confirm both carriers are listed as supporting encrypted RCS. 4) Open the cross-platform thread and look for a lock icon or an "encrypted" label.

Worked example. After both phones and carriers are updated, you reopen a cross-platform conversation and see a small lock icon beside the thread name. Tapping or viewing the thread shows a label that indicates encryption. That's the visual evidence that Apple and reporting say you should look for to confirm protection.

Multiple outlets covering the feature in March and April reported that Apple first tested E2EE for RCS in earlier developer betas, then removed it before iOS 26.4 released, and then returned it in the iOS 26.5 beta as testing continued. Reporting notes the feature remains designated as beta in iOS 26.5 documentation. Apple’s developer notes and third-party coverage caution that not all devices, carriers, or contacts will show the encrypted indicator immediately.

One practical implication is that encryption may appear gradually. Apple is reported to enable encryption by default for supported carriers and to roll the protection into new and existing conversations over time on supported networks and devices. That means even if your phone and carrier are ready, you may need to wait a short while for the encrypted label to appear in older threads as network updates propagate.

Worked example. You install iOS 26.5 and find the End-to-End Encryption toggle in Messages. Your carrier supports encrypted RCS, but a colleague on a different participating carrier doesn't see the lock in your thread immediately. After a period, their thread updates and the lock appears, showing the roll-out in action.

If you don't see the End-to-End Encryption toggle or the lock icon, run through this checklist based on reporting and Apple’s notes.

  • Your iPhone is running a build that includes iOS 26.5. Use Settings > General > Software Update to check and install available updates.
  • Your carrier is listed among participating providers. A Canadian compilation at iPhoneInCanada lists participating and non-participating carriers at the time of reporting.
  • Your Android contact is using an updated RCS client, such as the latest Google Messages build.
  • Your device model is supported by the beta-level rollout. Reporting indicates device and network pairing matters for cross-platform E2EE.
  • Wait a short period for the network-side rollout to enable encryption for new and existing conversations on supported networks and devices.

Worked example. If you confirm all items above and still don't see a lock icon in a thread, ask your contact to confirm their Google Messages update, and verify each party’s carrier is listed as participating. One or more missing elements on the checklist commonly explains why the encrypted label doesn't appear.

Related Articles

Open Settings, tap General, then Software Update to see whether an iOS 26.5 build is available. If it is, install it, then open Messages, find RCS Messaging in the app’s settings and confirm an End-to-End Encryption toggle is present. Finally, in a cross-platform thread with an Android contact who has updated Google Messages and uses a participating carrier, look for the lock icon or an "encrypted" label to verify protection.

This article was created with AI assistance.