HeyGen avatar new outfit with reference images vs Sume

HeyGen can put an existing avatar in a new outfit by passing the look as avatar_id and up to three reference_images (url, asset_id or base64) on a prompt avatar. Sume's photo input takes a single image_url, so a new look there is a new avatar created from one reference photo.

How does HeyGen's new-outfit call work?

With type: "prompt", an avatar_id makes the referenced look's image condition the result, so the person stays recognisable while the prompt changes outfit and setting. reference_images add wardrobe, style or setting guidance; use them alone for a new character or layered on avatar_id. A crop showing only the garment keeps the reference about wardrobe. Read 2026-10-01.

What does Sume take for a new look?

POST /v1/avatar-1.0/generate with input.type: "photo" and one image_url, plus a top-level avatar_handle. The URL must be a fetchable public HTTPS image; localhost, private-network URLs, non-HTTPS URLs and non-image responses are rejected before submission, per the avatar docs. A product image is a separate field on Avatar Video; omit product_image for a productless video, per Generate avatar video.

What are the differences?

What should I do for several outfits on Sume?

Make one photo of each outfit and create one avatar per look, each with its own handle. One new avatar per look covers naming, and retouching a look from a photo covers fixes to an existing one.