Meta's 4 GB video cap at Sume's 30-minute render limit: 17.8 Mbps
Meta ad video tops out at 4 GB. A 30-minute Sume Timeline render can average up to 17.8 Mbps and fit; a 15-minute Reels ad allows 35.6 Mbps. Table inside.

The short answer
Meta lists a 4 GB maximum file size for Instagram Feed, Instagram Reels and Facebook Feed video ads, and the longest single file Sume's Timeline 1.0 will render is 1,800 seconds (30 minutes). If 4 GB means 4,000 MB, a 30-minute file fits as long as its average bitrate is under 17.78 Mbps (32,000 megabits divided by 1,800 seconds). Real ad files almost never get near that, so size is rarely the constraint; duration is.
Limits side by side
Meta's three ad-guide pages read 2026-10-09 give different length ranges for the same 4 GB cap. The last column divides 32,000 megabits by the longest length each placement allows, which shows how much bitrate headroom there is at the extreme. Meta's pages do not say whether GB is decimal or binary, so treat the figures as approximate.
| Placement | Length range (Meta) | Max file size | Bitrate that fills 4 GB at the longest length |
|---|---|---|---|
| Instagram Feed | 1 second to 60 minutes | 4 GB | 32,000 Mbit / 3,600 s = 8.89 Mbps |
| Instagram Reels | 0 seconds to 15 minutes | 4 GB | 32,000 Mbit / 900 s = 35.56 Mbps |
| Facebook Feed | 1 second to 241 minutes | 4 GB | 32,000 Mbit / 14,460 s = 2.21 Mbps |
What Sume can render in one file
Timeline 1.0 takes audio.duration_seconds from 1 to 1,800 and 1 to 200 video slots, and renders one MP4 at the public rate of $0.10 per output minute, rounded up (docs read 2026-10-09; the live rate is in the public catalog). The default output is 1080x1920. So a Reels-length ad (15 minutes) is one job, $1.50, while a 30-minute file is $3.00.
At the 1,800-second ceiling the bitrate headroom is 17.78 Mbps, which is far above what a 1080p or 1440p social ad needs. A Reels ad at its 15-minute maximum could average up to 35.56 Mbps before reaching 4 GB. The two placements where the arithmetic bites are the long ones: an Instagram Feed ad near 60 minutes would need to stay under 8.89 Mbps, and Sume cannot render that length as one Timeline job anyway.
What to check on the file you deliver
Sume compiles ffmpeg on the server and rejects client-supplied codec and crf fields, so you do not set a bitrate. Measure the delivered MP4 instead. Meta's pages also list container rules that are independent of size: for Reels, H.264, square pixels, fixed frame rate, progressive scan and stereo AAC at 128 kbps or higher, and Instagram Feed's page says videos should not contain edit lists or special boxes in the container.
- 15-minute Reels cut: one Timeline job, ceil(15) x $0.10 = $1.50.
- 30-minute cut, the Sume maximum: ceil(30) x $0.10 = $3.00, average bitrate under 17.78 Mbps to stay inside 4 GB.
- Anything past 1,800 seconds: the docs describe no single-render path, so plan the file outside Sume.
Sources
Related posts
More in Media tools
- Meta lists Reels ads from 0 seconds; Sume's shortest trim is 0.2
Meta's Reels ad page lists lengths from 0 seconds, Feed from 1. Sume's shortest trim is 0.2 s and shortest Timeline render 1 s; shortest clip per model.
- Kling 3.0 Motion Control API: 7.2 s driver video bills 8 s, $1.26
Sume's Kling 3.0 Motion Control costs $0.1575 per second rounded up from the driving video, 1 to 30 seconds. Fields, orientation, and the cost table.
- A 12-second sting scored from a product still: image_url on Sume music
Sume music takes an optional image_url and no duration field. Put "a 12-second track" in the prompt; the job is a flat $0.125 whatever the image or the length.
- Native 1:1 AI video for a TikTok ad, or 9:16 plus a $0.02 crop?
TikTok's 1:1 ad minimum is 640x640 and Gemini Omni Flash 1.1 renders only 16:9 or 9:16. Generate vertical, crop with video filter for $0.02, at 720p.
Written by Sume