One 16:9 master for Samsung Ads CTV and Quora video ads, under 50 MB
Both take 16:9 MP4 with H.264 and AAC. The shared envelope: 5 to 60 seconds, 1920x1080, 30 fps, under 50 MB. Build it as a Sume timeline and check the size.

Make one MP4 at 1920x1080, 30 fps, H.264 video and AAC audio, between 5 and 60 seconds long and under 50 MB, and it satisfies both Samsung Ads' CTV video spec and Quora's video ad spec. Render it as a Sume timeline with output width 1920, height 1080 and fps 30, then check the file size before you upload.
The numbers come from Samsung's DSP help page and Quora's ad specs, both read 2026-10-04. The existing posts on Samsung TV specs and Quora specs cover each alone; this one finds the overlap.
Where do the two specs overlap?
Samsung's CTV row is shown. Quora's limits are the stricter ones on frame rate and length, and Samsung's are stricter on file size and minimum length.
| Property | Samsung CTV | Quora | Safe for both |
|---|---|---|---|
| Format | MP4 | MP4 or MOV | MP4 |
| Aspect ratio | 16:9 | 16:9 | 16:9 |
| Resolution | Min 1280x720, recommended 1920x1080 | 640x360 to 1920x1080, recommended 1280x720 | 1920x1080 or 1280x720 |
| Length | 5 to 90 s | 3 to 60 s | 5 to 60 s |
| Frame rate | 30 fps recommended | 30 fps or less | 30 fps |
| File size | 50 MB max, 30 MB recommended | 70 MB or less | Under 50 MB |
| Codecs | H.264, AAC or MP3 | H.264, AAC | H.264 and AAC |
Why does bitrate decide whether 60 seconds fits?
Samsung asks for a bitrate between 5 Mbps and 10 Mbps for CTV. Size is bitrate times length: at 10 Mbps, one second is 1.25 MB, so 60 seconds is about 75 MB, which breaks Samsung's 50 MB cap. At 5 Mbps, 60 seconds is about 37.5 MB and passes. A 30-second spot passes at either end of the range, near 37.5 MB at 10 Mbps.
The rule of thumb: for a 60-second ad, aim for the low end of the bitrate range, and prefer 15 to 30 seconds, which is also what both vendors recommend.
How do I build it in Sume?
Timeline accepts output width and height as even integers from 256 to 2160, fps of 24, 25, 30 or 60, and up to 200 video slots over an audio spine of 1 to 1800 seconds. Set 1920, 1080 and 30. It costs $0.10 per output minute, rounded up, and you send an Idempotency-Key header. Source URLs must be on media.sume.com.
Timeline takes no ffmpeg arguments, so you cannot set the bitrate directly. That is why the size check matters: download the result, read its byte count, and compare it with 50 MB. If it is over, shorten the cut or simplify the footage, since busy motion costs more bits.
How do I check the file before uploading?
Import the finished MP4 and run video-inspect, which returns a probe of the file along with stills and, when requested, a transcript. It needs an Idempotency-Key and a source of at most 1800 seconds. Use the probe to confirm resolution, frame rate and duration against the table, and note that STT billing only applies if you ask for a transcript ($0.01 per audio minute).
Last, remember Quora's note that captions and sound are recommended, not required. Burn captions into the master with video-captions if the ad will often play muted.
Sources
Related posts
More in Use cases
- One 9:16 master for Instagram ads: what two Meta pages say
Meta's Instagram Feed video ad page lists 9:16 at 1080x1920 and 4 GB. Its placement chart shows a narrower Feed range. How to pick a master and check it.
- One video in three languages: per-language voiceover tracks on Sume
Render scene lines in each language with TTS, join each language into one track with timeline audio concat, then re-base scene starts from segments[].
- Online course trailer in 30 seconds with Seedance 2.5: beats and cost
A 30-second course trailer in one Seedance 2.5 request: beats for hook, promise and call to action, authored captions on top, about $17.33 at 720p on Sume.
- Out-of-office video message with an AI avatar: 15 seconds on Sume
Make a 15-second out-of-office video from a script: return date, contact, captions on. $2.76 on Standard plus a $0.20 caption add-on; Plus and Max too.
Written by Sume