Virtual try-on or virtual fitting: which Sume Format for clothing?
Both are Sume catalog Formats that take a garment still and return 9:16 video. Try-on is an outfit-change reveal; fitting is a fit preview with a small turn.
Use sume-virtual-try-on when the video is a reveal, where a creator changes into the garment. Use sume-virtual-fitting when the video is a fit preview that shows silhouette, sleeve length and drape on the same person with a small turn. Both answer at the sume handle, take a garment still as the clothing reference, and are called like any Format.
What the example briefs say
The catalog ships an example brief for each. They are examples of what the Format was registered with, so treat the wording as guidance and send your own instruction for your garment.
Do not treat the example names as guarantees. The example briefs name a first frame built with ChatGPT Image 2 and an animation with Seedance 2.5 reference-to-video, and the run records the tools that actually ran. Judge the output, not the brief.
| Format | Example brief | Focus |
|---|---|---|
sume-virtual-try-on | A creator changing into a relaxed overshirt, preserving the same face, body, room and camera angle | Outfit reveal |
sume-virtual-fitting | A fitting preview of an oversized shirt on the same person, showing silhouette, sleeve length, fabric drape and a small turn | How the garment fits |
Calling either one
Send POST /v1/formats/sume/sume-virtual-try-on/runs (or sume-virtual-fitting) with a key that has formats:write, an Idempotency-Key, and your garment as an attachment: attachments takes up to 30 images, each as an input_image URL or an asset_id. Put your garment details in instruction and any structured row data in input.
Read the Format first with GET /v1/formats/sume/{slug}. It returns the description and the io profile, and it is the only declared contract for what input expects.
Pick by the job the clip does
- A clip meant to stop the scroll with a quick transformation: try-on.
- A clip meant to answer "how will this fit" on a product page: fitting.
- A catalog of many garments: either one, in a bulk queue with one garment image per item and a cap on each.
- Several angles of one garment: run both and compare, since each run is capped and billed on its own.
Set the cap, then check the result
Each run has the Format's cap, $400 if it never named one, or the number you send up to $500. Send a cap per garment that matches what you would pay for a keeper. The receipt reports usage.billable_amount_usd_micros against the cap. Check the video itself before publishing, because Sume reports whether the run delivered a file, not whether the fabric looks right on your product.
Sources
Related posts
More in Formats
- Weekly series drop: on_active_run reject stops a second render
Set on_active_run to reject and a second episode run on the same Format answers 409 format_run_in_progress instead of starting. skip records a skipped run.
- Which Sume catalog Formats make ad creative: the slugs by ad type
Sume ships 27 ready-made Formats at the sume handle. Which slugs fit which ad type, and how to read one with GET /v1/formats/sume/{slug} before paying.
- Ready-made Formats for product video: the Sume Format catalog
Sume ships ready-made Formats for product and UGC-style video and images, each callable from your backend with one HTTP request at the reserved sume handle.
- What is a Sume Format? Turn an agent thread into one API call
A Sume Format is a saved video recipe your backend calls by handle and slug. One POST runs it in a fresh sandbox and returns media plus optional typed JSON.
Written by Sume