Why MMS Messages Fail, Expire, or Won’t Download on Android

A normal text message sends without a problem.

Then somebody sends you a picture.

It sits on Downloading.

Or your photo refuses to send.

Or a group conversation stops working.

Or, even stranger, the phone tells you:

MMS expired.

It is easy to assume the messaging app itself is broken.

Sometimes it is.

But MMS has more moving parts than ordinary SMS.

A standard text and an MMS can use different carrier paths, different network requirements, different size limits, and different retrieval steps.

That is why:

SMS working does not prove MMS will work.

Understanding that difference makes MMS problems much easier to troubleshoot.

MMS is not just SMS with a picture attached

SMS and MMS are related, but they are not the same delivery system.

A normal SMS is a small carrier text message.

MMS — Multimedia Messaging Service — is used for things such as:

• pictures
• videos
• audio
• some attachments
• many traditional group conversations

An MMS usually has to move through the carrier's multimedia messaging system.

At a high level, the process looks something like this:

1. Your messaging app prepares the MMS.
2. Your phone connects to the carrier's MMS service.
3. The carrier accepts and temporarily handles the multimedia content.
4. The recipient is notified that an MMS is available.
5. The recipient's phone retrieves the message.
6. The content appears in the conversation.

Those stages can fail independently.

That is what makes MMS troubleshooting different from ordinary SMS troubleshooting.

Why SMS can work while MMS fails

This is one of the most useful things to know.

You can have:

• working cellular service
• successful SMS messages
• normal phone calls

and still have broken MMS.

That can happen because MMS may also depend on:

• a working data connection
• carrier MMS provisioning
• correct carrier network settings
• attachment size
• group-MMS support
• roaming settings
• the recipient's network conditions

Google's own Messages troubleshooting guide treats MMS separately from ordinary SMS and specifically recommends checking the data connection and carrier APN settings when MMS fails.

Google Messages troubleshooting guidance

So if plain texts work but pictures or group messages do not, that is useful information.

It means the basic SMS path may be fine while something specific to MMS is failing.

Sending an MMS and downloading an MMS are different stages

Not every MMS failure happens on the sender's phone.

There are several broad possibilities.

The sender cannot submit the MMS

The message may fail before the carrier successfully accepts it.

Possible reasons include:

• no usable data connection
• carrier MMS service unavailable
• incorrect carrier configuration
• attachment too large
• MMS disabled or unsupported on the account

In this case, the sender usually sees the problem first.

The carrier accepts it, but the recipient cannot retrieve it

The sender's phone may appear to have successfully sent the MMS.

But the recipient might still be unable to download it.

Possible reasons include:

• recipient has no usable data connection
• recipient is out of coverage
• carrier MMS settings are wrong
• automatic MMS download is disabled
• roaming restrictions
• carrier interoperability problems

The MMS waits too long and becomes unavailable

Carriers do not necessarily keep an undelivered MMS available forever.

If the recipient cannot retrieve the content within the carrier's delivery window, it may eventually become unavailable.

That is where an expired message can come from.

What does “MMS expired” actually mean?

The safest interpretation is:

The multimedia content is no longer available for retrieval.

Carriers can temporarily store undelivered MMS content while they wait for the recipient device to become available.

The exact window varies.

For example, AT&T currently documents that picture and video messages may be stored for up to 72 hours when the receiving phone is turned off or outside a data coverage area.

AT&T picture and video messaging guidance

Other carriers may use different delivery or storage behavior.

There is no universal Android rule saying:

Every MMS expires after exactly X hours.

So if your phone shows Expired, it does not automatically prove:

• the messaging app deleted the message
• the sender did something wrong
• the sender blocked you
• you blocked the sender
• the attachment was definitely too large

It usually tells you something about the message no longer being available through the MMS delivery path.

The exact reason it reached that state can still vary.

An MMS can expire without sitting on your phone for days

There is another wrinkle.

Sometimes an app may receive information from the carrier indicating that the underlying MMS content is already unavailable.

That can make an MMS appear to arrive already expired.

So the visible time between:

message appears

and:

message says expired

does not necessarily represent how long the carrier had been trying to deliver it.

The carrier-side delivery process may have started earlier.

This is why an instant-looking expiry does not automatically mean the app itself discarded the message.

Mobile data often matters for MMS

A very common MMS troubleshooting step is:

Check mobile data.

Many carrier/device combinations need a working carrier data path for MMS.

That can be true even when:

• Wi-Fi is connected
• ordinary SMS works
• phone calls work normally

Google's MMS troubleshooting guidance specifically tells users to make sure they have a data connection.

Google Messages MMS troubleshooting

T-Mobile's troubleshooting guidance similarly recommends testing picture messaging on the T-Mobile network data connection.

T-Mobile messaging troubleshooting

But there is an important caveat:

Do not turn that into “MMS always requires cellular data on every Android phone.”

