Media
Updated: Dec 2, 2025 You use 4 different endpoints to manage your media:
See Supported Media Types for supported types and size limits.
Get media ID
Some of the API requests described in this document require a media ID. Media IDs are returned by the API when uploading media, and are included in incoming media messages webhooks ( image messages, video messages, etc.) Media IDs returned by the API expire after 30 days. Media IDs in webhooks expire after 7 days.Upload media
To upload media, make aPOST call to /PHONE_NUMBER_ID/media and include the parameters listed below. All media files sent through this endpoint are encrypted and persist for 30 days, unless they are deleted earlier.
Parameters
Request
Response
Upon success:Example request
Example response
Get media URL
You can query a media ID directly to get a media URL, which you can then query directly with your access token to download the media asset. Starting November 12, 2025, incoming media messages webhooks ( image messages, video messages, etc.) will include the media url automatically, and assign it to a newurl property. This property is being released to developers gradually over several weeks, so may not be available to you immediately.
Media URLs expire after 5 minutes, after which you must query the ID again to get a new URL.
Request syntax
phone_number_id is optional. If included, the request will only be processed if the business phone number ID included in the query matches the ID of the business phone number that the media was uploaded on.
Response syntax
A successful response includes an object with a media url. The URL is only valid for 5 minutes. To use this URL, see Download Media.Delete media
Use the DELETE /<MEDIA_ID> endpoint to delete a media asset.Request syntax
phone_number_id is optional. If included, the request will only be processed if the business phone number ID included in the query matches the ID of the business phone number that the media was uploaded on.
Example response
Download media
To download media, make aGET request on the media URL and include your access token. If you omit your token, the request will fail.
Note that when retrieving a media from a media ID received via webhook, the media ID will only be available to download for 7 days.
Request syntax
404 Not Found response code. In that case, we recommend you try to get a new media URL and download it again. If doing so doesn’t resolve the issue, renew your access token and attempt to download the media asset again.
Supported media types
Audio
Document
Image
Images must be 8-bit, RGB or RGBA.Sticker
WebP images can only be sent in sticker messages.Video
Only H.264 video codec and AAC audio codec supported. Single audio stream or no audio stream only. Note that videos encoded with the H.264 “High” profile and B-frames are not supported by Android WhatsApp clients. We recommend that you use H.264 “Main” profile without B-frames, or the H.264 “Baseline” profile when encoding (or re-encoding with a tool like ffmpeg), and place moov boxes before mdat boxes, for broader compatibility. If you are using ffmpeg, you can use the -movflags faststart flag to place moov boxes before mdata boxes.
Note that mismatched MIME type (
131053) is a common error. We recommend that you inspect your media files to verify their MIME type, and make sure that your file name extensions reflect their types. For example, if you are using UNIX, you can inspect a file via the command line to determine its MIME type:
file -I your-image-asset.png
Media message download constraints
The maximum supported file size for media messages on Cloud API is 100MB. In the event the customer sends a file that is greater than 100MB, you will receive a webhook with error code 131052 andtitle:
“Media file size too big. Max file size we currently support: 100MB. Please communicate with your customer to send a media file that is smaller than 100MB”.
We advise that you send customers a warning message that their media file exceeds the maximum file size when this webhook event is triggered.

