Render a 2-minute video with the Timeline API: $0.20
Sume Timeline 1.0 renders at $0.10 per ceil(output minute), so 2 minutes of finished video is $0.20. Compose and audio steps are $0.02 and $0.01 per job.
Rendering a 2-minute video on Sume's Timeline costs $0.20: the public rate is $0.10 per ceil(output minute). A 2-minute output bills 2 minutes.
Source: the Timeline docs, read 2026-10-06. The reserve is ceil(audio.duration_seconds / 60) minutes, and the job uses no AI model, so the cost does not depend on resolution.
What else is on the bill?
Timeline audio and compose steps are fixed per job:
| Step | Price |
|---|---|
| Timeline render | $0.20 for 2 min |
| Timeline audio (per job) | $0.01 |
| Timeline compose (per job) | $0.02 |
What should I know?
Keep a 61-second cut at 60 seconds if you can.
- Renders past 12 segments chunk automatically with
render.strategy: auto. strategy: singleabove 12 slots returnsrender_strategy_unsafe.- Billing rounds the output minute up: 61 seconds bills 2 minutes.
Sources
Related posts
More in Media tools
- Render a 3-minute video with the Timeline API: $0.30
Sume Timeline 1.0 renders at $0.10 per ceil(output minute), so 3 minutes of finished video is $0.30. Compose and audio steps are $0.02 and $0.01 per job.
- Render a 5-minute video with the Timeline API: $0.50
Sume Timeline 1.0 renders at $0.10 per ceil(output minute), so 5 minutes of finished video is $0.50. Compose and audio steps are $0.02 and $0.01 per job.
- Timeline transition_not_frame_aligned: why a 0.01 s fade fails
A Timeline fade under half a frame rounds to zero frames and is refused with transition_not_frame_aligned. How many frames a fade is at 24, 25, 30 and 60 fps.
- transition_snapped_to_frame: a 0.3 s fade at 25 fps is 8 frames
Timeline rounds a fade to whole frames and reports transition_snapped_to_frame as a warning, not a failure. What 0.3 s becomes at 24, 25, 30 and 60 fps.
Written by Sume