10-minute 1080p YouTube video at 8 Mbps is about 629 MB: $1.00 on Sume

At YouTube's 8 Mbps for 1080p plus 384 kbps audio, 600 seconds is 628.8 MB. A 600 second Sume Timeline render at 1920x1080 costs $1.00. The arithmetic.

5 min readSume
All posts

A 10 minute 1080p video at YouTube's recommended 8 Mbps video bitrate plus 384 kbps stereo audio is 628.8 MB: (8 + 0.384) x 600 / 8 = 628.8. On Sume, a 600 second Timeline render at 1920x1080 bills ceil(600 / 60) = 10 minutes at $0.10, which is $1.00. The bitrates come from YouTube's upload encoding page (read 2026-10-08), and the price from the Timeline 1.0 docs.

Working it out

Take the total bitrate in megabits per second and multiply by the seconds, then divide by 8. Decimal megabytes are used throughout, so 1 GB is 1,000 MB.

Size at 8 Mbps video plus 384 kbps audio (computed from figures read 2026-10-08)
LengthMegabitsMegabytesGigabytes
5 min (300 s)2,515.2314.40.31
10 min (600 s)5,030.4628.80.63
20 min (1,200 s)10,060.81,257.61.26
30 min (1,800 s)15,091.21,886.41.89

What Sume bills

The Timeline price is per ceil output minute and does not depend on size or bitrate. The docs set audio.duration_seconds from 1 to 1800, so 30 minutes is the longest single render, and the table's last row is the largest file one Timeline job can produce at those rates.

Sume Timeline cost by length (computed from $0.10 per ceil minute)
LengthBilled minutesCost
5 min5$0.50
10 min10$1.00
20 min20$2.00
30 min30$3.00

Two caveats

First, 8 Mbps is YouTube's recommendation for a standard frame rate SDR upload, and the page lists a higher figure for higher frame rates that is not used here. Second, Sume does not accept a bitrate: the docs refuse codec and crf fields because the server compiles ffmpeg, so the sizes above are planning figures. Read the byte count of the finished file. Run POST /v1/timeline-1.0/plan before you render; it is unbilled and returns billable_minutes. For the Short-length version of this math, see the 3 minute post, and for sizes above 1080p, see the 4K post.

The 720p comparison

For the same 600 seconds at YouTube's 720p rate of 5 Mbps plus audio, the total is 5.384 Mbps, so 5.384 x 600 / 8 = 403.8 MB. That is 225 MB less than the 1080p figure. Render 1280x720 with output.width 1280 and output.height 720; the price stays at $1.00.

These are planning numbers built from YouTube's recommended rates, not a measurement of any file. The upload size matters for your connection and for any file cap you meet on the way, so read the byte count of the real render.

Using the number

Use 628.8 MB as the size to expect for a 10 minute 1080p upload if your encoder follows YouTube's recommendation. If the real file is much larger or smaller, the encoder used a different bitrate, and the table above shows the length at which that difference starts to matter for your connection.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume