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.

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.
| Length | Megabits | Megabytes | Gigabytes |
|---|---|---|---|
| 5 min (300 s) | 2,515.2 | 314.4 | 0.31 |
| 10 min (600 s) | 5,030.4 | 628.8 | 0.63 |
| 20 min (1,200 s) | 10,060.8 | 1,257.6 | 1.26 |
| 30 min (1,800 s) | 15,091.2 | 1,886.4 | 1.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.
| Length | Billed minutes | Cost |
|---|---|---|
| 5 min | 5 | $0.50 |
| 10 min | 10 | $1.00 |
| 20 min | 20 | $2.00 |
| 30 min | 30 | $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
- A 10-minute TikTok ad from 120 five-second slots: 600 s, $1.00
Timeline takes up to 200 slots and 1,800 s. 120 slots of 5 s make exactly 600 s, which meets TikTok's 10-minute ad limit and bills 10 minutes, $1.00.
- 100 Omni clips on Sume Pro: queue_full after 24 jobs
Sume Pro runs 4 jobs at once and accepts 24 in total. Submitting 100 Omni clips at once returns 429 queue_full. A Python wave loop that retries safely.
- Re-render 100 Sora prompts at 8s 720p 9:16: six Sume models priced
A 100-prompt library of 8-second 720p vertical clips costs $60.00 to $242.00 on Sume depending on the model. Exact per-clip cents and the arithmetic.
- A 12s 1080p clip from two 6s Omni clips: 236 cents with the join
Gemini Omni Flash 1.1 stops at 10 seconds, so a 12-second 1080p shot is two 6-second clips at 113 cents each plus a Timeline join: 236 cents on Sume.
Written by Sume