invalid image format? The link is the problem, not the image
A real ticket: the image link was a download grant issued by an application endpoint (access_token with an expiry, capped at 10 downloads), and it answered requests with a Range header with a 416 and a JSON body. The provider did not receive an image, so submission returned a 400 with received: "". The same image submitted as Base64 produced the video.
The new FAQ explains why links like this do not work for server-side fetching, how to choose between a public URL, an asset:// asset ID, and Base64, and gives two curl commands for checking a link. See Seedance Says invalid image format, but the Link Opens in a Browser.
← Back to Live · 📚 Monthly archive