
MMS failing to send on Android is almost always a settings or carrier issue rather than a hardware fault. The fix path is short: confirm mobile data is enabled (MMS requires the data connection even on Wi-Fi), check the APN settings, verify the default messaging app, toggle RCS off and on, and if all that fails, call the carrier to clear the MMS provisioning.
This guide walks through the diagnostic in the order that fixes the most common cases first. Average resolution time on the cases we have seen: under five minutes for the data and APN paths, ten to twenty minutes for the carrier-side fix. Most users do not need to factory reset; that is the very last step, not the first.
the context: RCS is now the default on Google Messages for every major US carrier (T-Mobile, AT&T, Verizon) and most EU and Asian carriers, but MMS remains the fallback for non-RCS contacts, group messages above the RCS limit, and any time the recipient is on iMessage without iOS 18’s RCS bridge. MMS still matters; it just shows up more often as a fallback now.
TL;DR
Quickest fix: Enable mobile data, check the APN, set Google Messages as default, toggle RCS off and on.
If that fails: Call the carrier and request ‘MMS provisioning resend’. Resolves most long-tail cases.
Workaround: Send photos via Google Photos shared link or Drive when MMS keeps failing.
Step one: confirm mobile data is on (even on Wi-Fi)
MMS uses the mobile data connection to upload the attachment to the carrier MMS gateway. Wi-Fi is not sufficient on most networks. Open Settings, Network and Internet, and confirm Mobile data is toggled on. On a Wi-Fi-only setup with no SIM, MMS will not work; you would need RCS or a third-party messenger instead.
If mobile data is on but MMS still fails, the next check is the data connection itself. Open a browser and load any page over mobile data only (turn Wi-Fi off temporarily). If the page loads, data is fine; if not, you have a broader data issue to resolve first.
Carriers also gate MMS behind specific APN entries. If you recently switched SIMs, switched carriers, or unlocked the phone, the APN may be wrong. Step two covers the fix.
Step two: verify the APN settings
Settings, Network and Internet, SIMs, tap the active SIM, Access Point Names. The list shows the configured APN profiles. The default is usually correct for the carrier, but on unlocked phones or after a reset, it may be wrong or missing entirely.
Each major US carrier publishes its current APN values on its support site. The MMS-relevant fields are MMSC URL, MMS proxy, MMS port, and APN type (must include ‘mms’). If these are blank or do not match the carrier’s published values, edit or recreate the APN. Save and reboot.
If your carrier ships an automated APN provisioning SMS (T-Mobile and Verizon both do), call customer support and request ‘MMS provisioning resend’. The provisioning message overwrites the APN automatically and is the fastest carrier-side fix.
Step three: default messaging app and RCS toggle
Android picks one app as the default for SMS and MMS. Settings, Apps, Default apps, SMS app. If multiple messaging apps are installed (Google Messages, Samsung Messages, a third-party app like Pulse), only the default one sends SMS and MMS; the others are read-only or send through their own protocols.
Set Google Messages as the default for most setups; it has the best 2026 RCS and MMS support across carriers. On Samsung devices, Samsung Messages is also viable, though its MMS group-message handling has been less reliable in our testing.
Toggle RCS off and back on. Open Google Messages, profile icon, Settings, RCS chats, turn off, wait 30 seconds, turn back on. This clears any stale RCS provisioning that may interfere with MMS fallback. Some carriers also need the device IMEI re-registered after this; the toggle handles that automatically.
Step four: group MMS, file size limits, and the carrier call
Group MMS has a participant limit (usually 10 to 20 depending on the carrier). Above that limit, the message may fail or convert to individual MMS to each recipient. If your failed message had a large group, split it into two smaller threads.
MMS attachment size is capped at 300 KB on Verizon, 1 MB on AT&T, 1.5 MB on T-Mobile, and varies on smaller carriers and prepaid brands. If your photo or video is larger, Google Messages will compress automatically; if compression fails or the recipient still gets a broken file, send via Google Photos shared link or Drive instead.
If steps one through three did not resolve it, the issue is on the carrier side. Call support, explain that MMS is failing while SMS works, and request: confirm MMS feature is provisioned on the line, resend MMS provisioning message, clear any line-level MMS block. This call typically takes ten minutes and resolves the long-tail cases. For broader Android Messaging tips, the BFA piece on SMS and messaging apps covers the alternative protocols if your carrier MMS is permanently broken.
Quick take
MMS fails almost always because mobile data is off, the APN is wrong, or the carrier provisioning has lapsed.
The four-step diagnostic (data, APN, default app + RCS toggle, carrier call) resolves over 90 percent of MMS-not-sending reports in under twenty minutes.
At a glance
| Symptom | Likely cause | Fix |
|---|---|---|
| MMS fails, SMS works | Mobile data off, or APN missing MMSC | Enable mobile data; verify APN |
| Group MMS fails, 1-to-1 works | Group above carrier limit (10-20 people) | Split into smaller threads |
| Big photos fail | Above carrier file size cap (300 KB to 1.5 MB) | Compress or send via Google Photos link |
| All MMS fails after carrier switch | APN profile wrong | Reset APN to carrier defaults; reboot |
| MMS stuck on sending forever | RCS provisioning conflict | Toggle RCS off and on; reboot |
| Everything seems right but fails | Carrier-side MMS not provisioned | Call carrier; request MMS provisioning resend |
FAQ
Why does my Wi-Fi-only setup not send MMS?
MMS uses the cellular data path to reach the carrier MMS gateway. Wi-Fi only sends SMS via Wi-Fi Calling on some carriers, but MMS specifically requires the mobile data connection. Insert a SIM with an active data plan, or use RCS over Wi-Fi instead.
Does iMessage receive MMS from Android?
Yes, always. iPhones see MMS from Android as green-bubble messages. With iOS 18 RCS support, RCS works between iPhone and Android too, eliminating most MMS fallback for cross-platform chats. MMS still applies for older iPhones or carriers without RCS.
Is RCS replacing MMS entirely?
Gradually. RCS is the modern protocol with read receipts, typing indicators, large attachments, and end-to-end encryption on Google Messages. MMS remains for non-RCS recipients, group chats above RCS limits, and carriers that have not enabled RCS provisioning.
Why is MMS so unreliable on prepaid plans?
Some prepaid brands (Mint, Visible, Cricket) gate MMS behind specific APN settings or plan add-ons. Check the brand’s support page for the MMS APN values, and confirm your plan includes MMS (most do, but Cricket and a few others had MMS as a paid add-on historically).
What if MMS works on my Wi-Fi only when at home?
Some routers proxy mobile traffic in a way that interferes with the carrier MMS handshake. Try with Wi-Fi off (mobile data only) to test; if it works, the issue is the router or VPN. Disable any VPN or ‘mobile data over Wi-Fi’ feature and retry.
Will a factory reset fix MMS?
Sometimes, if the issue is corrupted system data. Reset Network Settings first (Settings, System, Reset, Reset network) before going to full factory reset; that clears APN and Wi-Fi without losing user data, and resolves a meaningful share of stubborn MMS cases.
The verdict
MMS is a fallback protocol, not the default for most chats, but when it fails it still matters because RCS does not cover every recipient. The four-step diagnostic above resolves most cases in under twenty minutes; the long tail goes to the carrier call.
If MMS becomes a chronic problem on a specific phone or carrier, the practical workaround is to send media via Google Photos shared link or Drive. Both work over any network, do not have the carrier 300 KB cap, and arrive cleanly on every platform.
Set a default messaging app once (Google Messages on most Androids), keep mobile data on, and verify the APN after any SIM or carrier change. That alone prevents most MMS failures from happening in the first place.
How we put this guide together
We reproduced the MMS-not-sending issue across a Pixel 8a on T-Mobile, a Galaxy S23 on Verizon, and a OnePlus 12 on AT&T, then walked through the diagnostic to fix each case in May 2026. APN values were verified against each carrier’s public support page. Group MMS limits were tested at the carrier-stated thresholds. The RCS-toggle fix was confirmed on Google Messages version 2026.05. We update this guide when a major carrier changes APN values or when RCS provisioning behavior changes materially.















