20-second talking clip: Fabric 720p $3.75 vs Avatar Standard $3.68

For 20 seconds, VEED Fabric 720p on Sume bills $3.75 (20 x $0.1875) and Avatar Video Standard $3.68 (20 x $0.184). The inputs differ: audio + still vs a script.

5 min readSume
All posts

A 20-second talking clip costs $3.75 on VEED Fabric 1.0 at 720p and $3.68 on Sume Avatar Video at the Standard tier, so the two are within 7 cents. Which one to use depends on what you already have: Fabric needs a still and recorded audio, Avatar Video needs an avatar and a script.

Price side by side

Fabric is priced per ceil(audio second): $0.1875 at 720p and $0.10 at 480p. Avatar Video Standard is $0.184 per second without a product image. Pricing as of 2026-10-08.

20-second clip, as of 2026-10-08
RouteRateArithmeticCost
Fabric 720p$0.1875 per audio second20 x $0.1875$3.75
Fabric 480p$0.10 per audio second20 x $0.10$2.00
Avatar Standard$0.184 per second20 x $0.184$3.68
Avatar Plus$0.245 per second20 x $0.245$4.90
Avatar Max$0.55 per second20 x $0.55$11.00

What you supply

The models page says every shot where a person speaks on camera is Fabric with an accepted still plus TTS, and that video models do not lip-sync to generated TTS or a later voice-over. Fabric takes audio_url, a measured duration_seconds and one visual source: the preferred image_url of an inspected posed still, or an avatar_handle, never both.

Avatar Video starts from an avatar and a script, or from multi-scene video_inputs, with optional product and scene references and inline captions.

  • Fabric: you control the voice recording or TTS and the exact still.
  • Avatar Video: Sume plans the clip from your script; 4 to 60 seconds.
  • Fabric accepts up to 300 seconds of audio; Avatar Video stops at 60.

How to choose

If you have an approved voiceover and a still, Fabric at 480p is the cheapest of the five rows at $2.00 for 20 seconds. If you want a reusable presenter and only have text, Standard Avatar Video at $3.68 is the lower-cost entry. The 7-cent gap between Fabric 720p and Standard is not the deciding factor.

Practical notes

Media inputs. Any media field, whether product_image, scene.image_url or an avatar image_url, must be a fetchable public HTTPS URL. Sume rejects localhost, private-network and non-HTTPS addresses before it submits anything, so a broken link fails fast instead of consuming a render. Host reference images where Sume can fetch them and keep them available until the job finishes.

Reading results. A completed result can include public media.sume.com video artifacts, and for avatar videos also public-safe preview fields such as preview_image_url and scene_previews. You can list or read finished videos with GET /v1/avatar-videos and GET /v1/avatar-videos/{id}. Store the job id and the video id together so a billing line can be traced back to a creative.

Reusable avatars. An avatar is created once, for a flat $0.95, and then referenced by its avatar_handle on every later request. Sume normalizes a leading @ away and stores the handle without it. Treat the handle as a stable identifier in your own system, and keep one record per handle noting who the avatar represents and what it may be used for.

Sources

Related posts

More in Comparisons

All Comparisons posts

Written by Sume