AI video models with 4:3 and 3:4 on Sume: which rows list them
For 4:3 or 3:4 video on Sume, use a Seedance, Wan 3.0 or H3 row. Kling 3, Omni and Veo do not list those ratios. Read 2026-10-13.
If you need 4:3 or 3:4, pin a Seedance, wan-3.0, minimax-h3 or minimax-h3-max row; those list the ratios, while kling-3 lists 16:9, 9:16 and 1:1, Omni lists 16:9 and 9:16, and the Veo rows list 16:9 and 9:16. A request that sends an unlisted ratio to a row gets a 400 rather than a crop.
Where each ratio lives
Square work can go to Kling 3, which lists 1:1 but renders 1080p only; the Seedance, Wan and H3 rows list 1:1 as well.
| Row | Ratios |
|---|---|
Seedance rows, wan-3.0, H3 rows | include 4:3 and 3:4 |
kling-3 | 16:9, 9:16, 1:1 |
gemini-omni-flash-1.1 | 16:9, 9:16 |
veo-3.1 rows | 16:9, 9:16 |
mingmou-1 | 16:9 only |
Why it fails closed
sume/auto clips are 16:9 or 9:16, so a 4:3 request on auto gets 400 unsupported_capability. Pin a model that lists the ratio, then confirm with the filter script in this post.
Sources
Related posts
More in Models
- Veo 3.1 on Sume: Google Cloud rows, 720p, text-to-video only
Veo 3.1, Fast and Lite appear on Sume only where Google Cloud serves them: text-to-video, 720p, 4, 6 or 8 s, 16:9 or 9:16. Check your own list. Read 2026-10-13.
- WAND-Vega for e-commerce video: what Tencent says, what Sume lists
Tencent describes WAND-Vega as trained for vertical industries such as e-commerce. On Sume it is three text-to-video rows, 4-15 s, up to 4K. Read 2026-10-13.
- Which video_url row to call: Omni edit, Recast or Motion Transfer
Three Sume rows accept video_url: gemini-omni-flash-1.1 edits by prompt, h3-max-recast swaps people, higgsfield-genjutsu moves motion. Limits and prices.
- Whistle's 86,174-utterance benchmark: test your own clips first
Cactus Whistle's card reports word error rates over 86,174 utterances. Score 20 of your own clips against a human transcript before choosing it over hosted STT.
Written by Sume