Why Group Chats Break When Someone Has a Different Phone

Short answer

A group chat only keeps its modern features while every single participant can use the same modern protocol. One person who cannot — old phone, RCS off, a texting app that does not support it, a carrier that has not provisioned it — drops the whole group to MMS. It happens silently, it affects everyone equally, and there is no way to run the group half-and-half.

The rule that explains everything

Group messaging has one rule that, once you know it, explains every complaint you have ever had about a mixed group chat:

A group runs at the level of its least capable participant.

Not at the level of the person who created it, not at the level of the majority, and not per-person. One protocol carries the whole group, and it has to be one that every single participant can receive. Add one person who cannot do RCS and the entire group falls back to MMS — for everyone, including the eleven people with brand-new phones.

This is not a bug and it is not anyone being lazy. There is genuinely no way to send one message that arrives as a rich group message for some recipients and a plain one for others while remaining a single coherent conversation. The moment you try, replies stop threading and the group stops being a group.

The reason it feels like a bug is that nothing tells you it happened. The group looks the same. It just quietly gets worse, and everyone blames their own phone.

What actually disappears

The differences between a modern group and an MMS group are larger than most people realise, because the MMS version of a group is barely a group at all. Technically, an MMS “group” is just a message addressed to several numbers at once. There is no group object anywhere — no server knows the group exists.

That single fact explains all of the following:

The group has no name. You cannot name it, and if it had a name it loses it. There is nothing to attach a name to.

You cannot leave. This is the one that generates real frustration. There is no group to leave — you would have to persuade every other participant to stop including your number. Muting is your only option.

Nobody can be added or removed. Changing the participant list creates a different thread, which is why mixed groups have a habit of splitting into near-duplicate conversations.

Photos and video are crushed. MMS has a size cap measured in about a megabyte, and it applies to group messages the same as any other. This is the most visible symptom and the one people complain about first. The full explanation is here.

Reactions become text. Someone taps a heart and everyone receives a separate message saying that they loved something. In a group of eight, one reaction to one photo produces eight notifications. Why that happens.

No typing indicators, no read receipts, no reliable delivery status. None of those exist in MMS.

Replies do not thread. Threaded replies need a way to reference an earlier message, and MMS has none.

Finding the person who is dragging it down

Before you can do anything, you need to know who it is. There is no built-in way to see this, which is maddening, but there are reliable signals.

Check your one-to-one chats with each member. This is the practical method. If your direct conversation with someone is modern and healthy — typing indicators, sharp photos — that person is not your problem. Work through the group one person at a time and the culprit usually emerges quickly.

Look for the recent addition. If the group was fine last month and is broken now, ask what changed. The usual answers are: someone new joined, someone changed phones, or someone moved carrier. All three do it.

Suspect the person with the oldest phone, and the person on a budget carrier brand. A resold or prepaid line often does not get RCS even though the handset supports it perfectly well, which makes it invisible as a cause — the phone looks fine because it is fine.

Suspect a non-standard texting app. Someone using a third-party SMS app instead of the default one will not be doing RCS, regardless of how new their phone is.

The three ways out, and what each costs

There are exactly three realistic options and each one has a real price. Anyone offering you a fourth is selling something.

Option one: fix the person

Find whoever cannot do RCS and help them turn it on. This is the only option that keeps the group intact with everyone in it, and when it works it is clearly the best outcome.

The cost: it depends on someone else doing something, and it may not be possible at all. If their line is not provisioned by their carrier, there is nothing to switch on. Our guides on turning RCS on and registration getting stuck are what to send them.

Option two: move the group to an app

WhatsApp, Signal, Telegram, Discord — pick one. All of them work identically on every platform, because they are not trying to bridge two different phone ecosystems. Everything works: names, leaving, reactions, full-quality photos, and end-to-end encryption in the cases that offer it.

The cost: everyone has to install it and remember to check it. In practice one or two people never migrate, and you end up maintaining two groups. This works best when the group has a clear organiser who will chase people.

Option three: accept it

Keep the group on MMS and adjust expectations. Send photos individually to the people who need them at full quality. Do not react to things. Mute it.

The cost: obvious. But it is the correct answer more often than people admit, particularly for a group that exists to coordinate one event and will be dead in a fortnight. Not every group is worth a migration project.

A note on all-iPhone groups

If everyone in the group has an iPhone, the group runs on iMessage and none of this applies — that is why mixed groups feel like such a downgrade to people who are used to all-iPhone ones.

Add one Android phone and the group leaves iMessage entirely. It does not become a half-iMessage group. If everyone including the new person can do RCS, the group lands on RCS and keeps most of its features. If they cannot, it lands on MMS and loses nearly all of them. That fork — RCS or MMS — is exactly what our checker is for, and it is worth running before you conclude that adding one Android friend has ruined everything. Increasingly, it has not.

Check your own setup

Set the conversation type to a group and see exactly which features survive and which ones do not.

Run the checker

Version facts on this page: not verified yet — the site-wide verification pass has not been completed. See the update log

Related guides

Published 1 September 2026. Last reviewed 1 September 2026. This guide depends on facts F24, F21, F9, F1 in our verification table — if one of those changes, this page gets rewritten and the change is logged in the update log.