Price a Reel or Short before you render it with Timeline plan
Sume's Timeline plan call returns billable minutes and an estimated cost for free. See what 59, 90 and 180 seconds cost against the 3-minute limits.

Both Instagram Reels and YouTube Shorts now run to three minutes, and a render bills by the started minute, so length is the cost lever. Sume's Timeline has an unbilled plan call that returns the billable minutes and an estimated cost for a program before you submit it. Run it first and you know what a 90-second Reel will cost.
The three-minute limits are from YouTube Shorts (read 2026-10-03) and Record a reel on Instagram (read 2026-10-03). The second page adds that Reels over 3 minutes will not be recommended to new audiences, so 180 seconds is also a reach ceiling, not only a length limit.
What a plan returns
Per the Timeline docs, POST /v1/timeline-1.0/plan returns duration_seconds, segment_count, billable_minutes, estimated_cost_usd_micros and a filtergraph_summary. It creates no job, reserves no credits and downloads no media, and it needs no Idempotency-Key. The public rate is $0.10 per ceil of the output minute.
curl -X POST https://api.sume.com/v1/timeline-1.0/plan \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"audio": { "mode": "silence", "duration_seconds": 90 },
"video": [{
"source_url": "https://media.sume.com/artifacts/artf_demo/clip.mp4",
"start": 0,
"duration": 90
}]
}'
Where the minute boundaries fall
The ceiling rounds up, so one extra second can add a full minute.
| Output length | Billable minutes | Cost | Within 3-minute limit |
|---|---|---|---|
| 59 s | 1 | $0.10 | Yes |
| 60 s | 1 | $0.10 | Yes |
| 61 s | 2 | $0.20 | Yes |
| 90 s | 2 | $0.20 | Yes |
| 180 s | 3 | $0.30 | Yes, at the limit |
| 181 s | 4 | $0.40 | No |
What the plan cannot see
The docs say a plan cannot predict warnings about short sources being padded or looped, so it checks the shape and cost of the program, not the quality of the result. It also costs nothing, so there is no reason to skip it in a script that renders in volume. Fail the script if billable_minutes is higher than you budgeted.
Use it as a budget gate
In a script, call plan for every program, compare billable_minutes with what you budgeted, and refuse to render when it is higher. The check costs nothing, and it catches the common mistake of a voice-over that runs two seconds past a minute boundary. Trimming the script by two seconds saves a whole minute of billing.
Sources
Related posts
More in Pricing
- Re-record one voiceover line: TTS cost for 50 to 5,000 characters
Fixing one 120-character line costs $0.0057 in Sume TTS, 12% of redoing a 1,000-character script at $0.0475. Gluing it in is free inside a Timeline render.
- Realtor's monthly market update: 4 neighborhoods, 45-second avatar
Four 45-second avatar updates a month cost $33.12 on Standard, $44.10 on Plus and $99.00 on Max on Sume, plus a one-time $0.95 for the avatar.
- Real-time AI avatar pricing: live minutes vs one render
Live avatars bill by conversation minute and concurrent stream; a rendered clip is paid once and watched by anyone. Tavus plan numbers and the break-even.
- Recast with four people costs the same as one: photos are free
h3-max-recast bills source seconds only; fal includes reference images at no charge. A 10-second clip is $3.75 at 768p on Sume with one photo or four.
Written by Sume