WhatsApp API error 131053: Media upload error
Error 131053 means the image, video, audio or document in your message couldn't be used. WhatsApp accepted the send, then failed to process the media, so the message wasn't delivered.
Quick answer
WhatsApp couldn't process the media file. Check its real MIME type and size against WhatsApp's supported formats and limits, fix or convert the file, and send again.What WhatsApp error 131053 means
Meta documents 131053 as: unable to upload the media used in the message, for reasons such as an unsupported media type. Meta says the error_data.details value in the failure webhook explains more, and suggests checking a file's real MIME type, for example with the Unix command file -I.
Why error 131053 happens
Request errors come from the payload, so the cause is usually in how it was built. Look for these first:
- A file whose extension says one thing and whose content is another, such as a .jpg that is really WebP or HEIC.
- A format WhatsApp doesn't support for that message type, such as a .mov video.
- A file over WhatsApp's size limit for its type.
- A media link that returns an HTML error page, a login page or a redirect instead of the file.
- A media host that is slow or blocks automated downloads.
How to fix error 131053
Work through these in order; the first one that turns up a problem is usually the fix.
- Read the details text in the failure for the specific reason.
- Check the file's real MIME type and size, not just its extension.
- Convert to a supported format: JPEG or PNG for images, MP4 with H.264 video and AAC audio for video, PDF for documents.
- Make sure media links are public HTTPS URLs that return the file directly, without login or redirects.
- Host media somewhere fast and reliable, or upload it first and send by media ID.
Should you retry after 131053?
Resending the same file fails the same way. Fix or replace the file, then send again; only retry unchanged if the cause was a temporary outage at your media host.
How error 131053 shows up in InfiQ
If Meta accepts the message and it fails afterwards, InfiQ posts a message.failed webhook for it with metaErrorCode 131053, linked to the message by its ID and wamid. Keep the trace IDs with the failed message: they are what support needs to look it up. Because the failure is discovered after the send is accepted, the API call itself succeeds; watch for the message.failed webhook with metaErrorCode 131053 and read Meta's details text in it.
Frequently asked questions
What media sizes does WhatsApp accept?+
Why does a file that opens fine on my computer fail with 131053?+
Send WhatsApp messages through one clean API
InfiQ's API takes the same message body and returns Meta's errors with a trace ID, so a bad payload is quick to find.