Carrier and device behavior can differ.

Some carriers support messaging through Wi-Fi Calling or other Wi-Fi-based paths.

Google Fi also documents messaging behavior that can work over Wi-Fi in some configurations.

So the practical rule is:

If MMS is failing, make sure your phone has the kind of data connection your carrier expects for MMS.

For many users, that means testing with mobile data enabled.

APN settings can break MMS while SMS still works

APN stands for Access Point Name.

You do not need to understand the technical details to troubleshoot MMS.

The useful thing to know is that these settings tell your phone how to connect to parts of your carrier's network.

MMS can depend on carrier configuration that ordinary SMS does not.

That means incorrect or missing carrier settings can produce a very specific symptom:

SMS works. MMS does not.

Google includes resetting APN settings to their defaults as an MMS troubleshooting step.

Google Messages troubleshooting guidance

If you reach that point, resetting to the carrier-provided defaults is generally safer than copying APN values from a random website.

If manual configuration is actually required, use your carrier's current support documentation.

Do not start editing APN settings immediately

APN problems are real.

But they should not be the first thing you change.

Before touching carrier network configuration, check the simpler possibilities:

• Is mobile data available?
• Is the phone in coverage?
• Does a small MMS work?
• Is MMS enabled on the carrier account?
• Is the correct SMS app set as default?
• Is automatic MMS download disabled?
• Is the phone roaming?

Only after those basics fail does carrier configuration become a stronger suspect.

MMS attachment limits vary by carrier

There is no single universal MMS attachment limit.

Current carrier documentation shows very different limits.

For example:

• AT&T documents picture/video messaging up to roughly 1 MB on its service and may compress larger attachments.
• T-Mobile documents up to 1 MB sending and 3 MB receiving for MMS.
• Google Fi documents MMS files up to 8 MB domestically, with a smaller international limit.
• Verizon publishes different limits for images and videos on its network.

AT&T MMS guidance

T-Mobile messaging limits

Google Fi SMS and MMS troubleshooting

Verizon picture and video message size guidance

The important point is not memorizing those numbers.

It is this:

MMS size limits are carrier-dependent.

An attachment that succeeds on one network might be compressed or rejected somewhere else.

Modern phone videos are especially difficult for MMS

Modern phones create enormous video files compared with traditional MMS limits.

A short high-resolution phone video can easily be many times larger than what a carrier accepts as MMS.

That leaves several possibilities:

• the messaging app compresses it
• the carrier compresses it
• quality drops dramatically
• the send fails
• the receiving carrier rejects it

So if a video refuses to send through MMS, try something much smaller before assuming the entire MMS system is broken.

That simple test tells you whether attachment size may be part of the problem.

Start with a tiny image

This is one of the best MMS diagnostic tests.

Instead of repeatedly retrying the same large photo or video, send:

• one small image
• to one person
• with mobile data available

If that succeeds, you have learned that:

• MMS itself can work
• the carrier path is available
• the previous attachment may have been too large or otherwise problematic

If even a tiny image fails, the problem is more likely related to the carrier/data/configuration path.

Group messages can fail because they are MMS too

Another common confusion:

Normal texts work, but my group chat doesn't.

Traditional carrier group conversations generally use group MMS.

So a group conversation inherits many of the same dependencies as other MMS:

• carrier support
• working data path
• MMS configuration
• recipient limits
• network interoperability

That means successful one-to-one SMS does not prove a group MMS should also succeed.

If group messaging itself is the main problem, I have a separate guide:

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

Auto-download settings can make MMS look stuck

Messaging apps can let you control whether MMS content downloads automatically.

Google Messages, for example, provides settings for:

• automatically downloading MMS
• automatically downloading MMS while roaming

Google Messages settings guidance

If automatic download is disabled, you may see a message waiting for manual retrieval rather than immediately seeing the photo or attachment.

That does not necessarily mean delivery failed.

But if the content remains unretrieved long enough, the carrier may eventually stop making it available.

Roaming can change MMS behavior

MMS can behave differently while roaming.

Possible differences include:

• mobile data availability
• roaming data permissions
• automatic MMS download being disabled
• different carrier routing
• international attachment limits

For example, Google Fi publishes a different MMS attachment limit for international usage than for domestic usage.

So if MMS suddenly stops working while traveling, check roaming and carrier guidance before assuming the app itself changed.

RCS can make MMS troubleshooting confusing

Modern messaging apps may send photos and group messages through RCS instead of MMS when RCS is available.

That means a conversation you thought was “picture messaging” may not have been using MMS at all.

This matters especially after switching messaging apps.

If you previously used Google Messages with RCS and then moved to an SMS/MMS-only app, the transport has changed.

If messages stop arriving after switching apps, Google's RCS troubleshooting guidance may apply.

I cover that situation in:

Missing Texts After Switching Android Messaging Apps? What to Check First

The important thing is to distinguish:

