Write motion as measurable numbers so image-to-video actually moves through the frame instead of marching in place.
Disclaimer: All content shown on this page is generated by AI models and is for reference only; it does not constitute any guarantee of results. Actual output and Credits consumption are subject to "Usage Details" in the console.
wan2.7-image (produce the first frame, place the character at about 25% from the left of the frame, place evenly spaced reference markers in the scene as a ruler) → happyhorse-1.1-i2v (drive the walk with a timeline + displacement-percentage constraint).
Result
The output 5-second walking shot (camera fixed, character crossing the wall corridor from left to right):
The starting first frame places the character at about 25% from the left of the frame, with evenly spaced lanterns on the wall serving as "rulers":

Step: Pin down motion with numbers
Send the first frame along with the following prompt to happyhorse-1.1-i2v:
Notes
- Consumption: This playbook involves image generation + image-to-video. Motion-controlled shots aren't guaranteed to land on the first try; you may need several iterations. Video consumption is high—start with 5 seconds / 720P to validate the motion before deciding whether to extend or raise the resolution.
- Stability: Motion control is the least stable part of image-to-video; running the same prompt multiple times will produce different results. When reviewing, don't just check whether there's movement—check whether the character has actually displaced relative to the reference markers in the scene, which is why the first frame must include evenly spaced reference markers.
- Tuning: To make displacement more obvious, break the timeline down more finely (one position per second), raise the N in "pass at least N reference markers," and keep "camera completely fixed" non-negotiable.