Loading...
MMS
MMS message types

MMS message types

MMS supports many different message types to enable you to send multimedia content. The multimedia attachments sent using MMS typically are images but you can also send other types of content, like audio and video files.

The media content may be displayed in different ways on some mobile devices. It is also possible that older devices, such as feature phones, may not support MMS.


MMS message size limits

The size of an MMS message is measured in bytes and includes the entire message, including all multimedia content, attachments, headers, and additional metadata.

The total MMS message size includes all attachments, message headers, and any additional metadata. When sending multiple attachments, the combined total must fit within the operator limit, not each attachment individually. For example, if an operator limit is 1 MB, two 700 KB attachments combined (1.4 MB) exceed the limit.

Unlike SMS, MMS does not have strict character limits for text. Standard text lengths for MMS can be up to 1600 characters, and some operators allow more (under the condition the message does not exceed the allowed MMS message size).

Note

If your campaigns are time sensitive, limit the total message size to 150 KB.

Maximum MMS sizes vary depending on the network operator, but all operators will reliably handle messages of up to 300 KB of data. For exact limits by operator, see Operator capabilities and limits.


MMS image dimensions

Infobip does not enforce specific image dimensions for MMS messages, as long as your media follows the recommended file size limits. However, selecting appropriate dimensions can improve display quality and help ensure consistent delivery across devices and networks.

Image dimensions are measured in pixels, which determine the image resolution and how the content appears on mobile devices. Optimizing both file size (KB/MB) and dimensions (pixels) helps maintain image clarity while staying within carrier limits.

There are no strict requirements for image width or height. The following aspect ratios are commonly used and generally display well on most devices:

  • Square (1:1): Example sizes 600 × 600 px, 320 × 320 px
  • Portrait (9:16): Example size 640 × 1138 px
  • Landscape (16:9): Example size 1280 × 720 px

MMS file formats

The following file formats are recommended for sending media content over MMS. The list does not include all potentially supported file types.

As additional assurance for some media types, it is recommended that you test sending MMS messages to a device that is commonly used in your region.

Multimedia contentMMS file format
ImagesJPEG, JPG
GIF
PNG
AudioMP3, MP4
MID, MIDI
WAV
VideoMPEG, MPG, MP4: Support may vary by handset
3GP
TextTXT, TeXT, US-ASCII: UTF-8, US-ASCII (not UTF-16)
vCard: Limited support; some handsets do not accept vCards
ApplicationPDF: Support may vary by handset; installed PDF reader required
SMIL: Support may vary by handset
Passbook: iOS only
vCards

A vCard is a file format that delivers the contact details for a person (or business) and can be sent using MMS.
The file format is called Virtual Contact File (.vcf).
Support for vC limitations:

  • For iPhones, you can send vCard files as long as the content ID ends with .vcf
  • Some feature phones will accept vCards
  • Use the Content-Type: text/vcard and specify the character encoding

A vCard can contain special characters, as well as different types of content, and will be successfully processed by the major carriers (Tmobile, Verizon, ATT, Rogers, Telus).
The most common special characters and content types are:
  • @ 
  • <, >
  • /
  • A URL
  • An encoded image within the vCard (the vCard as text and the image encoded in base64)
  • The use of accents within the vCard (Hola, cómo estas?)
  • ¿, ?

For most carriers, the recommended character encoding format for vCards in MMS is UTF-8. To help you to increase the success rate for your campaigns, follow these guidelines in the request body:
  • Accents must NOT appear as part of the name of the content in the header: Content-Type: text/x-vcard; charset=UTF-8; name="ÓNE/SIZE.vcf"
  • Accents within the header result in message processing failure and the following error message is displayed: Invalid String format in VCard contentType/contentId


MMS transcoding

Many carriers set their own MMS size limits when delivering messages to their subscribers. The Infobip MMS Transcoding service helps you to stay within those limits by automatically downsizing image attachments (JPG/PNG) to meet the destination carrier's requirements.

With MMS transcoding, you can:

  • Reduce costs: failed MMS deliveries still incur messaging fees. By preventing rejections, transcoding minimizes unnecessary charges.
  • Increase deliverability: MMS messages that failed due to size limitations are now successfully delivered to end-users.
  • Simplify integrations: no need to build custom validation or resizing logic - Infobip handles it automatically and at scale.
Note

MMS transcoding is disabled by default. To learn more or to request MMS transcoding, contact your account manager.


Supported mobile operators and limitations

The MMS APIs support both Mobile Originated (MO) and Mobile Terminated (MT) messages on the mobile network operators listed in the table below. For sending messages in other regions, contact your account manager.

Operator capabilities and limits

Use the table below to check media support, message size limits, and delivery capabilities for MMS across different mobile operators. For each country, the tables include allowed sender types, registration requirements, attachment count, and supported file formats.

The Maximum message size column refers to the total size limit for the entire MMS message. For the full definition of how message size is calculated, see the MMS message size limits section.

Select each country to expand the section and view details.



Need assistance

Explore Infobip Tutorials

Encountering issues

Contact our support

What's new? Check out

Release Notes

Unsure about a term? See

Glossary
Service status

Copyright @ 2006-2026 Infobip ltd.

Service Terms & ConditionsPrivacy policyTerms of use