MMS is supported on Long Code, Toll-Free, and Short Code numbers in the US and Canada. International MMS support varies by carrier.
Send an MMS message
Include one or moremedia_urls in your message request to send an MMS:
You can include up to 10 media URLs per MMS message. Each URL must be publicly accessible — Telnyx fetches the media at send time.
Supported media types
| Category | Formats | Notes |
|---|---|---|
| Images | JPEG, PNG, GIF, BMP, TIFF, WebP | Most widely supported across carriers |
| Video | MP4, 3GP, MOV | H.264 codec recommended |
| Audio | MP3, WAV, AMR, OGG | Limited carrier support |
| Documents | PDF, vCard (.vcf), iCal (.ics) | Limited carrier support |
Carrier size limits
Each US carrier imposes different maximum MMS message sizes based on the sender type. Messages exceeding these limits will be rejected by the carrier.| Carrier | Long Code | Toll-Free | Short Code |
|---|---|---|---|
| AT&T | 1 MB | 600 KB | 600 KB |
| T-Mobile | 1.5 MB | 600 KB | 1 MB |
| Verizon | 1 MB | 600 KB | 1.2 MB |
Automatic transcoding
Telnyx can automatically resize media to comply with carrier size limits. When enabled, oversized images and videos are resized before delivery.How transcoding works
- You send an MMS with media that exceeds the destination carrier’s size limit
- Telnyx detects the destination carrier and its size restriction
- Media is resized to fit within the limit:
- Images → converted to JPEG
- Videos → converted to H.264 MP4
- The resized media is delivered to the recipient
Transcoding reduces media quality to meet size constraints. For best results, optimize your media before sending.
Enable transcoding
Enablemms_transcoding on your messaging profile to apply it to all MMS sent through that profile.
- API
- Portal
Best practices
Optimize media before sending
Optimize media before sending
Pre-optimize your media for the best balance of quality and deliverability:
- Images: Resize to 640×480 or smaller, use JPEG at 80% quality
- Videos: Compress to H.264, keep under 30 seconds, target 480p
- Target size: Stay under 600 KB for universal carrier compatibility
Use publicly accessible URLs
Use publicly accessible URLs
Media URLs must be publicly accessible — Telnyx fetches them at send time. Ensure:
- URLs don’t require authentication
- URLs respond quickly (timeouts cause delivery failures)
- URLs return the correct
Content-Typeheader - URLs use HTTPS for security
Handle inbound MMS media
Handle inbound MMS media
Inbound MMS media URLs in webhooks are ephemeral — they expire after a short period. Always download and store important media to your own storage (e.g., AWS S3) immediately upon receiving the webhook.See the Send & Receive MMS tutorial for a complete implementation.
Consider SMS for text-only messages
Consider SMS for text-only messages
If your message doesn’t include media, send it as SMS instead of MMS. SMS is:
- Cheaper — MMS messages cost more than SMS
- Faster — No media download/processing overhead
- More reliable — Fewer points of failure
Related resources
Send & Receive MMS Tutorial
Full tutorial for building an MMS application with media storage.
SMIL Templates
Customize the layout of your MMS media with SMIL templates.
Send Your First Message
Get started with the Telnyx Messaging API.
Messages API Reference
API reference for sending messages with media.