Samsung Ads mobile video, 10 MB recommended: bitrate for 15 and 30 s
Samsung recommends 10 MB for mobile and tablet video, 30 MB for desktop. That caps a 30-second spot near 2.7 Mbps. The math, plus a Sume render and size check.

To hit Samsung's 10 MB recommended size for mobile and tablet video, a 30-second spot can carry about 2.67 Mbps of video and audio combined, and a 15-second spot about 5.33 Mbps. Those are recommendations, not hard limits: the page's maximum file size for all online video is 50 MB.
Samsung's DSP video page (read 2026-10-04) gives the desktop, mobile and tablet row as MP4, 16:9, recommended 1920x1080 with a minimum of 854x480, a maximum length of 120 seconds, 15 to 30 seconds recommended, and 24 to 30 fps. Its file size line reads 50 MB maximum, 30 MB recommended on desktop and 10 MB recommended on mobile and tablet. The page does not state audio loudness.
What bitrate fits 10 MB?
File size equals bitrate times length. Using decimal megabytes, 10 MB is 80 megabits, and dividing by the length gives the average rate. The CTV row has its own bitrate range of 5 to 10 Mbps, so do not apply these mobile figures to CTV files.
| Length | Mbps for 10 MB (mobile) | Mbps for 30 MB (desktop) |
|---|---|---|
| 6 s | 13.3 | 40.0 |
| 15 s | 5.3 | 16.0 |
| 30 s | 2.7 | 8.0 |
| 60 s | 1.3 | 4.0 |
| 120 s | 0.7 | 2.0 |
What does that mean for a Sume render?
Timeline lets you set output size and fps but takes no ffmpeg arguments, so it will not let you dial in a bitrate. What you can control is the content. A 1280x720 render at 30 fps uses far fewer bits than 1920x1080, and static or slow footage compresses better than fast cuts and film grain. For mobile, 854x480 is Samsung's own minimum, and timeline output sizes go down to 256 on even integers.
Render at 1280x720 and 30 fps, and for a 30-second spot expect a comfortable margin under 30 MB. Whether it lands under 10 MB depends on the footage, so measure it instead of guessing.
How do I measure the result?
Download the finished MP4 and read its size in bytes; divide by the duration in seconds and multiply by 8 to get the average bitrate. Then run the file through video-inspect for a probe of resolution, frame rate and duration. It needs a media.sume.com source, an Idempotency-Key and a source no longer than 1800 seconds; stills are optional and capped at 24 per call.
If a file runs over 10 MB, trim it to 15 seconds, drop the output to 854x480, or cut busy scenes. Because the 10 MB figure is a recommendation, going over is a delivery risk, not an automatic rejection, so decide per campaign.
When do I need the CTV numbers instead?
If the same ad also runs on connected TV, use the CTV row: 5 to 90 seconds, 50 MB maximum and 30 MB recommended, bitrate 5 to 10 Mbps. The post on one 16:9 master for Samsung CTV and Quora works through that case, and Samsung TV ad specs lists the whole sheet.
Sources
Related posts
More in Media tools
- Seedance 2.5 secondary edit vs trim-and-regenerate on Sume
BytePlus describes timestamp-level edits to Seedance 2.5 clips. Sume has no such edit field, so here is the trim-and-regenerate route and its limits.
- SeedVR2 10x video upscale vs Sume's upscale tool
SeedVR2 is listed with 1x to 10x video upscaling. Sume exposes a video_upscale_create tool, but its docs name no scale factors, so check the live schema first.
- Skim a 20-minute video: video inspect seek fast vs precise
Use seek fast to sample 24 stills from a long video quickly, up to one keyframe interval early, and seek precise when a timestamp must match. Sume docs, read.
- Split one recording into many audio clips: detach once, then split
Twenty ranges from one talking-head video need one audio detach and one split job, not twenty cuts. Wav or mp3, overlap rules, and what each clip returns.
Written by Sume