Kling motion control or Recast: a photo moves, or people get swapped
Kling 3.0 motion control moves one photo with a reference video; h3-max-recast swaps people inside your footage. Cost per 10 seconds and how to choose.

Both tools take a video and a photo, and both can make a person in your photo appear to do what someone in your video does. The difference is the starting point. Kling 3.0 motion control starts from your still photo and drives it with the motion of a reference video, so the result is a clip of the photo's subject performing that movement. h3-max-recast starts from your video and replaces the people in it with the people in your photos, keeping the original camera, cuts and sound. Pick Kling when the photo is the scene, and Recast when the footage is the scene.
On Sume the two also bill differently: motion control at about $0.1575 per second, Recast at about $0.375 per second at 768p (both list prices times 1.25, read 2026-10-03).
What each one takes in
Kling motion control is a Sume model-run surface of its own, not a Video Router id. It takes one visual source, either a public image_url or a ready avatar, plus a required motion_video_url that drives all output motion. You declare duration_seconds (1 to 30) so Sume can price the job; the provider has no duration knob and the output length follows the driving video. keep_original_sound defaults to true and character_orientation is video by default, or image if you want the photo's facing to win.
Recast is a Video Router id. It takes a source video_url and 1 to 4 reference_image_urls, one per person, and the output keeps the source's motion, camera, cuts and audio. The source must be 5 to 30 seconds with no shot over 15, and Recast's resolution is 768p or 1080p.
| Question | Kling 3.0 motion control | h3-max-recast |
|---|---|---|
| Starting point | One still photo (or ready avatar) | One source video |
| What drives motion | A reference motion video | The source video itself |
| People in the output | The photo's subject | The people in your photos, in the source's shots |
| Camera and cuts | Not carried from your photo | Kept from the source |
| Source video length | Driving video, 1 to 30 s declared | 5 to 30 s, no shot over 15 s |
| Sound | keep_original_sound, default on | Source audio kept |
| List price | $0.126 per second | $0.30 (768p) or $0.45 (1080p) per second |
| Through Sume (x 1.25) | about $0.1575 per second | about $0.375 or $0.5625 per second |
Worked cost for a 10-second clip
At 10 seconds the arithmetic is simple. Kling motion control reserves 10 times $0.126 times 1.25, which is $1.575 and rounds up to $1.58. Recast at 768p is 10 times $0.30 times 1.25, $3.75, and at 1080p $5.63. So motion control is less than half the price per second of Recast at its cheaper tier. The comparison is only fair when both give you what you need, and they usually do not: a motion-control clip has no original camera or cuts from your footage, and a Recast clip has no way to make a photo do a new movement.
Use that to decide on need first and price second. If the deliverable is "the existing ad, but with a different person", only Recast fits. If the deliverable is "my mascot photo doing this dance", only motion control fits.
A motion-control request, for contrast
The body below is the documented shape. There is no reference_image_urls or model field; the URL itself identifies the model, and the strict body rejects Video Router vocabulary.
curl -X POST https://api.sume.com/v1/kling/3.0/motion-control \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: kling-mc-001" \
-d '{
"image_url": "https://example.com/mascot.png",
"motion_video_url": "https://example.com/dance.mp4",
"duration_seconds": 10,
"keep_original_sound": true,
"character_orientation": "video",
"mode": "async"
}'Picking in practice
Run through three questions. Does the output need your original camera work and cuts? Then Recast. Does the output need a single character from a photo to move in a specific way? Then motion control. Is the person in the source a real individual whose likeness you are replacing? Then make sure you have the right to use both the source performance and the replacement face; Sume documents the tools, not your clearance to use them.
For the many-people case, Recast takes up to four photos in one call, one per person, while motion control is a one-image surface. For a deeper look at Kling's prices at 30 seconds see Kling motion control price per second and the cost of a 30-second clip, and for reference-video requirements see Kling motion control reference video requirements.
What neither does
Neither is a free-form prompt edit and neither writes new dialogue. Both keep or take audio from the video you supply rather than creating a voice for the new person. If you need speech from a still image with your own audio, that is the lip-sync surface, which has its own 5 to 14.8 second window. The practical outcome is a pipeline: choose the motion tool, then add captions or a voice step afterward.
Sources
Related posts
More in Comparisons
- Luma Ray 3.2 10-second clip cost vs Sume's video models
Luma's API lists a 10 second Ray 3.2 clip at $0.45 (540p), $0.90 (720p) and $3.60 (1080p). Sume's H3 Max is $1.00 at 768p and $2.00 at 1080p; Wan 3.0 is $2.50.
- Luma Ray3.2 API prices are approximate; Sume reserves at submit
Luma's API page says its prices are approximate and based on billing tokens; 10 s costs 3x 5 s at 1080p. Sume reserves provider list x 1.25 at submit.
- Luma Ray 3.2 video-to-video vs Sume H3 Max Recast: 10 s cost
Luma lists 10 s Ray 3.2 video-to-video at $2.16 (720p) and $4.32 (1080p). Sume's H3 Max Recast is $3.75 (768p) and $5.625 (1080p), per source second.
- Micro-drama lead: Avatar 1.0 or Seedance 2.5? Pick by dialogue
Pick Sume Avatar 1.0 for talking to camera and Seedance 2.5 for a lead who moves through places. Cost per minute: $14.70 against $34.67.
Written by Sume