Message size limits vary according to the type of message content and by account type and contract and carrier max allowed size and API used.
The table below shows you the maximum MMS API upload sizes for the various supported content types:
|
With Transcoding - The below Limits applies to MMS accounts that support transcoding on the JSON and MM7 API. Transcoding is only supported on Short Code senders
|
|
MMS Image
|
3000 KB
|
|
MMS GIF Image
|
1024 KB
|
|
MMS Audio
|
10000 KB
|
|
MMS Video
|
50000 KB
|
|
MMS Text size
|
5000 characters
|
|
MMS Object
|
2048 KB - saveMMS/sendMMS API
|
|
No Transcoding - The below Limits applies to MMS accounts that do not support transcoding on the JSON and MM7 API. This is supported on Short Code and Toll-Free senders.
|
|
MMS Image
|
1000 KB
|
|
MMS Audio
|
1000 KB
|
|
MMS Video
|
1000 KB
|
Transcoding is not supported on 10DLC. The following are the published maximum size limits for 10DLC MMS by operator:
| Operator |
base64 encoded |
Binary |
in Bytes |
| AT&T |
2 MB |
~1.46 MB |
1530843 bytes |
| T-Mobile USA |
3.1 MB |
~2.2 MB |
2306867 bytes |
| Verizon Wireless |
1.65 MB |
~ 1.25 MB |
1310720 bytes |
| U.S. Cellular |
2 MB |
~1.46 MB |
1530843 bytes |
* Sizes are subjected to change in future based on provider MMSC size updates
Click here for list of supported file types.
Important Notes:
- The final size of Base64-encoded binary data is equal to 1.37 time the original data size. Binary content encoded with Base64 produces a larger file size.
- May change based on future changes by the carriers.
- Transcoding is only supported on Short Code sender types.
- The sendMMS action of the JSON API only supports transcoding for image content.
- The saveMMS action of the JSON API supports transcoding for all content types.
- The SubmitReq action of the MM7 API also supports transcoding for all content types.
Visit the Sinch MMS product page to learn more about the Sinch MMS API.
