Wan 3.0 vs MiniMax H3: clip length, ratios and reference caps

The two differ mainly in clip length and frame shape. On Sume, wan-3.0 makes clips of 2 to 30 seconds at 480p, 720p or 1080p, while minimax-h3 makes 5 to 15 seconds at native 480p or 768p and adds a 21:9 ratio. Both accept image, video and audio references and can generate audio. This page compares limits only, not output quality.

Sume limits are from Video generation; Wan facts from fal's Wan 3 page and H3 facts from MiniMax's H3 post, all read 2026-09-29.

How do the limits compare?

Which is longer in one request?

Wan by a wide margin: 30 seconds against H3's 15. fal's page gives Wan 3 the same 2 to 30 second range, and MiniMax's post says H3 makes up to 15 seconds at 2K, with 768p also available. On Sume the 2K and 4K H3 outputs are upscales, priced if you request them, so the native sizes above are what you generate.

Do both make audio?

Yes. fal says Wan 3 generates audio in the same pass, and MiniMax says H3 produces native stereo sound. On Sume, generate_audio defaults to each model's audio capability, and GET /v1/videos/models reports it per model.

Which ratios matter for vertical?

Both list 9:16, so a Reels or Shorts clip works on either. The one shape only H3 accepts is 21:9. Send the ratio explicitly:

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: wan-h3-001" \
  -d '{
    "model": "minimax-h3",
    "prompt": "A skater crosses an empty plaza at dusk",
    "duration": 8,
    "resolution": "768p",
    "aspect_ratio": "21:9"
  }'

What is the practical split?

• Need more than 15 seconds in one clip, or under 5: use wan-3.0.
• Need a 21:9 frame: use minimax-h3.
• Need 1080p natively: use wan-3.0; the H3 variant that lists 1080p is minimax-h3-max, a latent refinement from 768p.
• Unsure: read supported_durations and supported_resolutions from GET /v1/videos/models and test one short clip on each.