Instagram Messaging API · error code

Instagram error 352: Video format is not supported (2207026)

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

Last verified against Meta for Developers - Messenger Platform error codes

What Instagram returns
The video format is not supported. Please check spec for supported {video} format

What error 352 means

Code 352 with subcode 2207026 is Instagram rejecting the video file itself. Meta's recommended solution is to have the user upload an MOV or MP4 (MPEG-4 Part 14) and to check the published video specifications. Re-sending the same file will fail every time.

The container format is only the first gate. Meta's IG User media reference lists detailed specs for reels and stories that a technically valid MP4 can still miss: HEVC or H264 video with progressive scan, closed GOP and 4:2:0 chroma subsampling; AAC audio at up to 48 kHz in mono or stereo; 23-60 FPS; and a VBR bitrate of up to 25 Mbps. Reels must run between 3 seconds and 15 minutes and stay under 300 MB; stories are limited to 60 seconds and 100 MB.

Files exported from screen recorders, phones in HDR modes, or editing tools set to ProRes or VP9 are frequent offenders. A transcode is almost always the answer.

What it looks like

{
  "error": {
    "type": "OAuthException",
    "code": 352,
    "error_subcode": 2207026,
    "error_user_msg": "The video format is not supported. Please check spec for supported video format",
    "fbtrace_id": "HcR9wPn4KsVm6Tg"
  }
}

Why it happens

  • The file is not MOV or MP4, for example WebM, MKV or AVI.
  • The MP4 wraps an unsupported codec such as VP9, AV1 or ProRes.
  • Audio is in a format other than AAC, or exceeds the documented sample rate or channel count.
  • The file uses interlaced video, an open GOP structure, or an out-of-range frame rate.

How to fix Instagram error 352

  1. 1Run ffprobe on the file and compare codec, frame rate, bitrate and audio against Meta's reel or story specs.
  2. 2Transcode to H264 or HEVC video with AAC audio in an MP4 container, progressive, 4:2:0, at 23-60 FPS.
  3. 3Keep video bitrate at or under 25 Mbps VBR and respect the duration and file-size limits for the media type.
  4. 4Create a new container with the transcoded file's URL; the failed container cannot be reused.
  5. 5Re-test with a known-good short MP4 to rule out hosting problems.

How to stop it recurring

Normalize every video before it reaches the publishing API: one transcode profile that produces H264 or HEVC plus AAC in MP4, capped bitrate, fixed frame rate. Validate duration and size against the media type at upload time in your UI so users fix problems before scheduling. Fetch failures and slow downloads are separate errors, listed under 9004/2207052.

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

Related codes

Error 352 - quick answers

What does Instagram error 352 mean?

Code 352 with subcode 2207026 is Instagram rejecting the video file itself. Meta's recommended solution is to have the user upload an MOV or MP4 (MPEG-4 Part 14) and to check the published video specifications. Re-sending the same file will fail every time. The container format is only the first gate.

How do I fix Instagram error 352?

1. Run ffprobe on the file and compare codec, frame rate, bitrate and audio against Meta's reel or story specs. 2. Transcode to H264 or HEVC video with AAC audio in an MP4 container, progressive, 4:2:0, at 23-60 FPS. 3. Keep video bitrate at or under 25 Mbps VBR and respect the duration and file-size limits for the media type. 4. Create a new container with the transcoded file's URL; the failed container cannot be reused. 5. Re-test with a known-good short MP4 to rule out…

Should I retry after error 352?

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.