Swap multiple characters in a video with AI: 2 to 4 people

Swap several people in one clip with H3 Max Recast on Sume: one photo per person, left to right by default, up to four, and a price that ignores headcount.

5 min readSume
All posts

To swap more than one person in a video, send H3 Max Recast one reference photo per new person, in the order they should land. Sume's h3-max-recast accepts one source clip of 5 to 30 seconds and 1 to 4 photos in reference_image_urls. fal's schema says the photos replace the main people in the video from left to right, each in every shot they appear in.

So a two-person interview gets two photos: the photo of whoever should replace the person on the left first, the other second. Headcount does not change the bill. Sume prices the job by source seconds and resolution only, and fal says reference images are included at no additional cost.

How does Recast decide who becomes whom?

By default it is positional. fal's schema for reference_image_urls says the photos replace the main people in the video from left to right. Sume passes your list through in the order you send it, so the first URL is the leftmost main person.

Position can be the wrong key. Two people can swap sides mid-shot, or the person who matters can stand on the right. For that, send a prompt. Sume allows one of up to 2000 characters, described in its OpenAPI as who becomes whom or what else to keep or change, and fal calls it optional guidance on character mapping. Neither page gives a prompt grammar, so treat the wording as something to test on a short clip first.

What does a two-person request look like?

This is a Video Router call. duration is not the length you want back: Sume requires the inspected length of your source, in whole seconds rounded up, because the output keeps the source length. Read it with ffprobe first (a 11.2 second clip is 12).

Every URL must be public HTTPS. Signed, private and localhost URLs are rejected before any paid work starts.

curl -X POST https://api.sume.com/v1/video-router/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: recast-duo-001" \
  -d '{
    "model": "h3-max-recast",
    "video_url": "https://example.com/duo.mp4",
    "reference_image_urls": [
      "https://example.com/left-person.png",
      "https://example.com/right-person.png"
    ],
    "prompt": "The person on the left becomes the first photo; the person on the right becomes the second.",
    "resolution": "768p",
    "duration": 12,
    "mode": "async"
  }'

What are the hard limits for a multi-person swap?

Limits from the Sume catalog entry and fal's schema, read 2026-10-03:

  • Sume's catalog says Recast replaces the main people. Neither page promises that bystanders are swapped, so check crowds in the output.
  • A photo that does not match a person on screen is a mapping you have to describe in the prompt.
  • aspect_ratio, generate_audio, frame images and audio references are all rejected; see the full rejected-field list.
H3 Max Recast limits that matter with several people, read 2026-10-03
LimitValueWhere it comes from
Photos1 to 4, one per new personSume catalog; five or more are rejected
Source length5 to 30 secondsSume catalog and fal schema
Longest single shot15 secondsfal schema
Resolution768p (Sume default) or 1080pSume catalog; fal's own default is 1080P
PromptOptional, up to 2000 charactersSume OpenAPI
Who is swappedThe main people in the videoSume catalog and fal schema
PricePer source second, not per personSume billing: list x 1.25

How should I prepare the photos and the clip?

Both vendors are thin on photo guidance: fal says one photo per new person and nothing about framing, and Sume's docs add only the URL rules. What follows is our practical suggestion, not a vendor requirement. Give each person one clear photo of that person alone, so the mapping is unambiguous, and keep the file at a stable public HTTPS address until the job finishes, because the job has to fetch it when it runs.

For the source, pick a clip where the main people stay visible. A clip that is mostly one wide shot of a crowd gives the model little to map. If your footage runs past 30 seconds or has one very long take, read the 30 second trim recipe first, because fal also forbids any single shot over 15 seconds.

What does a multi-person clip cost?

Sume bills fal's per-second list times 1.25: $0.375 a second at 768p and $0.5625 at 1080p. The 12 second duo above is $4.50 at 768p (12 x $0.375) and $6.75 at 1080p. A solo 12 second clip costs exactly the same, so swapping four people is not four times the price.

The cost that does multiply is retries. Because the model is not seedable on Sume, plan on more than one pass whenever the mapping matters, and test the prompt on the shortest valid slice (5 seconds, $1.88 at 768p) before you spend on the full clip.

What should I check in the result?

Watch the first appearance of each person, then any shot where two people cross. fal says each photo replaces its person in every shot they appear in, which is the part worth confirming frame by frame. Source audio is kept, so voices still belong to the original speakers; see whether Recast keeps the audio.

Sume has no seed on this model, so a clip where two people got swapped the wrong way round cannot be re-rolled identically. Resubmit with a clearer prompt and a new Idempotency-Key. Each submit is a new paid job at the same per-second price.

If you only need to change one face and not the person, Sume's Beta face swap is a different tool with its own limits. Only submit photos of people who agreed to appear. Sume's Terms of Service make you responsible for permission to use any person's likeness in content you submit.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume