Instagram Messaging API · error code

Instagram error 36003: Image aspect ratio cannot be published (2207009)

Permanent - do not retryHTTP 400Content publishing (posts, reels, stories)

Last verified against Meta for Developers - Messenger Platform error codes

What Instagram returns
The submitted image with aspect ratio {submitted-ratio} cannot be published. Please submit an image with a valid aspect ratio.

What error 36003 means

Code 36003 with subcode 2207009 means the image's width-to-height ratio falls outside what a feed post allows. Meta's recommended solution states the accepted range: 4:5 to 1.91:1. In decimal terms, that is anywhere from 0.8 (portrait) to 1.91 (landscape). The IG User media reference lists the same range for image posts.

The API does not crop for you. The Instagram app lets a person drag a crop box, but the publishing API takes the file as-is and rejects it when the shape is wrong. Tall phone screenshots and 9:16 story artwork sent as feed posts are the usual offenders; ultra-wide banners fail from the other side.

The message includes the ratio Instagram measured, which helps when an image looks fine but carries EXIF rotation that swaps its effective width and height. Stories and reels have their own, much wider ranges and do not trigger this check in the same way, so confirm which media_type you meant to send.

What it looks like

{
  "error": {
    "type": "OAuthException",
    "code": 36003,
    "error_subcode": 2207009,
    "error_user_msg": "The submitted image with aspect ratio 0.5625 cannot be published. Please submit an image with a valid aspect ratio.",
    "fbtrace_id": "KqW8nVs3LcRt5Yb"
  }
}

Why it happens

  • A portrait image taller than 4:5, such as a 9:16 story graphic, was sent as a feed post.
  • A landscape image wider than 1.91:1, such as a website banner, was sent as a feed post.
  • EXIF orientation causes the measured ratio to differ from what the preview shows.
  • The container omitted media_type=STORIES, so a story asset was validated as a feed image.

How to fix Instagram error 36003

  1. 1Compute width divided by height for the served file and confirm it is between 0.8 and 1.91.
  2. 2Crop or pad the image to a supported shape, for example 1:1, 4:5 or 1.91:1.
  3. 3Apply EXIF rotation to the pixels and strip the orientation tag before upload.
  4. 4If the asset was meant to be a story, create the container with media_type=STORIES instead.
  5. 5Create a new container with the corrected image.

How to stop it recurring

Validate aspect ratio in the composer, when the user picks an image, and offer a crop to 1:1, 4:5 or 1.91:1 before the post is saved. Normalize EXIF orientation during processing so the ratio you check is the ratio Instagram sees. Note that carousel images are cropped to the first image's ratio, so keep a carousel's images consistent. Siblings: 36000/2207004 and 36001/2207005.

Official reference: Meta for Developers - Messenger Platform error codes. See all Instagram error codes or the Instagram limits and quotas.

Related codes

Error 36003 - quick answers

What does Instagram error 36003 mean?

Code 36003 with subcode 2207009 means the image's width-to-height ratio falls outside what a feed post allows. Meta's recommended solution states the accepted range: 4:5 to 1.91:1. In decimal terms, that is anywhere from 0.8 (portrait) to 1.91 (landscape). The IG User media reference lists the same range for image posts. The API does not crop for you.

How do I fix Instagram error 36003?

1. Compute width divided by height for the served file and confirm it is between 0.8 and 1.91. 2. Crop or pad the image to a supported shape, for example 1:1, 4:5 or 1.91:1. 3. Apply EXIF rotation to the pixels and strip the orientation tag before upload. 4. If the asset was meant to be a story, create the container with media_type=STORIES instead. 5. Create a new container with the corrected image.

Should I retry after error 36003?

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.