HeyGen photo avatar renders without a reference look (Aug 2026)
HeyGen's August 2026 change lets an Avatar V photo avatar render from the photo alone; motion_prompt still needs a reference look. Sume's photo path, compared.
HeyGen's changelog for August 2026 says an Avatar V photo avatar can now render directly from the photo when its group has no eligible digital-twin or curated reference look, instead of the request being rejected. The fallback applies when reference_look_id is omitted and no eligible look can be picked automatically. motion_prompt still needs an animation reference. On Sume the photo path is two steps: create an avatar from the photo, then render by handle.
What did HeyGen change?
The entry, titled "Avatar V Photo Fallback", says video creation no longer rejects a photo avatar that lacks an eligible reference look. It renders from the photo. It adds that motion_prompt still requires an animation reference for Avatar V photo avatars, and that you should supply an eligible reference look when you need prompted body motion or hand gestures.
So the change removes a rejection; it does not add motion control for photo-only avatars.
| Question | HeyGen | Sume |
|---|---|---|
| Photo as the source | Photo avatar; render from the photo if no look | input.type: "photo" with a public HTTPS image_url |
| Reference look needed to render | No, as of August 2026 | No look concept; the avatar handle is the reference |
| Prompted body motion | Needs a reference look | Not a field on talking-video |
| Reuse | Avatar group | avatar_handle, stored without @ |
How does the photo path work on Sume?
Post the photo to POST /v1/avatar-1.0/generate with an avatar_handle and input.type: "photo". The image_url must be a fetchable public HTTPS image: localhost, private-network, non-HTTPS URLs and non-image responses are rejected before generation.
Poll the job until it completes, then render with POST /v1/avatar-1.0/talking-video using that handle.
curl -X POST https://api.sume.com/v1/avatar-1.0/generate \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: avatar-image-001" \
-d '{
"avatar_handle": "reference_presenter",
"input": {"type": "photo", "image_url": "https://example.com/reference.png"}
}'Which should I pick?
The choice comes down to the motion you need and how you reuse the avatar.
- You want a quick render from one photo and no motion prompt: both routes do this.
- You need prompted hand gestures on a photo avatar: HeyGen's entry says that needs a reference look.
- You want the avatar reused by a short name in code: Sume stores a handle normalized without
@. - Check that the avatar is
readybefore submitting a render on Sume, or the request returnsavatar_not_ready.
Sources
Related posts
More in Comparisons
- Ideogram API keys pause at $0 balance: Sume's 402 insufficient_credits
Ideogram's API is prepaid and its keys pause when the balance hits zero. Sume answers an empty wallet with 402 insufficient_credits. Handle both in code.
- InVideo credits per Seedance video vs Sume Seedance cost
InVideo lists about 13 Seedance 2 fast videos on a $20 plan. Sume estimates a 5-second 720p Seedance 2 fast clip at $1.51. Dated 2026-10-01.
- Kapwing subtitle minutes vs Sume caption job price
Kapwing Pro includes 1,000 auto-subtitle minutes for $16 to $24 a month. Sume charges $0.20 per caption job for a video up to 60 seconds. Dated 2026-10-01.
- Kie.ai API alternative: callbacks, credits and price vs Sume
Kie.ai says it prices 30 to 50 percent below official APIs and returns a task id on HTTP 200. Sume reserves list x 1.25. Here is how the two compare.
Written by Sume