Seasonal sale video: re-skin your own footage with sume-restyle
Reuse one product clip for a holiday sale by calling sume-restyle, which keeps motion, timing and cuts and rewrites the look. Inputs, limits and checks.

To make a seasonal sale video from footage you already have, call the sume-restyle Format. Sume's own description of it says it takes a clip you attach, keeps its motion, timing and cuts, rewrites the look, and puts your original audio back on the timeline. That suits a sale: one filmed demo can become a winter version and a spring version without a reshoot.
What the Format is described to do
The sume-restyle slug is in the catalog at the sume handle. The wording in the Format's example prompt is specific: use the attached packshot as the product reference for the look, restyle the attached clip, and rebuild it "chunk by chunk" before reassembling it with the original audio. Treat that as the intended use, not as a guarantee of any result, and run it once before you build a campaign on it.
A request for a sale variant
Attach the clip and one packshot. The attachment budget allows up to 10 videos, 10 audio files and 30 files in total, as listed in the call docs. State the season in instruction and keep the product colours explicit, because the look is what changes. One run per variant is simplest: each has its own receipt, spend cap and idempotency key, for example sale-winter-v1 and sale-spring-v1.
- Keep the instruction under about 4000 characters; only that much is carried as prompt text.
- Name the palette, light and props for the season, and what must stay the same.
- Set
generation_spend_cap_usdfor each variant, then compareusage.billable_amount_usd_micros.
Checking the variants
A restyled clip should keep the original length. Compare duration_ms on the artifact with the clip you attached. If the length differs, continue the run with previous_run_id and an instruction that names the cut to fix.
| Check | Source | Pass condition |
|---|---|---|
| Same length as the source | artifacts[].duration_ms | Equal to the source clip, within your tolerance |
| Run finished | status | completed |
| Within budget | usage.billable_amount_usd_micros | Below the cap you sent |
| Audio kept | Listen to the file | Matches the original track |
When you have many variants
For ten stores or ten seasons, queue them: a bulk request takes 1 to 100 items with a window of 1 to 16 runs. Each item is a full single-run body, so each carries its own attachment list and cap.
Rights and expectations
Only attach footage you own or have the right to change. The Format works on your footage, and the result is still your responsibility, including any claims about price or dates that appear in the video. Put the sale terms in the post text and not in the frame if you can, because on-screen numbers are the most likely thing to come out wrong in a generated look.
The example prompt names Seedance 2.5 as the model that does the work. We did not check Sume's price for it here, so for a cost figure use the cap you send and the usage block on the receipt, and read the video model docs for list prices.
Sources
Related posts
More in Use cases
- YouTube Shorts Over 60 Seconds: Why a Music Claim Blocks the Video
A YouTube Short longer than one minute with an active copyright claim is blocked worldwide. What that means for music choices, with Sume's Music Router noted.
- Silent captioned Reel: drop the audio first, burn with words
To burn captions on a Reel with no sound, run STT first, trim with audio drop, then send your own words: $0.02 + $0.01 + $0.20 = $0.23.
- Six Nano Banana 2.1 start frames, six Wan 3.0 clips: a 3-min Short
Six 9:16 Nano Banana 2.1 stills ($0.60 at 1K) feed six 30 s Wan 3.0 jobs as first frames: $23.40 at 720p for a 180-second Short, with Timeline.
- Six podcast ad-read variants at 500 characters: TTS cost and tags
Six 500-character ad reads cost $0.1425 on Sume TTS ($0.02375 each). Tag each take with the metadata field and one Idempotency-Key per variant.
Written by Sume