Timeline 1.0 rounds up by the minute: 61 seconds is $0.20, 60 is $0.10
Timeline 1.0 charges $0.10 per ceil(output minute). A 60 s video is $0.10, 61 s is $0.20, 100 videos of 45 s cost $10.00 and of 61 s cost $20.00.

The short answer
Sume's Timeline 1.0 charges $0.10 for each output minute, rounded up. A video up to 60 seconds long costs $0.10; one second more costs $0.20, because the rounding takes 61 seconds to two minutes. For 100 videos, 45 seconds each costs 100 x $0.10 = $10.00, and 61 seconds each costs 100 x $0.20 = $20.00. Trimming 1 second from each of the 61-second videos halves the assembly bill.
Price by output length
The docs give the public rate as $0.10 per ceil(output minute), and the render reserve is ceil(audio.duration_seconds / 60) minutes. The job uses no provider inference, only worker ffmpeg.
| Output seconds | Billable minutes | Price |
|---|---|---|
| 30 | 1 | $0.10 |
| 59 | 1 | $0.10 |
| 60 | 1 | $0.10 |
| 61 | 2 | $0.20 |
| 90 | 2 | $0.20 |
| 120 | 2 | $0.20 |
| 121 | 3 | $0.30 |
| 1800 | 30 | $3.00 |
Preview the cost before you render
POST /v1/timeline-1.0/plan is unbilled. It runs the schema and Sume-host URL checks and the compiler, then returns duration_seconds, segment_count, billable_minutes and estimated_cost_usd_micros. It does not create a job, reserve credits or download media. So you can check whether a 61-second program is really worth two minutes before spending anything. A plan cannot predict short-source pad or loop warnings, so the final render can still carry soft warnings, which the docs say are not failures.
The render accepts an audio.duration_seconds from 1 to 1,800 and up to 200 video slots. At the maximum 1,800 seconds the price is 30 x $0.10 = $3.00.
Worked batch examples
Rounding is per render, so batch totals are easy. 250 renders of 30 seconds: 250 x $0.10 = $25.00. 250 renders of 75 seconds: 250 x 2 x $0.10 = $50.00. 250 renders of 125 seconds: 250 x 3 x $0.10 = $75.00. A single 10-minute explainer (600 seconds) is 10 minutes and $1.00; at 601 seconds it is 11 minutes and $1.10.
The reserve is taken from audio.duration_seconds at submit, so the number you put in that field decides the minutes. The docs say to confirm the live rate in GET /v1/catalog before relying on this table.
Using the rounding in your favor
Plan to land at or just under a minute mark. Short-form platforms already cluster there: a Shorts-style video of 58 seconds and a 120-second explainer cost $0.10 and $0.20. If a cut runs at 62 seconds, either tighten it by 2 seconds for $0.10 or accept $0.20. Across 1,000 videos that choice is $100 against $200.
Timeline is the assembly step of a finished video. Clips, voice-over and music are billed separately, and the Timeline line is usually the smallest of them: for a 30-second ad it is $0.10 beside $3.75 for three 10-second Wan 3.0 clips at 720p. The Timeline 1.0 page has the request schema.
Sources
Related posts
More in Pricing
- Timeline 60 vs 61 seconds: the minute boundary that doubles the bill
Sume Timeline bills $0.10 per ceil(output minute). A 60-second ad costs $0.10; a 61-second ad costs $0.20. Table of boundaries from 30 to 1,800 seconds.
- Timeline bills 61 s as two minutes: the 60 s cut that halves the fee
Sume Timeline charges $0.10 per output minute rounded up, so 60 s costs $0.10 and 61 s costs $0.20. How to plan 30 s shots around it.
- Timeline plan as a spend gate: a 1,800 s render is at most $3.00
Call POST /v1/timeline-1.0/plan before render. It is unbilled and returns estimated_cost_usd_micros. The longest render, 1,800 s, is 30 minutes at $0.10: $3.00.
- Timeline price for a 90 s edit of three 30 s shots: $0.20
A 90-second Timeline render bills 2 minutes, $0.20, because output minutes round up. Add the shots: $11.45 on Wan 3.0 or $52.22 on Seedance 2.5 at 720p.
Written by Sume