Accepted Content Types for Media

When specifying one or more MediaUrls when sending a messagecontent types for MediaUrl validation are fetched via the content-type header at the provided URLs. If the content-type header does not match the media, Twilio will reject the request.

Total message size must be under 5MB. An API request with media or collection of media larger than 5MB will fail with an error.

Supported MIME Types

The following types of content are fully supported by Twilio for Media. This content will be formatted for delivery on destination devices.

  • image/jpeg
  • image/gif
  • image/png

Accepted MIME Types

The following types of content are accepted by the Twilio API for Media. Requests will not be rejected, but content will not be modified for device compatibility.

Audio

  • audio/basic
  • audio/L24
  • audio/mp4
  • audio/mpeg
  • audio/ogg
  • audio/vorbis
  • audio/vnd.rn-realaudio
  • audio/vnd.wave
  • audio/3gpp
  • audio/3gpp2
  • audio/ac3
  • audio/vnd.wave
  • audio/webm
  • audio/amr-nb
  • audio/amr

Video

  • video/mpeg
  • video/mp4
  • video/quicktime
  • video/webm
  • video/3gpp
  • video/3gpp2
  • video/3gpp-tt
  • video/H261
  • video/H263
  • video/H263-1998
  • video/H263-2000
  • video/H264

Image

  • image/jpeg
  • image/gif
  • image/png
  • image/bmp

Text

  • text/vcard
  • text/csv
  • text/rtf
  • text/richtext
  • text/calendar

Application

  • application/pdf

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd browsing the Twilio tag on Stack Overflow.