Is this actually MMS?

from:

Was this conversation previously using RCS?

Those are different problems.

What an MMS status can and cannot tell you

Some symptoms are useful clues, but they rarely prove one exact cause.

Sender says it was sent, but you received nothing

Possible explanations include:

• delivery delay
• recipient offline
• carrier interoperability
• network configuration
• wrong number
• filtering
• an RCS-versus-MMS mismatch

It does not identify one cause by itself.

You see a Download button but nothing happens

That points more toward retrieval.

Things worth checking include:

• data connection
• automatic-download settings
• roaming
• carrier configuration
• whether the message is still available

Every MMS fails but SMS works

That strongly suggests looking at MMS-specific dependencies:

• data
• MMS provisioning
• carrier configuration
• APN settings

Only large photos or videos fail

Attachment size or compression becomes a much stronger suspect.

The MMS says Expired

The content is no longer available through the MMS retrieval path.

That does not, by itself, tell you why.

What to check first when MMS fails

A good troubleshooting order is deliberately boring.

That is a feature.

1. Confirm it is actually MMS

Ask what kind of message is failing.

Is it:

• a photo
• video
• attachment
• traditional group conversation

Or was the previous conversation actually RCS?

Knowing the transport prevents you from troubleshooting the wrong system.

2. Check signal and carrier service

Make sure:

• Airplane mode is off
• cellular service is available
• the SIM is active
• the carrier account is working

3. Check the data connection

Try mobile data if your carrier normally uses it for MMS.

If you are roaming, check whether data roaming or MMS auto-download settings are preventing retrieval.

4. Try a small image

Send one tiny picture to one recipient.

This removes:

• group complexity
• huge attachment size
• video compression

from the test.

5. Confirm the correct default SMS app

Android uses one default SMS app to handle normal SMS/MMS messaging.

Make sure the app you intend to use is actually selected.

6. Check MMS download and group settings

Depending on your app, look for settings related to:

• MMS auto-download
• roaming auto-download
• group MMS
• individual mass text

7. Restart or reconnect

A phone restart or temporary Airplane-mode cycle can restore a stuck network connection.

8. Reset APN settings to carrier defaults

If MMS still fails, carrier configuration becomes more relevant.

Prefer resetting to the carrier defaults over entering values from an unofficial website.

9. Contact the carrier

If MMS fails across messaging apps even after basic troubleshooting, the problem may be account provisioning or carrier-side configuration.

At that point, the carrier is often better positioned to see whether MMS service is properly enabled.

What not to do first

Some troubleshooting advice creates more risk than value.

Do not factory reset your phone

A factory reset is wildly disproportionate to most MMS problems.

Do not clear messaging-app storage casually

Clearing storage can remove app-specific settings, drafts, and other local state.

It should not be a first-line response to a carrier messaging problem.

Do not delete conversations to “refresh” MMS

Deleting messages does not repair the carrier MMS path.

It can simply destroy message history.

Do not copy random APN settings from the internet

Incorrect carrier configuration can make things worse.

Use your carrier's official values or reset to defaults.

Do not repeatedly toggle RCS

If RCS is actually involved, follow Google's documented guidance.

Randomly cycling it can affect RCS groups and create more confusion.

MMS also has a privacy boundary

MMS travels through carrier infrastructure.

The carrier may temporarily store multimedia content while attempting delivery.

Standard SMS and MMS are not end-to-end encrypted in the same way eligible RCS conversations can be.

That carrier-side storage is separate from whether the messaging app itself keeps a cloud copy of your inbox.

A local-only SMS/MMS app can avoid maintaining its own remote message archive.

It cannot remove the carrier infrastructure that standard MMS depends on.

What this means for ZenSMS

ZenSMS supports standard MMS for images, documents, and group messages.

It does not provide RCS.

That means MMS in ZenSMS still depends partly on:

• your carrier
• your device
• the available network connection
• carrier MMS configuration
• attachment limits

ZenSMS can provide the messaging interface and process the message locally.

It cannot change the limits or delivery behavior of the carrier MMS network underneath it.

So if ordinary SMS works but MMS does not, that distinction matters.

The next question should not automatically be:

Is the SMS app broken?

It should be:

Which part of the MMS path is failing?

MMS has more places to fail — but that also makes it easier to narrow down

MMS can feel unpredictable because more systems are involved.

The app has to prepare the message.

The phone has to reach the carrier's multimedia service.

The carrier has to accept it.

The recipient has to be reachable.

The recipient's phone has to retrieve it.

And attachments have to fit within whatever limits the networks involved allow.

That sounds complicated.

But it gives you a useful troubleshooting rule:

If SMS works and MMS does not, troubleshoot MMS as its own system.

Check the data path.

Try something small.

Check the carrier settings.

Distinguish RCS from MMS.

And treat “expired” as a delivery/retrieval clue — not proof that somebody, or some app, deleted your message.