Timeline 1.0 limits: 200 slots, 1800 s, 20 audio parts, 8 fades
The numbers that cap one Timeline 1.0 render: 1 to 200 video slots, 1 to 1800 s of audio, 20 audio parts, 12-slot single strategy and 8 chained fades.
One Timeline 1.0 render takes 1 to 200 video[] slots and an audio spine of 1 to 1800 seconds, so the longest output is 30 minutes. Audio can be built from at most 20 audio.parts[], and a run of more than 8 adjacent fades is refused.
All numbers are from the Timeline 1.0 docs, read 2026-09-30.
What are the hard caps?
Required: audio.duration_seconds from 1 to 1800 and video[] with 1 to 200 slots. output.width and output.height are even integers from 256 to 2160; output.fps is 24, 25, 30 or 60, or omit it to match the sources. Default output is 1080x1920.
| Field | Cap |
|---|---|
| audio.duration_seconds | 1 to 1800 |
| video[] slots | 1 to 200 |
| audio.parts[] | At most 20 |
| adjacent fades | At most 8, else too_many_chained_transitions |
| transition duration | At most 1 s |
| edge fades | 0 to 5 s each |
Does a long timeline render in one piece?
render.strategy defaults to auto, which chunks past 12 segments. single is refused above 12 slots with render_strategy_unsafe. Use POST /v1/timeline-1.0/plan (unbilled) to see segment_count and billable_minutes before you submit.
How is the price counted?
The public rate is $0.10 per ceil(output minute). The reserve is ceil(audio.duration_seconds / 60) minutes, so a 1800 s spine reserves 30 minutes. Confirm the live rate in GET /v1/catalog.
What if I need more than 1800 s?
The docs give 1800 s as the ceiling for audio.duration_seconds and do not describe a longer single render. Two sources on screen at once are a separate step: Timeline compose builds one shot of at most 300 s, which you then drop into video[].
Sources
Related posts
More in Developers
- Timeline render warnings: padded or looped short sources explained
A Timeline 1.0 slot longer than its source renders with a soft warning, not a failure, and /plan cannot predict it. Read warnings[] and probe clips first.
- Token bucket vs fixed window: what a reset header means
Anthropic says its limits replenish continuously; Sume's docs call ratelimit-reset the seconds until the window resets. How to pace a client for each.
- Trim and conform a clip to 1080x1920 at 30 fps in one call
video-trim takes an optional output {width, height, fps} that conforms on the way out, exact precision only. Width and height 256-2160, fps 24, 25, 30 or 60.
- Vercel rewrite to an external API times out at 120 seconds
Vercel proxied rewrites to an external destination time out at 120 seconds with ROUTER_EXTERNAL_TARGET_ERROR. A Sume async submit returns at once.
Written by Sume