Your iPhone Just Started Doing “Secure” Texts With Android—So Why Can Your Messages Still Downgrade to Plain SMS Without You Noticing?
RCS arrived—and encrypted RCS is rolling out—but your iPhone still routes messages one-by-one based on carrier support, eligibility, and connectivity. That’s why a chat can quietly slip back to SMS/MMS with little or no warning.
By TheMurrow Editorial
May 15, 2026
Key Points
- 1Understand the fallback: iPhone Messages routes each text via the best available transport, but can silently drop from RCS to SMS/MMS.
- 2Watch the real signals: green bubbles cover RCS and SMS; only thread indicators like Apple’s lock icon can confirm encrypted RCS.
- 3Expect gatekeepers: carrier support, iOS version, Android client, and “all participants” requirements decide whether RCS—and RCS encryption—actually works.
Your phone just did something you didn’t ask it to do: it quietly changed the kind of message you sent.
One moment you’re sharing a crisp photo, seeing typing bubbles, maybe even a lock icon that suggests modern encryption. The next, you’re back in the 1990s—plain SMS, with none of the protections or features people now assume are standard. No warning. No “Are you sure?” prompt. Often, no obvious visual clue.
That “downgrade” is the hidden story inside the long-running iPhone-versus-Android texting mess. Apple’s adoption of RCS—first as a feature upgrade in iOS 18, then as an encryption upgrade announced May 11, 2026—has moved cross-platform texting forward. But it hasn’t made it predictable.
You’re not choosing secure messaging once. Your phone is choosing—message by message—based on what’s available.
— — TheMurrow Editorial
If you’re wondering why iPhone-to-Android texts can still slip into SMS without you noticing, the answer is less about conspiracy and more about plumbing: different networks, different gatekeepers, and a design philosophy that prizes delivery over clarity.
The new baseline: RCS arrived on iPhone, but it didn’t replace SMS
Apple added RCS support to Messages on iPhone starting in iOS 18, depending on your carrier. RCS (Rich Communication Services) is the modern successor to SMS/MMS: better media sharing, read receipts, typing indicators, and other comforts that iMessage users have taken for granted for years. Apple documents these capabilities—and the carrier dependency—directly in its Messages support notes. (Apple Support: HT207006)
A key point for readers: RCS is not iMessage, and it’s not a single Apple-controlled network. Apple describes RCS as a carrier-provided service, which matters because it means your ability to use it can hinge on your carrier’s provisioning and partners. (Apple Support: HT207006)
A key point for readers: RCS is not iMessage, and it’s not a single Apple-controlled network. Apple describes RCS as a carrier-provided service, which matters because it means your ability to use it can hinge on your carrier’s provisioning and partners. (Apple Support: HT207006)
The most important date people missed: May 11, 2026
On May 11, 2026, Apple announced that end-to-end encrypted (E2EE) RCS messaging was beginning to roll out in beta, starting with iOS 26.5, for iPhone users on supported carriers and Android users on the latest Google Messages. (Apple Newsroom, May 11, 2026)
Apple said encryption would be on by default and would “automatically enable over time” for new and existing RCS conversations—again, within the constraints of eligibility. A new lock icon is meant to signal that an RCS chat is end-to-end encrypted. (Apple Newsroom, May 11, 2026)
Apple said encryption would be on by default and would “automatically enable over time” for new and existing RCS conversations—again, within the constraints of eligibility. A new lock icon is meant to signal that an RCS chat is end-to-end encrypted. (Apple Newsroom, May 11, 2026)
Encryption can be on by default—and still not be on for you.
— — TheMurrow Editorial
8
Statistic #1 (with context): The RCS story on iPhone has two milestones—iOS 18 for RCS support and iOS 26.5 for encrypted RCS beta—an eight major-iOS-version span before carrier rollout timelines.
What “downgrade to SMS” really means (and why it’s easy to miss)
People talk about messaging “downgrading” as if a secure system suddenly becomes insecure. The reality is more procedural: SMS/MMS and RCS are different transport systems. Your messaging app tries to send a message via the “best” available method for that recipient at that moment. If that method fails—because of carrier support, provisioning, or connectivity—it falls back to SMS/MMS.
Apple’s UI design adds a layer of confusion. iMessage is blue. Everything else is green. On iPhone, RCS and SMS/MMS both appear as green bubbles, so the color doesn’t reliably tell you whether you’re using modern features or older, unencrypted messaging. Apple’s own support documentation emphasizes bubble colors mainly as iMessage versus non‑iMessage, not “secure versus insecure.” (Apple Support: HT207006)
Apple’s UI design adds a layer of confusion. iMessage is blue. Everything else is green. On iPhone, RCS and SMS/MMS both appear as green bubbles, so the color doesn’t reliably tell you whether you’re using modern features or older, unencrypted messaging. Apple’s own support documentation emphasizes bubble colors mainly as iMessage versus non‑iMessage, not “secure versus insecure.” (Apple Support: HT207006)
The problem isn’t only technical; it’s also interface
Even when platforms offer indicators, they can be subtle. Apple says users will see a lock icon to indicate end-to-end encrypted RCS. That helps, but it also creates a new ambiguity: when the lock isn’t there, are you still on RCS (just not encrypted), or did you fall back to SMS/MMS? The answer can vary by carrier support and the other person’s setup. (Apple Newsroom, May 11, 2026; Apple Support: HT207006)
Green bubbles don’t mean one thing anymore. They mean ‘not iMessage,’ and that’s a much bigger bucket.
— — TheMurrow Editorial
1
Statistic #2 (with context): Apple’s lock icon is one symbol representing a multi-party requirement—iOS 26.5 + supported carrier(s) + compatible Android client + all participants eligible—so its absence can’t explain which link failed.
Carrier gatekeeping: the hidden decider of whether RCS works at all
Apple is unusually blunt about the dependency: RCS is carrier-provided. If your carrier doesn’t support RCS on iPhone, the RCS option may not even appear, and iPhone-to-Android messages default to SMS/MMS. (Apple Support: 122195; Apple Support: HT207006)
That’s the first gate. The second gate is encryption.
Apple’s May 2026 announcement frames encrypted RCS as broadly rolling out, but Apple’s support language is specific about the constraints: E2EE for RCS requires iOS 26.5 and carrier support, and “all participants” must be on carriers that support encryption. (Apple Support: HT207006)
That’s the first gate. The second gate is encryption.
Apple’s May 2026 announcement frames encrypted RCS as broadly rolling out, but Apple’s support language is specific about the constraints: E2EE for RCS requires iOS 26.5 and carrier support, and “all participants” must be on carriers that support encryption. (Apple Support: HT207006)
Why “all participants” matters more than people expect
Group chats expose the rule most clearly. One person on an unsupported carrier—or using a client that doesn’t meet the requirements—can prevent an RCS thread from being end-to-end encrypted, and in some scenarios may force the conversation into a less capable mode.
That’s not Apple being petty. It’s how interoperable encryption works: the system can’t claim end-to-end protection unless every endpoint can actually do it.
That’s not Apple being petty. It’s how interoperable encryption works: the system can’t claim end-to-end protection unless every endpoint can actually do it.
2+
Statistic #3 (with context): Encrypted cross-platform RCS demands alignment across at least two carrier accounts (yours and the recipient’s), plus compatible software—so the other person’s setup can still dictate the lane.
Data vs. signaling: why RCS can fail when SMS still goes through
The most practical explanation for “why did my message change types?” is simple: RCS rides on IP/data, while SMS rides on the cellular signaling infrastructure. When data connectivity is unreliable, SMS can be the fallback that still “just works.”
Google’s own help documentation acknowledges the real-world consequence: when someone loses mobile/Internet service, messages “can’t always be delivered immediately,” and users can switch from RCS to SMS/MMS as an alternative delivery method. (Google Messages Help: answer/10253274)
That statement isn’t a dunk on RCS. It’s an admission that RCS, like other data-based messaging, inherits the fragility of data coverage, Wi‑Fi handoffs, and provisioning hiccups.
Google’s own help documentation acknowledges the real-world consequence: when someone loses mobile/Internet service, messages “can’t always be delivered immediately,” and users can switch from RCS to SMS/MMS as an alternative delivery method. (Google Messages Help: answer/10253274)
That statement isn’t a dunk on RCS. It’s an admission that RCS, like other data-based messaging, inherits the fragility of data coverage, Wi‑Fi handoffs, and provisioning hiccups.
Case study: the elevator, the stadium, the rural dead zone
You’ve seen this movie:
- You’re in an elevator leaving a parking garage.
- You’re at a crowded stadium where data bogs down.
- You’re driving through a rural area where LTE is spotty but basic cellular service remains.
In each case, the phone may fail to establish or maintain the IP session needed for RCS. The app’s priority becomes delivery, and SMS/MMS becomes the path of least resistance. The design goal is understandable. The trade-off is invisibility: the user experiences a “message send” but not a “security state changed.”
- You’re in an elevator leaving a parking garage.
- You’re at a crowded stadium where data bogs down.
- You’re driving through a rural area where LTE is spotty but basic cellular service remains.
In each case, the phone may fail to establish or maintain the IP session needed for RCS. The app’s priority becomes delivery, and SMS/MMS becomes the path of least resistance. The design goal is understandable. The trade-off is invisibility: the user experiences a “message send” but not a “security state changed.”
2
Statistic #4 (with context): The architecture forces a choice between two distinct delivery systems—IP for RCS and signaling for SMS—so every message becomes a routing decision under changing conditions.
The background checks you never see: capability discovery and interoperability
Messaging apps don’t guess whether RCS will work. They check.
Google’s documentation explains that when RCS chats are on, Google checks contacts to see if they can use RCS chats, and those checks may involve Google’s RCS infrastructure and other providers. (Google Messages Help: answer/9487020)
That’s a technical necessity—messages have to be routed correctly. It’s also a reason users experience inconsistent behavior: capability can change as people switch phones, reinstall apps, change carriers, toggle settings, travel internationally, or lose provisioning.
Google’s documentation explains that when RCS chats are on, Google checks contacts to see if they can use RCS chats, and those checks may involve Google’s RCS infrastructure and other providers. (Google Messages Help: answer/9487020)
That’s a technical necessity—messages have to be routed correctly. It’s also a reason users experience inconsistent behavior: capability can change as people switch phones, reinstall apps, change carriers, toggle settings, travel internationally, or lose provisioning.
What this means for “downgrades”
When your phone can’t confirm that RCS is available for a recipient—or can’t complete the authentication or setup—your messaging app tends to choose the conservative option: SMS/MMS. Many apps do this silently because the alternative is a message that fails to send at all.
From a product standpoint, silent fallback reduces support tickets. From a privacy standpoint, it creates a hazard: you may assume modern protections that aren’t active.
From a product standpoint, silent fallback reduces support tickets. From a privacy standpoint, it creates a hazard: you may assume modern protections that aren’t active.
Encryption isn’t a mood; it’s a set of requirements (and a small icon)
Apple’s May 2026 announcement sets expectations: encrypted RCS is rolling out in beta, encryption is on by default, and a lock icon will indicate end-to-end encryption. (Apple Newsroom, May 11, 2026)
Apple’s support language adds the boundary conditions: E2EE depends on iOS 26.5, supported carriers, and all participants meeting the bar. (Apple Support: HT207006)
Those two statements can both be true—and still leave many users in mixed states for months: some chats encrypted, some RCS-but-not-encrypted, some falling back to SMS/MMS.
Apple’s support language adds the boundary conditions: E2EE depends on iOS 26.5, supported carriers, and all participants meeting the bar. (Apple Support: HT207006)
Those two statements can both be true—and still leave many users in mixed states for months: some chats encrypted, some RCS-but-not-encrypted, some falling back to SMS/MMS.
Expert quote (Apple): carrier-provided and requirement-heavy
Apple’s support documentation frames the power dynamics directly: “RCS is a carrier-provided service” and encrypted RCS requires carrier support and participant compatibility. (Apple Support: HT207006)
That’s the core explanation for why “Apple added it” doesn’t equal “everyone has it,” and why messaging can revert without the sender consciously doing anything.
That’s the core explanation for why “Apple added it” doesn’t equal “everyone has it,” and why messaging can revert without the sender consciously doing anything.
Expert quote (Google): service loss and alternative delivery
Google’s help documentation spells out the user-facing symptom: when mobile/Internet service is lost, RCS messages may not be delivered immediately, and users can switch to SMS/MMS. (Google Messages Help: answer/10253274)
Taken together, Apple and Google are describing the same reality from different ends: the system routes around failure. The cost is that the user may not notice the route changed.
Taken together, Apple and Google are describing the same reality from different ends: the system routes around failure. The cost is that the user may not notice the route changed.
Practical takeaways: how to tell what you’re sending—and how to reduce surprises
You can’t control carrier provisioning from your couch. You can control what you look for and how you communicate sensitive information.
Look for thread-level indicators, not bubble color
On iPhone, green bubbles cover multiple possibilities. Use better signals:
- Look for Apple’s lock icon in an RCS chat to confirm end-to-end encryption (where available). (Apple Newsroom, May 11, 2026)
- Pay attention to whether you’re getting RCS features (richer media handling, read receipts/typing indicators), which can suggest RCS is active—but remember: features don’t automatically mean E2EE.
- Look for Apple’s lock icon in an RCS chat to confirm end-to-end encryption (where available). (Apple Newsroom, May 11, 2026)
- Pay attention to whether you’re getting RCS features (richer media handling, read receipts/typing indicators), which can suggest RCS is active—but remember: features don’t automatically mean E2EE.
Don’t assume yesterday’s settings apply today
RCS availability can change due to:
- a carrier change or plan reprovisioning
- traveling and roaming conditions
- intermittent data connectivity
- the other person switching devices or messaging apps
The same contact can be reachable via RCS in the morning and only via SMS at night, without either of you “changing anything” on purpose.
- a carrier change or plan reprovisioning
- traveling and roaming conditions
- intermittent data connectivity
- the other person switching devices or messaging apps
The same contact can be reachable via RCS in the morning and only via SMS at night, without either of you “changing anything” on purpose.
Case study: the “sensitive photo” mistake
Imagine texting a document photo (passport, medical form, legal letter) from an iPhone to an Android phone.
- If encrypted RCS is active, the risk profile is meaningfully improved.
- If the conversation quietly fell back to SMS/MMS, the message may travel through older systems with far weaker protections.
The lesson isn’t paranoia. It’s verification. For high-stakes material, confirm the indicator (such as the lock icon) or choose a messaging channel where you can clearly verify end-to-end encryption state.
- If encrypted RCS is active, the risk profile is meaningfully improved.
- If the conversation quietly fell back to SMS/MMS, the message may travel through older systems with far weaker protections.
The lesson isn’t paranoia. It’s verification. For high-stakes material, confirm the indicator (such as the lock icon) or choose a messaging channel where you can clearly verify end-to-end encryption state.
Key Insight
For anything sensitive, treat a green-bubble thread as unknown transport until you’ve confirmed the thread’s encryption indicator (like Apple’s lock icon).
A reasonable standard for readers
If the content would be damaging if intercepted—financial details, intimate images, sensitive professional information—treat “green bubble” as “unknown transport” until you’ve confirmed the thread’s security indicator.
That’s not a romantic vision of frictionless messaging. It’s a realistic one.
That’s not a romantic vision of frictionless messaging. It’s a realistic one.
The bigger picture: delivery-first design versus informed consent
Silent fallback is an engineering compromise that became a policy. Messaging apps are built to deliver messages even under imperfect conditions, and SMS remains the universal denominator.
Apple’s recent moves—RCS in iOS 18, encrypted RCS beta beginning with iOS 26.5—show a clear direction: cross-platform messaging should be richer and more private. (Apple Support: HT207006; Apple Newsroom, May 11, 2026)
Yet Apple’s own caveats explain why the messy middle won’t disappear overnight: carrier support, partner infrastructure, and multi-party requirements make “secure by default” a gradual, uneven reality.
The result is a new kind of confusion. People used to equate green bubbles with “Android.” Now green bubbles can mean RCS with modern features, RCS with encryption (sometimes), or plain SMS/MMS—and the app may move between them as conditions change.
The right response isn’t to despair about standards. It’s to demand clarity in interfaces and to cultivate a small habit of verification when it matters.
Apple’s recent moves—RCS in iOS 18, encrypted RCS beta beginning with iOS 26.5—show a clear direction: cross-platform messaging should be richer and more private. (Apple Support: HT207006; Apple Newsroom, May 11, 2026)
Yet Apple’s own caveats explain why the messy middle won’t disappear overnight: carrier support, partner infrastructure, and multi-party requirements make “secure by default” a gradual, uneven reality.
The result is a new kind of confusion. People used to equate green bubbles with “Android.” Now green bubbles can mean RCS with modern features, RCS with encryption (sometimes), or plain SMS/MMS—and the app may move between them as conditions change.
The right response isn’t to despair about standards. It’s to demand clarity in interfaces and to cultivate a small habit of verification when it matters.
1) Why do my iPhone messages to Android sometimes send as SMS instead of RCS?
Because RCS availability depends on carrier support and active data connectivity. Apple describes RCS as a carrier-provided service, so if RCS isn’t supported or can’t be established at that moment, Messages may fall back to SMS/MMS to ensure delivery. (Apple Support: HT207006; Apple Support: 122195)
2) Are green bubbles on iPhone now encrypted?
Not necessarily. On iPhone, RCS and SMS/MMS are both green, and only iMessage is blue. Green tells you “not iMessage,” not “encrypted.” For encrypted RCS (where available), Apple says a lock icon will indicate end-to-end encryption. (Apple Support: HT207006; Apple Newsroom, May 11, 2026)
3) When did Apple add RCS—and when did encrypted RCS start?
Apple added RCS support starting in iOS 18 (carrier-dependent). Apple announced on May 11, 2026 that end-to-end encrypted RCS began rolling out in beta starting with iOS 26.5, for supported carriers and compatible Android users on the latest Google Messages. (Apple Support: HT207006; Apple Newsroom, May 11, 2026)
4) Why would an RCS chat not be end-to-end encrypted even if RCS works?
Because encryption has extra requirements. Apple says encrypted RCS depends on iOS 26.5, supported carriers, and that all participants must be on carriers that support encryption. If any requirement isn’t met, the chat may be RCS without E2EE, or may fall back to SMS/MMS if RCS can’t be established. (Apple Support: HT207006)
5) Can poor reception cause a downgrade to SMS?
Yes. RCS relies on mobile data or Wi‑Fi, and Google notes that if someone loses mobile/Internet service, messages may not be delivered immediately and users can switch to SMS/MMS as an alternative. SMS uses the cellular signaling system and can sometimes go through when data-based services struggle. (Google Messages Help: answer/10253274)
6) How can I tell if an iPhone-to-Android conversation is encrypted?
Apple says encrypted RCS will show a lock icon in the chat. Without that indicator, you should not assume end-to-end encryption is active. Bubble color won’t help, because non‑iMessage chats—both RCS and SMS/MMS—are green on iPhone. (Apple Newsroom, May 11, 2026; Apple Support: HT207006)
7) Is Apple fully in control of whether RCS and RCS encryption work?
No. Apple explicitly frames RCS as carrier-provided, with setup and authentication relying on carriers and partners. That’s why two users with the same iPhone model can have different outcomes depending on carrier support and the other participant’s carrier and messaging client. (Apple Support: HT207006; Apple Support: 122195)
Editor’s Note
This article describes why iPhone-to-Android messaging can shift between encrypted RCS, unencrypted RCS, and SMS/MMS depending on carrier support, eligibility, and real-time connectivity—often without obvious UI feedback.
Quick verification habits (when it matters)
- ✓Look for the lock icon before sending sensitive material
- ✓Treat green bubbles as “not iMessage,” not as “secure”
- ✓Expect availability to change with travel, roaming, and data reliability
- ✓Assume group chats are only as secure as the least-compatible participant
T
About the Author
TheMurrow Editorial is a writer for TheMurrow covering how-to / guides.
Frequently Asked Questions
Why do my iPhone messages to Android sometimes send as SMS instead of RCS?
Because RCS availability depends on carrier support and active data connectivity. If RCS can’t be established, Messages may fall back to SMS/MMS to ensure delivery. (Apple Support: HT207006; Apple Support: 122195)
Are green bubbles on iPhone now encrypted?
Not necessarily. Green means “not iMessage,” and both RCS and SMS/MMS are green. Apple says a lock icon indicates end-to-end encrypted RCS where available. (Apple Support: HT207006; Apple Newsroom, May 11, 2026)
When did Apple add RCS—and when did encrypted RCS start?
Apple added RCS support starting in iOS 18 (carrier-dependent). On May 11, 2026, Apple announced end-to-end encrypted RCS began rolling out in beta starting with iOS 26.5 for supported carriers and compatible Android users. (Apple Support: HT207006; Apple Newsroom, May 11, 2026)
Why would an RCS chat not be end-to-end encrypted even if RCS works?
Encryption has extra requirements: iOS 26.5, supported carriers, and all participants on carriers that support encryption. If any requirement isn’t met, the chat may be RCS without E2EE or may fall back to SMS/MMS. (Apple Support: HT207006)
Can poor reception cause a downgrade to SMS?
Yes. RCS relies on mobile data or Wi‑Fi; if Internet service is lost, delivery can fail or delay, and SMS/MMS may be used instead. SMS can sometimes work when data struggles. (Google Messages Help: answer/10253274)
How can I tell if an iPhone-to-Android conversation is encrypted?
Apple says encrypted RCS will show a lock icon in the chat. Without it, don’t assume end-to-end encryption is active; bubble color won’t distinguish RCS from SMS/MMS. (Apple Newsroom, May 11, 2026; Apple Support: HT207006)
