Why Group Texts Get Complicated on Android: MMS, Mass Texts, and RCS

“Group text” sounds like one simple feature.

On Android, it can actually describe several different kinds of conversation.

A message sent to five people might be:

• one shared group MMS conversation
• five separate SMS messages sent as a mass text
• an RCS group chat

They can look similar in a messaging app, but they do not behave the same way underneath.

That difference explains a lot of the strange things people run into with Android group messaging: private replies when you expected reply-all, conversations splitting into different threads, media failing to send, groups behaving differently after switching apps, or a chat that worked as RCS no longer behaving the same way somewhere else.

The first step is understanding what kind of “group text” you are actually using.

Three different things can look like a group text

Here is the simplest way to think about it:

That distinction matters more than the phrase “group text.”

Even the term group SMS can be misleading.

Standard SMS does not provide the same shared reply-all group behavior that people expect from a modern group chat. On Android, a traditional carrier-based group conversation is generally handled as group MMS.

Google Messages makes this distinction explicit in its group messaging settings:

• group MMS sends one shared MMS conversation
• mass text sends separate SMS messages and receives individual replies

Google documents the difference here:

Google's group messaging settings guidance

A text-only group can still be MMS

This surprises people because MMS is usually associated with photos and videos.

But MMS is also used for traditional multi-person group conversations.

You can send nothing but plain text and still be using MMS if the message is part of a shared carrier-based group thread.

Why?

Because SMS by itself is fundamentally a one-to-one messaging system.

If you select several recipients and your app is configured to send individual messages, the same text can simply be sent separately to each person.

That is a mass text.

Each recipient gets their own message.

If they reply, the reply comes back privately to you.

If you want everyone to participate in the same carrier-based conversation, Android messaging apps generally use group MMS instead.

So two messages that look almost identical when you press Send can produce very different conversations.

Group MMS and mass text have completely different reply behavior

Imagine you send:

Dinner at 7?

to Alice, Bob, and Carol.

If the message is sent as group MMS, Alice, Bob, and Carol are participating in the same conversation.

When Bob replies, the reply normally goes back to the group.

If the same message is sent as a mass text, Alice, Bob, and Carol each receive their own individual SMS.

When Bob replies, only you receive Bob's response.

Alice and Carol never see it.

Neither behavior is necessarily wrong.

They are simply different messaging modes.

This is why checking the group messaging setting in your SMS app can be important when replies are not behaving the way you expected.

RCS groups are a different system again

RCS adds another layer.

An RCS group is not just a better version of an MMS thread stored somewhere inside the same system.

It is a different messaging service that uses mobile data or Wi-Fi and supports richer features such as typing indicators, read receipts, higher-quality media, and — in eligible conversations — end-to-end encryption.

In Google Messages, RCS can be used when the participants in the conversation are RCS-capable.

If you create a new group that includes someone who cannot use RCS for that conversation, Google Messages may create an MMS group instead.

But that does not mean every existing RCS group has an equivalent MMS group waiting underneath it.

That distinction becomes especially important when changing messaging apps.

Google explains RCS behavior here:

Google's RCS group messaging guidance

Switching SMS apps does not convert your RCS groups

Standard SMS and MMS history is generally stored through Android's shared messaging system.

That is why switching your default SMS app does not normally mean losing your ordinary SMS/MMS conversations.

RCS is different.

A standard SMS/MMS app does not simply inherit your Google Messages RCS conversations.

Your RCS history does not turn into SMS/MMS history, and an existing RCS group should not be expected to continue as the same MMS group after you switch away.

You can still start a new SMS/MMS group with the same people.

But that is a new carrier-based conversation, not a conversion of the previous RCS group.

This is one of the reasons changing messaging apps can make group conversations feel more complicated than ordinary one-to-one texts.

I covered the broader switching behavior in:

What Happens When You Switch Away from Google Messages?

Changing the people can change the conversation

Traditional SMS/MMS grouping also depends heavily on who is in the recipient list.

A conversation between:

• Alice
• Bob
• Carol

is not necessarily the same conversation as:

• Alice
• Bob
• Carol
• David

Even though most of the people are identical, the participant set has changed.

That can result in a separate thread.

The same applies when somebody is removed.

Traditional SMS/MMS groups do not have the same group-membership model that people may be familiar with from modern internet messaging services.

Sometimes changing the membership effectively means starting another conversation.

This can look strange if you are expecting every version of “the family group” or “the work group” to remain one permanent chat.

Contact names are not the actual messaging identity

Another source of confusion is contacts.

Your messaging app might show:

Mom

but the messaging system is fundamentally working with a phone number.

The contact name is a label your phone displays for that number.

That means two contacts with similar names are not interchangeable, and different phone-number formats can sometimes affect how participants or conversations are recognized.

For international numbers in particular, using complete phone numbers including the appropriate country code is a good habit.

The important point is simple:

the phone number matters more to the messaging system than the contact name you see on screen.

Why group MMS can work differently across carriers

Messaging apps are only one part of MMS delivery.

Your carrier is involved too.

Different carriers can have different:

• MMS attachment limits
• recipient limits
• network configuration
• roaming behavior
• interoperability with other carriers

Devices and carrier settings can also affect how MMS traffic reaches the carrier network.

This is why there is no single universal answer to questions like:

What is the maximum MMS size?

or:

How many people can be in a group MMS?

