Grok Imagine video length: 1-15 s on xAI, 4-15 s on Sume
xAI allows 1 to 15 seconds for grok-imagine-video-1.5. Sume's catalog row allows 4 to 15, so a 2-second clip needs another id such as wan-3.0.

Grok Imagine video length is 1 to 15 seconds in xAI's docs, and 4 to 15 seconds on the Sume Grok row (duration_seconds: { min: 4, max: 15 }). A 1, 2 or 3 second clip is outside the Sume row.
xAI's range is quoted from its video generation docs, read 2026-09-30. Sume's ranges are from its catalog and Video generation docs.
What are the two ranges?
xAI's page says "The allowed range is 1-15 seconds". Sume's row sets a minimum of 4. Both share the 15-second maximum, which is also the cap for every Sume catalog model not listed as longer.
| Where | Seconds |
|---|---|
| xAI, Grok | 1-15 |
| Sume, Grok | 4-15 |
Sume, wan-3.0 | 2-30 |
Sume, seedance-2.5 | 4-30 |
Sume, gemini-omni-flash-1.1 | 3-10 |
Where can I get a 2-second clip on Sume?
The catalog lists wan-3.0 at duration_seconds: { min: 2, max: 30 }, and the docs say it accepts 2-30 seconds. See Wan 3.0 2-second clips. gemini-omni-flash-1.1 starts at 3 seconds.
What happens if I ask for less than 4 on the Grok row?
The row's advertised minimum is 4, so use the catalog value rather than the xAI value. Read capabilities from the models endpoint instead of copying limits between providers.
What should I do?
Keep one duration table per id in your code, filled from the catalog. If you trim clips later, request the shortest advertised length and cut in an editor or Timeline step.
Sources
Related posts
More in Developers
- HeyGen API key permissions: /v3/api_keys/self vs Sume /v1/me
HeyGen's GET /v3/api_keys/self shows a key's name, scopes and expiry. On Sume, GET /v1/me verifies the key and returns non-secret account metadata.
- HeyGen avatar voice id: default_voice_id vs Sume avatar_handle
HeyGen's PATCH /v3/avatars/{group_id} stores a default_voice_id. On Sume, TTS can take an avatar_handle and resolve that avatar's ready voice.
- HeyGen API idempotency key vs Sume: two different 409s
HeyGen returns 409 request_in_progress for an in-flight retry. Sume returns 409 idempotency_conflict only when a key is reused for a different payload.
- HeyGen Video Agent edit_plan vs Sume preview regenerate
HeyGen's edit_plan revises named scenes in one turn, up to 50 items. Sume has no in-place scene edit: regenerate preview stills, then render.
Written by Sume