End Frame Control: Stopping an NSFW Clip Where You Want

A generated clip that starts well and ends badly is still unusable. The last frame is what freezes on a preview card, what a loop cuts back from, and what the next clip in a sequence has to match. On most adult video endpoints the ending is whatever the model arrives at. On a few of them it is an input.

Key Takeaways

• Five of the nineteen adult video endpoints on Siray declare end_image. All five are image-to-video. No text-to-video or reference-to-video endpoint has it.
• wan-3.0-i2v-prime-spicy, wan-3.0-i2v-spicy, seedance-2.5-i2v-spicy, and wan-2.7-i2v-uncensored are among them.
• wan-2.7-i2v-spicy does not have it, although wan-2.7-i2v-uncensored does. Same generation, same modality, different field list.
• minimax-h3-i2v-spicy declares five fields in total and end_image is not one of them.
• The field is optional everywhere it appears. Sending only image still works.

Five of Nineteen

The split is not by vendor or by generation. It is by modality. Reference-to-video endpoints take arrays of images but have no notion of a final frame, and text-to-video endpoints have no frames to anchor at all. Only the image-to-video shape supports a start and an end, and even inside that shape it is not universal.

That is worth checking before a pipeline is built around it, because two endpoints with near-identical names can differ on exactly this field.

What Goes In the End Frame

The end frame is a still, supplied as a URL, in the same way as the opening image. Useful choices are a pose the clip has to return to so a loop closes cleanly, the first frame of the next clip in a sequence so two renders join without a jump, or a composition chosen because it works as a thumbnail.

What does not work is treating it as a storyboard. One image is one destination. Nothing in the schema lets you place an intermediate keyframe, so anything between the two ends is still generated.

The Comparison

The Wan 3.0 endpoints reach a two-second floor, which matters when the end frame is being used to close a short loop. Seedance 2.5 starts at four seconds and has no seed, so a run that lands well cannot be reproduced exactly. Wan 2.7 caps at fifteen seconds but keeps both the seed and a negative prompt.

Turn Prompt Expansion Off

Both Wan 3.0 endpoints and the Wan 2.7 spicy endpoint carry prompt_expansion_enable, which defaults to true. When an end frame is specified, an automatically rewritten prompt can describe a motion that does not lead to the frame you supplied. Set it to false for this workflow.

What the Schema Does Not Promise

The spec says the field takes an End frame image URL for image-to-video generation. It does not state how closely the final rendered frame matches the supplied image, whether a distant end frame degrades the middle of the clip, or how far apart two frames can be before the transition breaks. None of that has been measured here. Run a short test at the lowest resolution before committing to a long render, and read pricing from the model detail page in the console rather than estimating it.

For the case where both frames are mandatory rather than optional, see renovation before-and-after videos from two photos. For excluding objects instead of fixing the ending, see NSFW video negative prompts. Related reading: Seedance 2.5 Spicy uncensored video and Wan 3.0 Spicy aspect ratios.

Compare the end frame behaviour across endpoints at console.siray.ai/model-api.

A Note on Compliance

Siray's NSFW models generate legal, consensual adult content only — CSAM and any illegal content are refused with zero tolerance. Uncensored means no excess moderation within the law, not the absence of law. Every example here assumes adult subjects, and any supplied start or end image is assumed to be used with the consent of the people in it and with the rights required to use it. Wan and Seedance models are third-party models available through Siray's API, not Siray-hosted models.