Genjutsu reference images: 30 on Higgsfield, 1 to 8 on Sume
Higgsfield says Genjutsu takes up to 30 reference photos. Sume's Genjutsu Motion Transfer row requires 1 to 8 images, so pick your best eight.
Higgsfield's Genjutsu page says up to 30 reference images. Sume's Genjutsu Motion Transfer row takes 1 to 8: at least one is required and nine or more are rejected. If your character sheet has more than eight images, choose eight before you send the request.
Higgsfield's number is from its Genjutsu page, read 2026-09-30; Sume's is from the catalog in code and the Video generation docs.
How should I budget eight slots?
Sume's docs do not rank images, so this split is a practical suggestion, not a documented rule.
| Slots | Use for |
|---|---|
| 1 to 2 | The face or character, front and three-quarter |
| 1 to 2 | The outfit or wardrobe |
| 1 to 2 | The product or prop that must stay legible |
| 1 to 2 | The location or background, if it changes |
How do I send the images on Sume?
On POST /v1/video-router/generate, send video_url plus reference_image_urls. On POST /v1/videos, put exactly one video and 1 to 8 images in input_references. The provider adapter repeats the rule with the error "Genjutsu requires 1–8 reference image URLs." The image URLs must be public HTTPS URLs.
What if one element drifts?
Swap in a clearer image of that element and run again, dropping a near-duplicate to stay at eight. Reference caps for another model are in Seedance 2.5 reference limits.
Can I split a bigger set across runs?
Yes, but each request is its own job with its own cost, so two runs give two separate outputs, not one merged clip.
Sources
Related posts
More in Developers
- Higgsfield Genjutsu API on Sume: one source video, 1 to 8 images
Genjutsu Motion Transfer on Sume needs exactly one source video plus 1 to 8 reference images. Text-only or malformed bodies are not valid. Request shapes below.
- GitHub Actions retention days: keep the Sume job id elsewhere
From 1 October 2026 GitHub Actions runs, checks and statuses follow the log retention setting (default 90 days). Store Sume job ids outside the log.
- cancel-in-progress killed my workflow; does the Sume job stop?
Cancelling a GitHub Actions run does not cancel a Sume job. Cancellation only works before generation starts, so store the job id and cancel it explicitly.
- GitHub Actions dropped Node 20: calling Sume needs no Node
Node 20 is gone from GitHub Actions runners. Sume's CLI is a native binary and the API is plain HTTPS, so a workflow step can call it with no Node version.
Written by Sume