Before a Recast swap with hired talent: a 4-person release checklist
H3 Max Recast uses one photo per person, up to 4. A process checklist for approvals and YouTube disclosure before you spend $0.375 per second.
H3 Max Recast on Sume puts up to four people into a source video using one photo per person, so before you submit, you need a photo and an agreement for each person. This checklist is a process suggestion, not legal advice. The Sume parts are facts from the docs: one to four photos, public HTTPS URLs, 5 to 30 seconds, $0.375 per second at 768p.
What Sume needs and what it cannot check
Sume's API checks that the photo URLs are public HTTPS links and that there are one to four of them. It cannot check that the person in a photo agreed to appear in the result. That check is yours.
| Step | Why |
|---|---|
| One written approval per photographed person | Recast uses each photo as a person in the final video |
| Say how long the result will be used | Output length equals the source length, 5 to 30 s |
| Keep the photo, source and result together | You will need them if someone asks what was swapped |
| Check disclosure rules for the platform | YouTube asks for disclosure of realistic content showing a real person doing something they did not |
| Test at 768p first | 5 s costs 5 x $0.375 = $1.875 |
Disclosure
YouTube's help page (read 2026-10-08) asks creators to disclose realistic content that makes a real person appear to say or do something they did not do, and says the label does not limit the audience or affect monetization. If your four people are real and recognisable, assume the label applies. Where a jurisdiction has its own digital-replica rules, check them before you publish; Sume's blog covers some of these in other posts.
Cost of a full job
A 20-second source with four photos at 768p costs 20 x $0.375 = $7.50. At 1080p it costs 20 x $0.5625 = $11.25. Run the cheap version for approvals, and only render the 1080p version once each person has signed off on how they appear.
Keeping records
Store the approval, the photo, the source video URL, the Sume job id and the date together. Sume returns durable media URLs for results, which are useful for the record. If a person later withdraws consent, you will want to know which published clips used their photo.
Decide the scope of each approval before you pay. A person may agree to appear in a 20-second ad but not in six variants; six variants at 768p cost 6 x $7.50 = $45.00 at 20 seconds each.
Do not use a photo that you do not have the right to use. The Sume API checks only that the link is a public HTTPS image.
Sources
Related posts
More in Use cases
- Indie game trailer: one 30 s Seedance 2.5 job, 480p then 720p
A 30-second game trailer on Seedance 2.5 is $8.07 at 480p, $17.34 at 720p and $42.65 at 1080p on Sume. Draft cheap, pay once for the final.
- Instagram 4:5 portrait image API: 14 Sume models list 4:5
Fourteen of the 18 Sume image rows list 4:5, from Qwen Image at 3 cents to GPT Image 2 at 27 cents. The table, plus what the 1080x1350 post-step means.
- Instagram Reels blurry or low resolution: probe before posting
Instagram lists blurry, low-resolution Reels among those it may show less. Check width, height and fps with Sume video inspect, then look at full-size stills.
- Instagram says muted Reels are shown less: check has_audio
Instagram's help page lists muted Reels among those you may see less often. Probe has_audio with Sume video inspect, then add sound with a Timeline render.
Written by Sume