One avatar handle, three platform cuts: keep the character consistent
Keep one presenter across LinkedIn, Snapchat and Pinterest by reusing a single avatar_handle and rendering each cut at the right ratio and length with Sume.
To keep one character across LinkedIn, Snapchat and Pinterest, create the avatar once and reference the same avatar_handle in every render. Only the ratio, length and script change per platform. Sume stores the handle without a leading @, so the same presenter comes back every time.
How does the avatar stay the same?
The Create new avatar docs describe three inputs: a prompt, a profile of traits (props) or a reference image (photo). Each request creates a job, and you use the returned handle or resource id for videos. Avatar video requests reference the avatar with a top-level avatar_handle. So the consistency is structural: the same stored avatar, not a fresh prompt per clip.
The honest caveat: the docs say current execution supports one resolved avatar per final video, and scene backgrounds resolve to one shared scene. For a cut with two presenters you need two separate renders.
What changes per platform?
Length and shape change. Here is what the vendor pages I fetched say next to what Sume offers.
| Platform | Constraint from its page | Sume setting to pick |
|---|---|---|
| LinkedIn video | 3 seconds to 30 minutes, MP4, 75 KB to 500 MB | Any ratio; script of 4 to 60 seconds |
| Snapchat Spotlight | MP4, 6 to 60 seconds, at least 540x960 | aspect_ratio 9:16, script of 6 seconds or more |
| Snapchat Story | MP4, 5 to 60 seconds, at least 540x960 | aspect_ratio 9:16, script of 5 seconds or more |
| Pinterest video Pin | mp4, mov or m4v; cover image required | Any ratio; extract a cover frame |
How do you check a look before three renders?
Use a preview. The Avatar video preview route makes the first-frame still without starting the full render. The docs say you can regenerate stills and, once happy, call generate-video on the preview. Preview stills are never caption-burned, and for multi-scene previews later stills are pose-anchored continuations of the first frame.
- Create the avatar once and note the handle.
- Preview the first frame at 9:16 and 1:1, approve the look.
- Render each platform's cut with its own script length and
Idempotency-Key. - Probe each finished file for duration before you upload it.
Request shape for a LinkedIn square and a Snapchat vertical
Same handle, different aspect_ratio. The default is 9:16, and resolution is currently 720p.
curl -X POST https://api.sume.com/v1/avatar-1.0/talking-video \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: host-linkedin-001" \
-d '{"avatar_handle": "product_host", "aspect_ratio": "1:1",
"script": "A short tip for busy product teams."}'What Sume does not promise
Sume does not claim pixel-identical faces across renders, and I found no such guarantee in the docs. The handle gives you the same stored avatar each time; lighting and framing come from each scene prompt, so reuse the same scene text when you want the same room. Publishing to any of the three platforms is outside Sume, as covered in the earlier posts on consistent characters in AI video.
Sources
Related posts
More in Sume Avatar 1.0
- Snapchat Spotlight needs 6 seconds: avatar clips that start at 4
Snap's Public Profile API takes Spotlight videos of 6 to 60 seconds, but Avatar 1.0 plans from 4. Plan scripts at 6 seconds or more and probe before posting.
- Sume Avatar API: canonical routes vs the legacy model-run aliases
Which Avatar 1.0 endpoint should a new integration call? The canonical /v1/avatar-1.0 routes, with the legacy aliases kept for compatibility. All paths listed.
- Tavus Memory Stores vs Sume: personalizing avatar video per person
Tavus PALs now keep persistent memory per participant. Sume avatar videos are one-shot renders, so personalization is in the script you send. Here is the split.
- Introducing Sume Avatar 1.0
Sume Avatar 1.0 is a multi-agent orchestration system as a single avatar model.
Written by Sume