Verified 19 August 2026
Every menu path, status name and encryption claim quoted from Google or Apple
Updated August 2026 · Every menu path, status name and encryption claim below is quoted from Google's or Apple's own page, read on 19 August 2026 · the encryption section now carries the 11 May 2026 announcement and its conditions
RCS is the one to leave on because Google's help page, read 19 August 2026, lists read receipts, typing indicators and sharper media that SMS cannot carry. SMS is the fallback worth keeping because it needs no data at all, where Google says RCS travels over Wi-Fi and mobile data. Encryption is the claim to check because Apple and Google, announcing it on 11 May 2026, called it a beta needing iOS 26.5 and a supporting carrier at both ends. Data checked: 19 August 2026.
Two systems carry the messages in your Android inbox, and your phone switches between them without asking. One works on a bar of signal and nothing else. The other needs an internet connection and gives you everything people expect from a modern messaging app. The part worth reading carefully is the last one, because what is encrypted today is narrower than most write-ups say, and both vendors are explicit about the limits on their own pages.
The old channel
SMS stands for Short Message Service, and it runs over the cellular network rather than the internet. That is its one real advantage and it is a big one: with a bar of signal and no data at all, a plain text still goes through.
The famous limit is real but it is not one number. Android's own SmsMessage reference publishes both: the maximum payload is 160 septets per message, and 153 per message once a user data header is present, which is exactly what a concatenated long message uses. So a short text gets 160 characters; the moment it is long enough to split, every part carries 153. Type in an alphabet outside the 7-bit set and the payload is counted in bytes instead, capped at 140, which is why an emoji or an accented character shortens a text so sharply.
Photos and video go through MMS, the older sibling standard, at a size your carrier decides. There are no read receipts and no typing indicators. And there is no end-to-end encryption, which both vendors state on their own pages rather than leaving to inference: Apple writes that SMS and MMS 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", and Google's encryption help page says flatly that "End-to-end encryption isn't available for SMS/MMS messages".
What RCS adds
RCS stands for Rich Communication Services, and Google Messages labels the feature "RCS chats". Rather than paraphrase what it adds, here is Google's own list, read 19 August 2026: share high-resolution photos and videos, know when someone is typing, get read receipts, send messages over mobile data and Wi-Fi, and rename, edit or remove yourself from group chats.
Two conditions come attached to that list on the same page, and both matter more than any feature on it. Google says RCS chats "will be turned on only when all the participants in a conversation have RCS", and that "Availability of RCS varies by region and carrier". This is not a capability your phone simply has, the way it has a cellular radio. It is a service your carrier provides, and the other person has to have it too.
Apple's side is documented just as plainly. On its comparison page Apple says RCS supports "delivery and read receipts and typing indicators", that "RCS messages appear in green text bubbles on your device", and that to use it "you need iOS 18 and a text-messaging plan from a carrier that supports RCS on iPhone". Apple also warns that "There may be a delay of a few hours in activating RCS", which is worth knowing before you conclude that something is broken.
The app itself is not the variable most people assume. Google Messages carries 4.3 stars from 45,155,464 ratings on a 10,000,000,000+ install badge, free with no ads and no in-app purchases, listing updated 12 August 2026 and checked 19 August 2026 on its Play listing. Its Data safety section says the app may share and may collect data, and it carries an independent security review badge.
Which one am I on
The page you are probably looking for is this one, and the tells are not the ones most guides print.
To check the account status, Google's own steps are: open Google Messages, at the top right tap your Profile picture or Initial, then Messages settings, then RCS chats. Google adds that if you cannot find "RCS chats", tap Chat features instead.
The four statuses Google publishes, in its own words: Connected, "You can use RCS chats with other people who have them turned on". Connecting, "Your phone number is under verification. Please wait". Trouble connecting. Awaiting retry, an issue with verification, and Google says that if it lasts more than 30 minutes you should tap Details and submit feedback. Not supported, "You can't use RCS chats", where Google tells you to check your internet connection. A separate message, "RCS chats are disabled by your carrier", is the one that means you should contact the carrier rather than keep retrying.
One troubleshooting step Google documents that almost nothing else mentions: on a dual SIM phone with both SIMs inserted, your Call SIM has to be configured as your Data SIM, under Settings then Network and internet.
When it drops
A single thread can switch between the two systems without a clear warning, which is the part people find confusing. Your message drops to SMS when the other person does not have RCS, when either side has no data or Wi-Fi, or when an RCS message fails and is resent as a text.
That last case is a setting, not fate, and the page in front of you probably never mentioned it. Google names it in its RCS FAQ: under Messages settings, then RCS chats, there is a toggle called Automatically resend as text (SMS/MMS), which you can turn on or off. There is also a Resend messages choice for how a failed message should go out.
One resend option carries a warning from Google itself. On the same help page, read 19 August 2026: "If you choose the option to send as 'SMS with a link,' your media could be accessible by a public link not controlled by Google." If you send photos you would not put on the open web, that is the option to leave alone.
Do not toggle RCS off and on to troubleshoot. Google's warning is unusually blunt for a help page: "It's not advised to turn RCS chats on and off. If you do, you'll be removed from group chats." Google lists the narrow cases where turning it off is right, all of them about leaving a device behind: swapping to a phone without RCS, switching messaging apps, or losing a phone while keeping the number.
What it costs
Because RCS runs over the internet, it needs a connection, and Google says so in the plainest possible way by listing "Send messages over mobile data and Wi-Fi" as one of the things RCS gives you. The practical consequences run both directions.
On the good side, RCS works over Wi-Fi where the cellular signal is too weak for anything else. On the other side, if you have a signal for calls but no data, RCS will not send and your message reverts to SMS. Google's own RCS FAQ answers the case directly: if you do not have data, or the recipient is not online, "Google Messages can still be sent as SMS or MMS".
The billing difference follows from the same fact. RCS media travels over your data connection and counts against a data allowance the way any messaging app's media does; SMS does not, because it never touches the data channel. For text alone the difference is negligible. For a habit of trading videos it is not, and Wi-Fi is the answer rather than turning RCS off.
What is protected
Cross-platform encrypted RCS is real and it is dated. Both companies announced it on the same day, and both used the same word for its status.
The announcement. On 11 May 2026, Apple's newsroom post and Google's Android blog said the same thing. Apple's wording: "Starting today, end-to-end encrypted RCS messaging begins rolling out in beta for iPhone users running iOS 26.5 with supported carriers and Android users on the latest version of Google Messages." Apple adds the part that answers the question most people actually have: "Encryption is on by default and will be automatically enabled over time for new and existing RCS conversations."
So the honest summary is not that nothing has happened. It is that four conditions have to line up at once, and you control only two of them: iOS 26.5 or later on the iPhone, a current Google Messages on the Android side, and a carrier that supports it at both ends. Everything below is those conditions in the vendors' own words.
What Google says. Its encryption help page, read 19 August 2026: "Google Messages supports end-to-end encryption when messaging other users using Google Messages over Rich Communication Services (RCS)." The conditions are listed as a requirement on both sides: you and the person or group you message must both use the Google Messages app, have RCS chats turned on, and use data or Wi-Fi. Google adds that "RCS conversations between Google Messages users default to end-to-end encryption", and that the key "is not shared with Google, anyone else, or other devices".
What Apple says. The dates first, from Apple's own release notes and security releases list: RCS reached the iPhone in iOS 18 on 16 September 2024, and encrypted RCS arrived with iOS 26.5 on 11 May 2026, whose release note reads "End-to-end encrypted RCS messaging (beta) in Messages is available with supported carriers and will roll out over time". The current release is iOS 26.6.1, from 17 August 2026, so the requirement in practice is iOS 26.5 or later. On its comparison page, read 19 August 2026, Apple repeats it: "Starting with iOS 26.5, end-to-end encrypted RCS messaging (Beta) in Messages is available with supported carriers and will roll out over time." Apple states the dependency twice: "RCS messages can be end-to-end encrypted when all participants have carriers that support encryption", and "Even if your carrier supports encrypted RCS messages, the encryption of each RCS conversation depends on whether your contact's carrier also supports it." Apple's indicator is its own: an encrypted conversation "show[s] 'Encrypted' with a lock icon at the top", and Apple says that if you do not see it, "your RCS messages aren't protected from a third-party reading them while they're sent between devices".
Note the gap between the announcement and the help centres. Three months after launch, Apple's own pages still call it a beta that "will roll out over time", and Google's help centre still describes end-to-end encryption in terms of two people who both use Google Messages, without mentioning the iPhone case at all. That is documentation lagging a rollout rather than a contradiction, but it is why you should not read "encrypted now" as covering every chat you have. Check for the indicator in the conversation rather than assuming, and check your own carrier: Apple keeps a per-carrier feature list for the United States and Canada, read 19 August 2026, on which "End-to-end encrypted RCS messaging (beta)" appears against each carrier that has it.
Two limits both companies agree on, and they are the ones that bite. Encryption never covers a message that went out as SMS or MMS: Google says it "isn't available" for those, and Apple says they "aren't end-to-end encrypted". And if a conversation loses RCS, Google says the lock disappears from the send button and the timestamp, which is the signal to look for before you type something sensitive.
Where it still leaks
If privacy is why you are reading this, the honest summary is that encrypted RCS is a real improvement on SMS and still not the same thing as a messenger built for the job.
The reason is structural rather than a flaw in anyone's code. RCS is a carrier service. Apple describes what that means for identifiers in a sentence worth reading twice: when your device connects, "User identifiers are exchanged for your carrier and their partners to authenticate your device and provide a connection. These identifiers include your phone number and, depending on your carrier, your current IP address." Encryption protects the contents of the message. It does not remove the carrier from the path, and it does not cover the fact that the conversation happened.
Add the two conditional pieces above, that encryption depends on software versions and on carriers, and that any fallback to SMS is unprotected, and the position is clear enough: leave RCS on, look for the indicator, and use a purpose-built encrypted messenger when you need certainty rather than a good default. For the alternatives, our notes on private texting on Android cover what SMS cannot do, our roundup of free messaging apps for Android covers the wider field, and the communication hub ties the messaging, calling and privacy guides together.
One last thing SMS is still uniquely good for, and uniquely bad for: it reaches every phone and verifies nothing, which is why it remains the channel scammers use. If your inbox is filling with junk texts, our guide to stopping spam calls and texts on Android covers the blocking and reporting steps.
Look at the send icon and the colour. Google documents that the send icon in the compose bar shows the method, with three states: send by Wi-Fi or mobile data, send by SMS, and send by MMS. Google also says text messages are dark blue in the RCS state and light blue in the SMS or MMS state. For the account level view, open Google Messages, tap your profile picture, then Messages settings, then RCS chats, and look for Connected. Checked 19 August 2026.
It began on 11 May 2026, in beta. Apple and Google announced it the same day, and Apple's wording is that it rolls out "for iPhone users running iOS 26.5 with supported carriers and Android users on the latest version of Google Messages", with encryption "on by default". The condition that decides your case is the carrier one, and it applies at both ends: Apple says the encryption of each conversation depends on whether your contact's carrier supports it too. Look for the lock in the conversation rather than assuming. Checked 19 August 2026.
That the conversation is end-to-end encrypted at that moment. Google says you get a lock on the send button and next to the message timestamp, and an "RCS chat with" header. Apple shows the word Encrypted with a lock at the top. Apple is explicit about the reverse: if you do not see the indicator, your RCS messages are not protected from a third party reading them in transit. Checked 19 August 2026.
Only when it fits in one message. Android's own SmsMessage reference gives a maximum of 160 septets per message, and 153 per message once a user data header is present, which is what a long concatenated text uses. So a message that splits carries 153 characters per part, not 160. Messages using characters outside the 7-bit alphabet are counted in bytes instead, capped at 140. Checked 19 August 2026.
Yes. Google lists sending messages over mobile data and Wi-Fi as one of the things RCS gives you, so media counts against a data allowance the way any messaging app's media does. SMS does not, because it never uses the data channel. If you have no data and no Wi-Fi, Google says messages can still be sent as SMS or MMS. Checked 19 August 2026.
Google advises against toggling it. Its own help page says it is not advised to turn RCS chats on and off, and that if you do, you will be removed from group chats. Google lists the narrow cases where turning it off is right, and they are all about leaving a device behind: moving to a phone without RCS, switching messaging apps, or losing a phone while keeping the number. For data alone, use Wi-Fi for video instead. Checked 19 August 2026.
Yes. Google says RCS chats turn on only when all the participants in a conversation have RCS, and that when you or the recipient are offline, messages can still be sent as SMS or MMS. There is a setting for this, Automatically resend as text (SMS/MMS), under Messages settings then RCS chats. You lose read receipts, typing indicators and full quality media for that conversation. Checked 19 August 2026.
Checked 19 August 2026: the encryption section is rebuilt on the primary announcements it never cited. The page was right that cross-platform encrypted RCS arrived in May 2026 and right that it is on by default, and both are now sourced: Apple's newsroom and Google's Android blog, both dated 11 May 2026, say it "begins rolling out in beta for iPhone users running iOS 26.5 with supported carriers and Android users on the latest version of Google Messages", and Apple adds that "Encryption is on by default". What the page omitted is the conditions, which are what decide whether any given chat is covered: it is a beta three months on, it needs iOS 26.5 or later, and it needs a supporting carrier at BOTH ends, a dependency Apple states twice. The page now carries the announcement, the conditions, and a link to Apple's per-carrier list so a reader can check their own. The encryption indicator was Apple's, presented as universal: Google documents a lock on the send button and beside the timestamp, plus an "RCS chat with" header, and separately that messages are dark blue in the RCS state and light blue in SMS or MMS. The send button labels the page printed, "RCS message" and "Chat message", are published by nobody; Google documents a send icon with three states, "Send by Wi-Fi or mobile data", "Send by SMS" and "Send by MMS". The flat 160 character limit is right only for a message that does not split: Android's own SmsMessage reference gives 160 septets per message and 153 once the concatenation header is present. The RCS status names have been corrected to Google's exact wording, including the 30 minute threshold on "Trouble connecting. Awaiting retry" and the separation of "Not supported" from "RCS chats are disabled by your carrier". Three things Google publishes were missing entirely and are now on the page: that turning RCS off and on removes you from group chats, that the "SMS with a link" resend option can make your media "accessible by a public link not controlled by Google", and the Automatically resend as text toggle itself. A first-person aside was removed. A decision table, an "Our answer" capsule, a dated verification box and this changelog are new.
The Best Free Messaging Apps for Android in 2026Communication