MMS vs SMS in 2026 — what rich media on US carrier networks actually takes

MMS is the only rich-media channel that reaches any US handset over a standard phone number — no app, no opt-in to an OTT service, no sender registration beyond your existing 10DLC campaign. For US A2P programs it is the difference between text that carries a link to an image and the image itself, delivered inline. This guide covers what MMS actually is at the protocol level, how the three US carriers treat it today, when it beats WhatsApp/RCS rich media and when it loses, how per-message pricing works, and the send path on Devotel Orbit.

What MMS actually is, beyond "picture SMS"

MMS is not SMS with an attachment flag. It is a separate carrier protocol: the message is assembled as a multipart document (a SMIL envelope wrapping the body text and each media part), submitted to the carrier's MMSC (Multimedia Messaging Service Center), and delivered either 1-to-1 or, as a distinct carrier class, 1-to-many group MMS.

Three facts about that protocol decide every practical question:

• Multipart means counted parts, not segments. An SMS bills in 160-character or 70-character segments; an MMS bills per message regardless of how it fragments, and a multipart SMS that attaches media stops being SMS priced.
• The media goes through the carrier's MMSC, not a link. The handset downloads the attachment from the carrier's own servers. That is the fundamental difference from an SMS with a URL in the body — which is a clickable link, not rich media. The "image-only SMS" pattern many senders mistake for MMS is just a link: it renders nothing inline, gets filtered harder by carriers that scan URLs, and loses the message entirely if the link host is down.
• Size is negotiated with the carrier, not the sender. The widely quoted "1 MB ceiling" is a myth in both directions: some carrier gateways accept more than 1 MB, while others will down-render or silently drop attachments well below it. The practical cross-carrier cap is roughly 300–600 KB per attachment; plan assets under 600 KB and treat anything above 1 MB as carrier-dependent, not guaranteed.

Group MMS is its own carrier class. A 1-to-many message with a media part routes through the carrier's group-messaging logic rather than N individual 1-to-1 sends, and caps the recipient count per operation (on Orbit, up to 20 recipients per group send). Treat group MMS as a separate feature with its own vetting posture, not as a loop over single sends.

The US-carrier reality: T-Mobile, AT&T, Verizon

US MMS works because all three national carriers run MMSC infrastructure, but they do not treat payloads the same, and the differences show up as delivery variance rather than explicit errors.

• T-Mobile generally passes the largest image payloads and is tolerant of animated GIFs. It is the friendliest of the three for richer creative.
• AT&T applies tighter size gates and recompresses images aggressively. An image that renders crisply on T-Mobile can arrive recompressed on AT&T; another reason to stay under the practical 600 KB cap.
• Verizon accepts rich deliverability checks at the network edge, which means malformed or oversized payloads can die at the carrier without a deliverable-to-handset failure you can attribute later.

10DLC pairs with MMS, it does not replace it. In the US, MMS A2P traffic still needs a registered 10DLC sender identity — brand and campaign registration through The Campaign Registry — exactly like SMS. The registration covers the sender; the protocol selected per message is either SMS or MMS depending on whether media is attached. A sender with clean TCR vetting can send both from the same number.

The fallback when MMS cannot land. When the destination handset or carrier refuses MMS — a feature-phone, a NANP-unsupported recipient class, or a carrier rejection — the correct degraded form is an SMS with a plain-HTTPS link to the asset. That is a real fallback pattern on Orbit's cross-channel chain; the channel fallback matrix lists MMS with the fallback target "SMS with link" precisely because degradation loses the inline image. Plan for it in creative: the SMS leg must read complete as text.

MMS vs WhatsApp/RCS rich media — the decision table

MMS is not the only way to put images in front of a customer. The comparison that decides it is reach, not features: MMS reaches any US handset; WhatsApp and RCS reach app-installed or carrier-RCS-capable devices and lose everyone else.

Use MMS when the media itself is the payload — product photos, QR codes for in-store redemption, appointment cards, map screenshots — and the audience is US handset reach you cannot assume has WhatsApp or RCS. Use WhatsApp or RCS when the audience is known to be reachable on those channels and the creative is interactive (buttons, carousels, suggested replies). Use SMS with a link as the raw fallback, and route the choice per recipient through a channel fallback chain rather than a static campaign-wide pick.

