How to Use Wan 2.5 for Image to Video with ComfyUI
Wan 2.5 image-to-video takes a single still frame and animates it, giving you control over the first shot instead of rolling the dice on a text prompt.
This is the workflow that actually saves time on client work. You already have a product photo, a character sheet, or a location still. Feeding that in keeps the composition and colors stable while the model adds camera movement and small motion. Text-to-video rarely matches a specific brief; image-to-video usually gets close on the first try.
What makes a good input frame?
Use the highest resolution you have, at least 1280px on the long edge. Avoid heavy JPEG compression and avoid images where the whole frame is motion-blurred. Faces should be sharp, since the model will animate whatever detail is present and will not invent missing structure. One subject per frame works better than a crowded scene.
How do you set up the image-to-video workflow?
- Load the Wan 2.5 image-to-video checkpoint in the load node.
- Feed your still through the image encode node.
- Write the motion description in the positive prompt.
- Keep clip length at 3-5 seconds for a first pass.
- Set the sampler to 20-30 steps; below 15 the motion turns mushy.
Generate a five-second test before committing to a long render. On a 24GB card, five seconds of 720p is roughly 3-6 minutes, and 1080p can triple that.
How should you write the motion prompt?
Describe camera and subject movement separately: “slow dolly-in on the bottle, label stays legible, condensation drips on the glass, warm side lighting”. Vague prompts such as “make it cinematic” produce drifting, weightless motion. Concrete verbs help because the model has been trained to respond to camera language like pan, tilt, and dolly.
What are the limits you will hit?
| Limit | Detail |
|---|---|
| Clip length | 5s per generation on most setups |
| Resolution | 1080p at 24fps; higher needs tiling |
| Text in frame | Still distorts over time |
| Hands and faces | Fine in slow motion, breaks on fast turns |
For repetitive shots, render one good clip and reuse it with different edits rather than regenerating. Each rerun costs GPU time even though Wan 2.5 has no per-clip fee.
When does image-to-video beat text-to-video?
When you need a specific look. Brand work, product demos, and narrative shots with a fixed character all benefit. If you are exploring ideas and have no reference, text-to-video is faster to iterate. Many teams run both: text-to-video for mood boards, image-to-video for the shots that get delivered.
Key Takeaways
- Image-to-video locks composition while adding motion.
- Start with a 5-second 720p test before a full render.
- Describe camera moves explicitly, not moods.
- Expect 3-6 minutes per clip on a 24GB card.