For example, current carrier documentation shows different MMS limits from different providers.

The exact number is less important than the larger point:

MMS limits are carrier-dependent.

An attachment that works on one carrier may be resized, compressed, or rejected somewhere else.

That is also why messaging-app troubleshooting sometimes has to extend beyond the app itself.

Modern camera video and MMS are not a great match

This becomes especially obvious with video.

Modern phones can create very large video files within seconds.

MMS was designed around much smaller payloads.

So attaching a raw video directly from your camera can easily exceed what the carrier will accept.

Messaging apps may resize or compress media before sending it, and carriers may perform additional compression.

The exact behavior varies.

A large attachment might:

• be compressed substantially
• lose quality
• fail before it is submitted
• be rejected somewhere in the carrier path
• work for one carrier combination and fail for another

There is no universal MMS size limit that every Android phone and carrier shares.

If an MMS photo or video refuses to send, testing with a smaller file is one of the simplest ways to determine whether attachment size is part of the problem.

Group MMS can depend on mobile data and carrier configuration

MMS also needs access to the carrier's MMS service.

On many carrier/device combinations, that means mobile data and the correct carrier configuration need to be available.

Exact behavior can vary with carrier features such as Wi-Fi Calling, so it is better not to assume that every Android phone behaves identically.

But if normal SMS works while MMS or group MMS does not, checking the data connection and carrier MMS configuration is reasonable.

Google's own Messages troubleshooting documentation includes mobile data and APN configuration among the things to check for MMS problems:

Google Messages MMS troubleshooting guidance

A reply to a group is not a private reply to the latest sender

This sounds obvious once the systems are separated, but it causes real confusion.

In a group MMS conversation, replying normally means replying to the participant group.

The fact that Bob sent the most recent message does not turn the next reply into a private message to Bob.

In a mass text, there was never a shared group conversation in the first place.

Bob's response appears in the individual conversation between you and Bob.

And in an RCS group, replies belong to the RCS group session.

These models are different enough that two conversations containing the same people can behave differently depending on how they were originally created.

If your group messages are behaving strangely, check these first

Before assuming the app is broken, it helps to identify which layer is causing the problem.

1. Check your default SMS app

Android expects one app to act as the default SMS handler.

Make sure the app you are trying to use is actually set as the default messaging app.

2. Check whether the conversation is RCS or MMS

If you moved away from Google Messages, an old RCS group does not automatically become a standard MMS group.

Try creating a new SMS/MMS group if that is what you want to use.

3. Check group messaging versus individual messages

If everybody is receiving the message but replies are arriving privately, your app may be configured for mass texting rather than group MMS.

Look for a setting describing:

• group MMS
• group conversation
• send individual messages
• mass text

The exact wording varies by app.

4. Test without a large attachment

If text works but a photo or video fails, try a smaller attachment.

Carrier MMS limits vary significantly.

5. Check mobile data and carrier service

If MMS is not sending or downloading at all, confirm that your carrier service and mobile data are available.

Carrier MMS configuration can matter even when ordinary SMS is working.

6. Consider the carrier

If the problem only appears with certain recipients, group sizes, or attachments, carrier interoperability or limits may be involved.

There is not always an app-side setting that can override a carrier restriction.

You usually do not need to disable RCS just to try another SMS app

One troubleshooting step that gets repeated too casually is:

Turn off RCS first.

That is not universally necessary just to test another default SMS app.

Google recommends RCS deregistration in specific situations, such as when someone has switched devices or messaging apps and messages are no longer reaching them correctly.

Turning RCS off can also remove you from RCS group chats.

So it is better to treat deregistration as a targeted troubleshooting step rather than a requirement every time you change SMS apps.

Google's current guidance is here:

Google's RCS deactivation guidance

Group messaging also has different privacy properties

The transport matters for privacy too.

Standard SMS and MMS travel through carrier infrastructure and are not end-to-end encrypted.

Eligible RCS conversations can provide end-to-end encryption depending on the participants and messaging implementation.

That does not make one system universally “good” and the other “bad.”

They simply have different capabilities and dependencies.

Google documents the SMS/MMS versus RCS encryption distinction here:

Google's SMS/MMS and RCS encryption guidance

What this means for ZenSMS

ZenSMS supports standard SMS and MMS group messaging.

It does not provide RCS.

That means a group conversation in ZenSMS uses the standard carrier SMS/MMS system rather than importing or continuing an existing RCS group.

SMS/MMS history stored through Android remains available when switching compatible default messaging apps, but RCS history does not become SMS/MMS history.

Group MMS also remains partly dependent on your carrier, device, network conditions, recipient set, and attachment limits.

ZenSMS can provide the messaging interface.

It cannot redefine the carrier protocol underneath it.

That is an important boundary for any SMS/MMS app.

“Group text” is simpler once you know which system you are using

Android group messaging feels inconsistent partly because several different technologies are presented through very similar interfaces.

A shared carrier conversation is usually group MMS.

Sending the same SMS separately to several people is mass texting.

An RCS group is a separate data-based group messaging system.

Once those are separated, a lot of the weird behavior starts making sense.

Private replies might mean the message was sent individually.

A new thread might mean the participant set changed.

A group disappearing after switching apps might have been RCS rather than SMS/MMS.

A video failing might simply be too large for the carrier's MMS limits.

None of that means group messaging is always simple.

But at least it stops being mysterious.