X video ad: 2:20 at 6,000 kbps is 105 MB, so the 1 GB cap never binds
X allows 1 GB and 2 minutes 20 seconds. At its recommended bitrate the length limit hits first. The math, plus the 9:55 case for approved advertisers.
For a standard X video ad the 2:20 length limit binds long before the 1 GB size limit. At X's recommended 1080p bitrate of 6,000k, 140 seconds is about 105 MB, roughly a tenth of the cap. Only a bitrate near 57 megabits per second would fill 1 GB in 140 seconds. If your upload is rejected, check length first.
The two limits side by side
X's creative specs page lists a 1 GB maximum file size and says up to 2:20 is supported, with 15 seconds or less recommended. It adds that select advertisers can request an increase up to 10 minutes, and advises 9:55 to leave room for variation between video files. Ask your X account manager for that increase; Sume cannot grant it.
| Case | Duration | Bitrate | Size |
|---|---|---|---|
| Standard max length, 1080p recommended | 140 s | 6,000 kbps | 105 MB |
| Standard max length, 1080p ceiling | 140 s | 10,000 kbps | 175 MB |
| Increased length, 1080p recommended | 595 s (9:55) | 6,000 kbps | 446 MB |
| Increased length, 1080p ceiling | 595 s (9:55) | 10,000 kbps | 744 MB |
| Bitrate that fills 1 GB in 140 s | 140 s | about 57,143 kbps | 1,000 MB |
How the numbers are derived
Size in megabytes is kilobits per second times seconds, divided by 8,000. For 6,000 kbps over 140 seconds: 6,000 times 140 is 840,000 kilobits, divided by 8,000 is 105 MB. For 595 seconds at 10,000 kbps: 5,950,000 divided by 8 is 743,750 kB, about 744 MB, which is still under 1 GB. So even the approved long case fits at the top of the 1080p bitrate range.
The practical reading: if X refuses a file, compare the length to 2:20 first, then the container (MP4 or MOV only), then the codec guidance (H264 Baseline, Main or High profile with 4:2:0 color, AAC LC audio). Size is the last suspect.
Cutting a longer master to 2:20 on Sume
Say you have a 4-minute product film. Video trim cuts one range into a new MP4: send start 0 and duration 140. Trim takes a duration from 0.2 to 900 seconds, and the source can be up to 1,800 seconds. The default exact precision re-encodes frame-accurately, so the cut lands on the second you asked for. Keyframe precision copies the stream and can start up to a GOP early, which could push you over 140 seconds if you place the cut tight.
If you need to join pieces instead, a timeline render takes one audio spine plus up to 200 video slots. It bills $0.10 per output minute rounded up, so a 140-second render bills 3 minutes, $0.30. A trim is $0.02 for the same 140 seconds (Sume catalog, read 2026-10-08).
Looping and the 60-second line
X says videos loop if they are under 60 seconds. A 140-second ad plays once and stops, so end on a frame that works as a final card. A 45-second ad replays, so the last frame should hand over cleanly to the first.
Sources
Related posts
More in Use cases
- X video ad under 30 MB: how many seconds fit at 6,000 and 5,000 kbps
X says keep video ads under 30 MB. At its 6,000 kbps (1080p) and 5,000 kbps (720p) targets that is 40 and 48 seconds. Check yours with Sume video inspect.
- X video ads loop under 60 seconds: design the last frame of a 45 s ad
X loops video ads shorter than 60 seconds and plays longer ones once. Plan the first and last second differently for each, then check them with Sume.
- YouTube AI label: player if photoreal, description if animated
YouTube shows the AI label in the player for photorealistic content and in the expanded description for animated content. Which Sume clips fall where.
- YouTube can add an AI label you cannot remove: C2PA 2.1 and Sume jobs
YouTube auto-labels files with Content Credentials 2.1+ and can add a label creators cannot remove. What to record per Sume job, and what the docs do not claim.
Written by Sume