An image-to-video model treats the frame you upload as the visual anchor and then synthesises change over time: camera movement, fabric and hair motion, a liquid pour, cloud drift. It is a different task from text to video, which has to invent an opening frame first. xAI documents the relationship between the two directly, noting that its text-to-video path generates a first frame and then animates it, so both modes share one image-to-video pipeline underneath. The practical consequence is that the still supplies what exists, and the prompt only decides what moves.
Because the anchor is a real frame, the model never has to guess at the subject. That makes image to video the right mode when a still has already been signed off: a packshot, a portrait, a piece of key art, a diagram, a product label. Reference to video answers a different question, namely what a described subject or scene could look like as a new shot, and start-end to video answers a third, namely how to get from one frame to another. Vendors expose these as separate modes because they accept different inputs and carry different limits, and this site mirrors that split rather than collapsing it.
Model vendors also attach conditions to the frame itself, and those conditions are worth reading before an upload rather than after a rejection. Vidu’s image-to-video endpoint accepts one image, in png, jpeg, jpg or webp, with an aspect ratio narrower than 1:4 or 4:1 and a single file no larger than 50 MB. Kling requires both sides of the frame to be at least 300 px and the aspect ratio to sit between 1:2.5 and 2.5:1. MiniMax takes JPG, JPEG, PNG, WEBP, HEIC and HEIF up to 30 MB, with pixel sides between 256 and 5760 and a width-to-height ratio between 0.4 and 2.5. Veo 3.1 caps an input image at 20 MB. Every rule in this paragraph comes from the vendor that wrote it, not from a setting on this site.