Video
First/last frame
First/last-frame generation gives a video engine both a starting image and an ending image; the model interpolates the motion between them. It is the most precise way to control where a clip ends.
Useful for transitions (an object moves from one composition to another), reveals, and matching a clip to a following one in a storyboard.
On eroq
Supported on the Seedance, Veo 3.1, Kling and Hailuo engines: the start reference plus an end frame, in the composer or the API.
Questions
Which engines support first and last frames?
eroq Motion One, Seedance, Veo, Kling and Hailuo take an end_reference next to the start image; /v1/engines reports it per engine as endFrame. Motion Pro, Runway Gen-4.5, Grok Imagine and Wan 3.0 ignore it.
Does an end frame work without a start image?
Yes, on the engines that take one — an end frame is sent on its own too, and the clip is rendered to land on it. Giving both frames is the tighter setup, since the engine then interpolates between two images you already approve.
What should the two frames have in common?
Enough for the engine to read them as one shot — same subject, same lighting family, same framing distance. Two unrelated images produce a morph rather than a move.