TikTok upload error: file_format_check_failed

Per TikTok's Content Posting API media transfer guide, a video upload needs to fall within these documented bounds:

• Container: MP4 (recommended), WebM, or MOV.
• Video codec: H.264 (recommended), H.265, VP8, or VP9.
• Frame rate: minimum 23 fps, maximum 60 fps.
• Resolution: minimum 360px on both height and width, maximum 4096px on both.
• File size: maximum 4GB.

That is the documented, checkable list. TikTok's guide does not publish a minimum bitrate or a specific audio codec requirement for the Content Posting API upload step itself — do not assume a number you saw in a consumer-app video-specs roundup applies to this API endpoint unless it traces back to this page.

TikTok's own documentation does not define file_format_check_failed as a named error with a documented root-cause list — it is a message developers encounter from the API, not a code TikTok explains in its reference docs. That matters because it means there is no official checklist to compare your rejection against beyond the general format requirements above.

It also means you should not assume the rejection is always a genuine spec violation. There are credible developer reports of this exact error firing on files that already matched the documented container, codec, resolution, and frame-rate requirements — one widely discussed case involved a 1080×1920 MP4 encoded with H.264 video and AAC audio at roughly 59.94 fps and a bitrate well within normal range, rejected consistently with file_format_check_failed on both private and public accounts, with no resolution beyond the report itself. Keep that possibility in mind before you sink hours re-encoding a file that was already compliant.

Work through these in order — most "my file meets the spec" assumptions turn out to be wrong on close inspection:

• Check the real codec, not the file extension. A file named .mp4 is not guaranteed to contain H.264/H.265 video — inspect it with ffprobe rather than trusting the extension or what your export tool claims.
• Confirm actual resolution and frame rate against the 360–4096px and 23–60fps bounds, including for variable frame rate sources — a screen recording or a phone clip with a fluctuating frame rate can report a nominal fps that does not match what is actually encoded frame to frame.
• Verify file size is comfortably under 4GB, accounting for any re-encoding or container remuxing your pipeline does after the file leaves your validation step.
• Rule out an unusual color space or bit depth. 10-bit or HDR-encoded video is a common source of format-check failures across social platforms generally, even when the container and codec name look correct.
• Check the container is genuinely playable end to end, not just that it opens — a partially transcoded or improperly finalized file can pass a basic open-and-preview check while still failing a stricter server-side validation.

Do not retry the identical file — repeating the exact same upload will not produce a different result. Instead, re-encode from source with conservative, well-tested settings: H.264 video in an MP4 container, AAC audio, a standard (not variable) frame rate within the 23–60fps range, and 8-bit color. Re-encoding with a mainstream tool and mainstream settings, rather than whatever your original export pipeline produced, resolves this for a meaningful share of reports even when the original file looked compliant on paper.

If a conservatively re-encoded file still fails, that is worth escalating to TikTok support with the exact file (or its ffprobe output) attached, since this is one of the cases where the platform-side validation logic is not fully documented and TikTok is the only party who can confirm what actually tripped it.

PostGate validates media against each platform's known requirements before it ever reaches TikTok's upload step — see Media for how assets move through pending, uploaded, processing, and ready states, with a failed asset carrying structured evidence under error instead of an opaque platform message. If TikTok rejects a file that passed PostGate's own validation, that distinction is visible in the delivery evidence rather than buried in a generic failure.