WhatsApp error 131052 (media download error): when a customer's photo or file never reaches you

WhatsApp error 131052 means a customer sent you media, an image, video, voice note, document or sticker, and it could not be downloaded. Meta's error reference calls it "Unable to download the media sent by the user" and explains: "The media included in the WhatsApp user's message could not be downloaded." Meta tells you to check error.error_data.details in the messages webhook triggered when the message was received, and to "ask the WhatsApp user to send you the media file using a non-WhatsApp method." Unlike most error codes, this one is not about something you sent.

Where you see it

131052 arrives on the incoming message, in the messages array of the webhook, not in a failed status for one of your own sends. The customer's phone shows the file as sent. You get a message event with an error instead of a usable media object. Illustrative webhook (the exact type, title and details vary):

{
  "messages": [
    {
      "from": "919876501234",
      "id": "wamid.HBgMOTE5ODc2NTAxMjM0FQIAEhgUM0E...",
      "timestamp": "1761989400",
      "type": "unsupported",
      "errors": [
        {
          "code": 131052,
          "title": "Media download error",
          "message": "Media download error",
          "error_data": {
            "details": "Unable to download the media sent by the user."
          }
        }
      ]
    }
  ]
}

Log from, timestamp and details. They are all you have to follow up with the customer.

131052 or your own download failure?

Many "the customer's photo did not arrive" tickets are not 131052 at all. Use this table before you debug:

The last three are common in home-built integrations that queue downloads for later. The URL Meta returns for a media ID is short-lived, so resolve it immediately before each download attempt rather than storing it.

Why a customer's media fails

Meta does not publish a full list. The details string sometimes gives a hint; otherwise the usual suspects are on the customer's side or in transit:

• the upload from the customer's phone was interrupted on a weak mobile connection
• the file is very large, such as a long video recorded in high resolution
• the file type or a feature of it (for example view-once media) is not handed to the Cloud API
• a temporary problem in WhatsApp's media pipeline

None of these can be fixed from your server, which is why Meta's advice is to ask for the file another way.

What to do

1. Reply in the chat promptly. The 24-hour customer service window is open because the customer just messaged you, so a free-form reply works.
2. Say what happened in plain words and offer an alternative. For example: "Hi Arjun, your photo did not come through on our side. Could you send it again, or email it to support@sunrise-electronics.in?"
3. Offer an upload link for documents that are often large, such as warranty bills or KYC copies.
4. Do not retry anything on your side. There is no media ID to fetch.
5. Track how often it happens. One or two a week is normal. A sudden spike across many customers is worth comparing with Meta's platform status.

A worked example

Sunrise Electronics in Kochi handles warranty claims on WhatsApp. Customers send a photo of the damaged product and the bill. One Saturday, Meera in support sees a message from Arjun with no attachment, and the webhook log shows 131052. From Arjun's side the video of his ₹24,990 washing machine making a noise was sent, with two ticks.

Meera replies within minutes, asks for a short clip under a minute or two photos instead, and offers the claims email as a fallback. Arjun sends two photos, which arrive normally, and the claim is logged. The team adds the same request to their saved replies, so anyone on shift can answer a 131052 in one tap.

Preventing problems with incoming media

• Ask for photos rather than long videos where a photo is enough, in your bot prompts and replies.
• Download valid media immediately after the webhook, with a fresh URL for each attempt and retries with back-off.
• Store your own copy. Meta does not keep media forever, so keep the file in your storage once downloaded.
• Have a saved reply for "we did not receive your file".

How Broadchat handles incoming media

When a customer's media arrives with a media ID, Broadchat downloads it in the background after the webhook, keeps a permanent copy for the Inbox, and retries failed downloads on a schedule, resolving a fresh download URL for each attempt because Meta's URL is short-lived. A download that Meta reports as permanently gone is marked failed instead of being retried. When WhatsApp hands Broadchat a message without its content as type unsupported, the Inbox shows a notice in the chat with a suggestion to ask the sender to resend, instead of an empty bubble. For 131052 the file never reached the platform, so the customer has to send it again.

Related: 131053, when media you send fails, 131051, unsupported message type and the WhatsApp API error codes cheat-sheet.