A 62-second Short bills two Timeline minutes: $0.20 vs $0.10 at 60 s

Timeline render is $0.10 per started minute: 60 s renders for $0.10, 62 s for $0.20, and 180 s (the Shorts limit) for $0.30. Read 2026-10-08.

5 min readSume
All posts

A voiceover that runs 62 seconds renders as two billed Timeline minutes ($0.20), while one trimmed to 60 seconds renders as one ($0.10). Sume bills Timeline render at $0.10 per output minute, rounded up, with a one-minute minimum, so the cost steps at every 60-second boundary. YouTube Shorts can now run up to three minutes, so the boundaries at 60, 120 and 180 seconds are the ones to watch.

Billing steps for common durations

The reserve is ceil(audio.duration_seconds / 60) minutes, per the Timeline docs, and audio.duration_seconds accepts 1 to 1,800. The table applies ceil and $0.10 to eight durations around the boundaries.

Timeline render cost by output length, read 2026-10-08
Output secondsBilled minutesRender cost
591$0.10
601$0.10
612$0.20
622$0.20
1202$0.20
1213$0.30
1793$0.30
1803$0.30

What YouTube says about Short length

YouTube's help page states that Shorts can be up to three minutes, that videos uploaded on or after October 15, 2024 with a square or vertical aspect ratio up to three minutes are categorized as Shorts, and that a Short over one minute with an active copyright claim is blocked. So a 62-second Short has two reasons to be 60: it renders for half the price, and it is below the one-minute line where a claim blocks a Short globally.

A 180-second Short is the longest allowed and renders at $0.30; a 181-second video would cost $0.40 and would not be a Short. The voiceover has to fit before the render, so measure the audio length before you commit to a script.

Cutting two seconds

If a read comes out at 62 seconds, you can trim two seconds of silence or tighten the script rather than pay for a second minute. Timeline audio.source_in picks an in-point on a single audio file and audio.gain_db adjusts level, and the output length is whatever audio.duration_seconds you set, so shortening the declared length to 60 saves $0.10 if the content fits. The TTS side is unaffected: a 1,000-character script is $0.0475 whether it runs 58 or 62 seconds.

A budget for a weekly series

For a channel that posts 5 Shorts a week, the difference between a 59-second and a 62-second format is five times $0.10 a week, or $26 over 52 weeks ($0.50 x 52). The saving is small per video and real per year, but it is only worth chasing if the content survives the trim. A 3-minute Short is a different format: 180 seconds renders as 3 minutes for $0.30, so a 5-a-week series is $1.50 a week for renders.

Remember the render bills the output you declare, not the voiceover alone. If the voiceover is 58 seconds and the video is padded to 62 for an end card, the declared audio.duration_seconds of 62 is what sets the two billed minutes.

A practical rule follows: when a cut lands within a few seconds over a minute boundary, decide whether the extra seconds earn the extra $0.10. At 62 seconds you pay for 120 seconds of render, so 58 seconds of that capacity go unused, which is 48.3 percent of the billed time. Trimming 2 seconds returns that fraction to zero waste at the boundary.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume