Paramount ad specs: :15 or :30 spots, 720p minimum, 6 Mbps
Paramount video ads are :15 or :30 spots at 1280x720 or larger, MP4 or MOV, 6 Mbps minimum, with 23.98 to 30 fps. What Sume can render for those.

Paramount video ads are :15 or :30 spots, at least 1280x720 (16:9), MP4 (H.264 High preferred) or MOV (ProRes 422 or 422 HQ). Frame rate is 23.98, 24, 25, 29.97 or 30, bitrate is 6 Mbps minimum, and audio is two-channel AAC at 192 kbps or more, 48 kHz, -24 LUFS plus or minus 2. Specs are from Paramount, read 2026-10-01.
What are Paramount's spec limits?
| Item | Spec |
|---|---|
| Length | :15 or :30 |
| Resolution | 1280x720 minimum, 16:9 |
| Container | MP4 (H.264 High preferred) or MOV (ProRes 422 or 422 HQ) |
| Frame rate | 23.98, 24, 25, 29.97 or 30, constant |
| Scan | Progressive only |
| Bitrate | 6 Mbps minimum, 8-bit minimum, 4:2:2 or 4:2:0 |
| File size | 10 GB max |
| Audio | 2-channel AAC, 192 kbps minimum, 48 kHz |
| Loudness | -24 LUFS plus or minus 2, peaks never above -6 dB |
| Avoid | Leaders, slates, countdowns, black bars |
Which of the frame rates can Sume render?
Timeline's output.fps takes 24, 25, 30 or 60, so 24, 25 and 30 are on Paramount's list. 23.98 and 29.97 are not offered by the output.fps field. Omit fps to render at the rate the sources already run at, and probe the file.
How do I render a 16:9 spot at the right length?
Set 1280x720 or 1920x1080, and audio.duration_seconds to 15 or 30. fit: "cover" fills the frame, which avoids the black bars Paramount asks you to avoid. Timeline 1.0 (POST /v1/timeline-1.0/render) takes output.width and output.height as even integers from 256 to 2160 and output.fps of 24, 25, 30 or 60, or omits fps to match the sources. It needs an Idempotency-Key, accepts only media.sume.com sources, and returns one MP4 at $0.10 per output minute, rounded up. The unbilled POST /v1/timeline-1.0/plan previews the cost first.
curl -X POST https://api.sume.com/v1/timeline-1.0/render \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: paramount-30-001" \
-d '{
"audio": { "mode": "silence", "duration_seconds": 30 },
"output": { "width": 1920, "height": 1080, "fps": 30 },
"video": [
{ "source_url": "https://media.sume.com/artifacts/artf_demo/shot.mp4",
"start": 0, "duration": 30, "fit": "cover" }
]
}'What does Sume not control here?
Bitrate, codec, scan type and loudness. Sume's docs list no bitrate or codec field. The render endpoints refuse codec, crf and filtergraph keys with a 400, so you cannot tune the encode from the request. The docs do not describe loudness normalization. Audio gain is a single audio.gain_db from -60 to 12, so measure LUFS with your own tool, and use Timeline audio only to join audio, not to normalize it.
How do I check the render?
Probe the finished file with Video inspect 1.0. With frames: false it is a probe only, it is unbilled, and it reports width, height, container, fps and duration_seconds. It does not report file size, codec or bitrate, so check those with a local tool before you upload.
Paramount wants a constant rate and no leaders, so scrub the first and last frames yourself.
Sources
Related posts
More in Media tools
- Patreon native video: 720p/1080p, 100 hours a month, 10 min on iOS
Patreon native video uploads at 720p or 1080p, viewers default to 720p, and creators get 100 hours of media a month. Render a 1080p file with Sume.
- Pinterest's "AI modified" label: IPTC metadata and classifiers
Pinterest labels Pins "AI modified" using IPTC metadata plus classifiers and self-reports, and you can challenge it. How to prepare an image with Sume.
- Quora video ad specs: 3 to 60 seconds, 16:9, 70 MB, 30 fps max
Quora video ads run 3 to 60 seconds in 16:9 MP4 or MOV, 70 MB or less, H.264, 30 fps or less, 1280x720 recommended. How to render one with Sume.
- Rumble ads video creative specs: 16:9 or 4:3, H.264 MP4, under 50 MB
Rumble video ad creatives must be 16:9 or 4:3, H.264 MP4 only, and under 50 MB each. How to render a 16:9 or 4:3 MP4 with Sume.
Written by Sume