Skip to main content

MMS Transcoding

Destination carriers impose various restrictions on MMS message sizes (see below), and these restrictions are contingent on both the destination carrier and the type of phone number. To assist our users in complying with these restrictions, we provide a messaging profile setting known as mms_transcoding. When this setting is enabled (set to true), we will adjust the size of the media to adhere to the size requirements of the destination. However, please take note of the following:

  • Only images and videos will undergo resizing. Additionally, please be aware that animated GIFs are not supported. If you intend to send animated GIFs, ensure that they are small enough.
  • It's important to understand that resizing will typically result in a reduction in the quality of the media.
  • During the resizing process, images will be converted to JPEG format, while videos will be converted to H.264 MP4.

Setting mms_transcoding on messaging profile

curl -i -X PATCH \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"mms_transcoding": true

MMS message size limits

The table below shows the MMS message limits imposed by the destination carriers.

Destination CarrierSource Number TypeMaximum Size
AT&TLong code1 MB
AT&TToll free600 KB
AT&TShort code600 KB
SprintLong code1.5 MB
SprintToll free600 KB
SprintShort code1 MB
T-MobileLong code1.5 MB
T-MobileToll free600 KB
T-MobileShort code1 MB
VerizonLong code1 MB
VerizonToll free600 KB
VerizonShort code1.2 MB

On this page