Pricing: per message, on a published rate card

MMS bills per message, not per segment and not per attachment. A multipart payload with three images is one message; an SMS + media auto-upgrade is one message priced at the MMS rate. The rate differs from the SMS rate on the same destination — MMS has a higher per-message cost because the carrier's MMSC termination is a separate, more expensive path.

On Devotel Orbit that difference is published, not negotiated: per-country and per-channel rates on the pricing page list SMS and MMS as separate destination rates, so the cost of "upgrade every product photo from SMS-with-link to real MMS" is computable before the campaign ships. Like every Orbit channel, there is no quote-only tier — the rate card is the price, and the bill matches the estimator.

Implementation on Orbit: one endpoint, one dashboard

The send path reuses the SMS endpoint. Attach media and the API upgrades the message to MMS automatically:

1. Send single MMS. POST /api/v1/messages/sms with media_url or media_urls. The same API upgrades the send to MMS when any attachment is present; body text is optional when media is attached.
2. Validate media at send time. Each attachment URL must be HTTPS; Orbit HEAD-checks every URL before dispatch and rejects unsupported content types before the message leaves. Accepted: JPEG, PNG, GIF, WebP images; MP4/3GPP video; MPEG/OGG/AAC audio. Rejected as 422: PDFs, vCards, and anything over 5 MB.
3. Avoid the failure modes that dump media. Attachments above ~1 MB look accepted but routinely arrive recompressed or dropped by individual carrier gateways. Untrusted HTTPS hosts fail the SSRF allowlist and die as pre-send 422s rather than reaching the carrier. Keep assets under 600 KB on a checkable domain and the 422 class disappears.
4. Choose group MMS deliberately. POST /api/v1/messages/group sends one payload to up to 20 recipients as a true group message; each recipient is tracked with its own status row so per-recipient rejections (unsupported NANP class, failed pre-check) are attributable rather than silently dropped.
5. Watch it in the dashboard. MMS is a first-class channel in the Messages hub: delivery history for both single and group sends lives under /messages/mms alongside the SMS workspace, with per-recipient status for group sends.

The MMS channel docs carry the full field and status reference; the fallback posture for "MMS not supported at destination" is the org-level fallback chain described in the channel fallback matrix.

Frequently asked questions

What is the maximum attachment size for MMS?

Carrier-practical, roughly 300–600 KB per attachment for reliable inline delivery across the US carriers. The Orbit API accepts up to 5 MB per attachment before rejecting, but most carrier gateways down-render or drop media over ~1 MB — so API acceptance is not delivery. Budget creative under 600 KB.

Do I need special registration to send MMS in the US?

No additional registration beyond your 10DLC sender identity. MMS rides the same registered long-code number as SMS; The Campaign Registry brand and campaign vetting covers the sender, and the protocol per message flips between SMS and MMS based on whether media is attached.

Can I send MMS outside the US and Canada?

No — MMS terminates on NANP (+1) carriers only. For international rich media use WhatsApp or RCS, or degrade to SMS with a link. Non-NANP destinations are rejected per-message before dispatch.

What happens when the recipient's phone cannot receive MMS?

The right fallback is an SMS with a plain HTTPS link to the asset, applied via the organization-level fallback chain. The downside is a link, not the image — the SMS leg must carry enough text to compensate.

Is group MMS per-recipient deliverability trackable?

Yes. A group send pre-registers each recipient with its own status, so rejections on one recipient show as per-recipient failures instead of a whole-batch failure. Group sends cap at 20 recipients per operation.

The takeaway

MMS is the carrier-native rich-media channel for US A2P: multipart messages through the carrier MMSC, delivered inline on any +1 handset, priced per message on a published rate card, paired with SMS fallback for the destinations that refuse it. Its practical limits are carrier-set — 300–600 KB per attachment, NANP-only reach, group sends as a separate carrier class — and none of those limits is hard to plan around once mobile creative is sized for the carrier reality rather than the protocol maximum. For where MMS sits in a full fallback chain, the channel fallback matrix is the comparison surface.

Published 2 September 2026.