sync-3 image formats JPEG PNG WebP vs Sume image URL rules

sync-3 accepts JPEG, PNG and WebP stills. Sume's docs set URL rules instead: a fetchable public HTTPS image, with private and signed URLs rejected.

4 min readSume
All posts

sync-3 lists JPEG, PNG and WebP as its supported image formats. Sume's docs do not publish a format list for the Fabric still; what they state is the URL rule: image_url must be a fetchable public HTTPS image URL, and private or signed URLs are rejected before generation.

sync-3 facts are from its model page; Sume facts from Media inputs and Avatar 1.0, read 2026-10-01.

What does sync-3 accept?

The page says a single face image works, with JPEG, PNG or WebP, in image plus audio or image plus text (TTS) combinations. For images with several faces it asks for manual speaker selection with coordinates; auto-detect is not supported for images.

What URL rules does Sume apply?

Image URL rules from the Sume docs, read 2026-10-01.
URL typeResult
Public HTTPS imageAccepted
Localhost or private-networkRejected before submission
Non-HTTPSRejected before submission
Signed or private URLRejected before submission
Non-image response or mismatched content typeRejected before submission

How does the still reach the talking-clip route?

The Fabric body is audio_url, measured duration_seconds, and exactly one visual source; the docs prefer image_url of a generated, inspected posed still. Check the live OpenAPI schema for the exact field shapes before you send.

Which format should I send?

The Sume docs only require that the URL serve an image with a matching content type. Since a format list is not published, test with a small request and read the rejection; see lip-sync API with photo and audio.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume