Instagram error 36001: Image format is not supported (2207005)
Last verified against Meta for Developers - Messenger Platform error codes
The image format {current-image-format} is not supported. Supported formats are: {format}.What error 36001 means
Code 36001 with subcode 2207005 reports that the file behind image_url is in a format Instagram's publishing API will not take. The content publishing guide is blunt about what is allowed: JPEG is the only supported image format, and extended JPEG variants such as MPO and JPS are not supported either. PNG, WebP, HEIC, GIF and TIFF all end here.
The message fills in the detected format and the accepted list, so read it - it tells you what Instagram actually received, which is not always what your file extension claims. iPhones save HEIC by default, many CDNs auto-convert to WebP for browsers that accept it, and some design tools export PNG with a .jpg name.
Meta's error table also pairs this subcode with a generic suggestion about missing permissions or an expired token and generating a new container. If the format in the message is genuinely JPEG, do check the token; otherwise convert the image.
What it looks like
{
"error": {
"type": "OAuthException",
"code": 36001,
"error_subcode": 2207005,
"error_user_msg": "The image format webp is not supported. Supported formats are: jpeg.",
"fbtrace_id": "JkT5yRm2WqPz8Nc"
}
}Why it happens
- The image is PNG, WebP, HEIC, GIF or another non-JPEG format.
- The file is an MPO or JPS extended JPEG, often produced by some phone cameras.
- A CDN performs content negotiation and serves WebP or AVIF instead of the stored JPEG.
- The file extension says .jpg but the bytes are a different format.
How to fix Instagram error 36001
- 1Read the detected format in the error message, then confirm it with
fileoridentifyon the downloaded bytes. - 2Convert to standard baseline JPEG before upload.
- 3Disable automatic format conversion on the publishing URL path of your CDN.
- 4Create a new container pointing at the converted file.
- 5If the bytes really are plain JPEG, validate the token and permissions and retry with a fresh container.
How to stop it recurring
Convert every image to plain JPEG in your upload pipeline and store the converted file as the publishing source. Exempt that path from CDN format negotiation so Meta's fetcher always receives the stored bytes. Size and aspect-ratio rules are enforced on the same file - see 36000/2207004 and 36003/2207009.
Official reference: Meta for Developers - Messenger Platform error codes. See all Instagram error codes or the Instagram limits and quotas.
Related codes
- 36000: Image is too large to download (2207004)The image is too large to download. It should be less than {size}.
- 36003: Image aspect ratio cannot be published (2207009)The submitted image with aspect ratio {submitted-ratio} cannot be published.…
- 9004: Media could not be fetched from the URI (2207052)The media could not be fetched from this uri: {uri}
Error 36001 - quick answers
What does Instagram error 36001 mean?
Code 36001 with subcode 2207005 reports that the file behind image_url is in a format Instagram's publishing API will not take. The content publishing guide is blunt about what is allowed: JPEG is the only supported image format, and extended JPEG variants such as MPO and JPS are not supported either. PNG, WebP, HEIC, GIF and TIFF all end here.
How do I fix Instagram error 36001?
1. Read the detected format in the error message, then confirm it with file or identify on the downloaded bytes. 2. Convert to standard baseline JPEG before upload. 3. Disable automatic format conversion on the publishing URL path of your CDN. 4. Create a new container pointing at the converted file. 5. If the bytes really are plain JPEG, validate the token and permissions and retry with a fresh container.
Should I retry after error 36001?
No. Retrying the same request produces the same error; the condition has to be fixed first. Treat it as a permanent failure for that message and surface it, rather than looping.
Stop debugging Instagram by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.