Skip to main content
HTTP Status: 422

Reasons and How to Fix

Unsupported Format

POST /remove detects the media type from the file content. MP4, MOV, WebM, M4V and MKV containers are accepted as video. AVI, WMV, FLV, image sequences and audio-only files are rejected. GIF and animated WebP files are handled by the image path, so a GIF is still rejected (invalid_image) and an animated WebP uses its first frame; neither is treated as a video. Nothing is billed. To fix:
  • Convert the file to MP4 (H.264) before uploading

No Video Stream

The container is fine but it contains no video track (for example an .mp4 that only holds audio). Check the file with ffprobe:

Corrupted or Truncated File

The file may have been cut off during download or upload, or is not a video at all. To fix:
  1. Verify the file plays in a video player
  2. Re-download or re-export the source video
  3. Check that you are sending the file bytes, not a path string

URL Did Not Return a Video

When using url, the URL must return the raw video file. A page that embeds a video (a YouTube or Vimeo page, a Google Drive preview) is HTML, not a video. Use a direct download link, and make sure it is publicly reachable without cookies or authentication.

Wrong Extension

The media type is detected from the file bytes, not the extension or the field name. Renaming a .gif to .mp4 does not make it an MP4: it still takes the image path and is rejected with invalid_image. Convert it with ffmpeg as shown above.

Need Help?

Contact us at support@poof.bg with your request_id and the video (if possible).