Amazon Sponsored Brands video: Sume fps 24-30 fit; 60 and 4K do not

Pick 24, 25 or 30 fps and 1280 x 720 or 1920 x 1080 when you conform a clip for Amazon Sponsored Brands video with Sume. Amazon's spec page lists frame rates of 23.976, 23.98, 24, 25, 29.97, 29.98 or 30 fps and resolutions of 1280 x 720, 1920 x 1080 or 3840 x 2160 (read 2026-10-03). Sume's video trim accepts fps of 24, 25, 30 or 60 and edges from 256 to 2160, so 60 fps is outside Amazon's list and 3840 x 2160 is outside Sume's range.

The rest of Amazon's list covers codec, bit rate and audio, where Sume has no setting. Here is the full comparison.

Amazon's list against Sume's fields

Amazon asks for H.264 or H.265 video, the Main or Baseline profile, progressive scan, a minimum bit rate of 1 Mbps (4 Mbps or higher recommended), and audio of PCM, AAC or MP3, stereo or mono, at 96 kbps or more and a 44.1 kHz or higher sample rate (read 2026-10-03). Sume's exact trim re-encodes with libx264 and yuv420p and keeps audio as AAC, and the docs name no bit rate or profile controls.

Conform a clip to 1920 x 1080 at 30 fps

Video trim takes output with width, height and fps, only in the default exact precision. Pick 1920 x 1080 and 30 fps, set a duration between 6 and 45 seconds (Amazon recommends 20 or less), and leave audio at its default so the track is kept. The cut costs $0.02 under the current public rate (confirm in GET /v1/catalog).

If your source is 3840 x 2160, the trim can downscale it to 1920 x 1080, which Amazon accepts. If you wanted to deliver at 4K, Sume cannot do that step, and the file has to come from another tool. The script below makes the 1080p version and prints the URL.

import os, time, requests
BASE = "https://api.sume.com"
H = {"Authorization": f"Bearer {os.environ['SUME_API_KEY']}"}

def run(path, body, key):
    r = requests.post(BASE + path, headers={**H, "Idempotency-Key": key}, json=body)
    r.raise_for_status()
    job = r.json()["request_id"]
    while True:
        s = requests.get(f"{BASE}/v1/jobs/{job}/status", headers=H).json()["status"]
        if s in ("completed", "failed", "canceled"):
            break
        time.sleep(3)
    return s, (requests.get(f"{BASE}/v1/jobs/{job}/result", headers=H).json() if s == "completed" else None)

status, res = run("/v1/video-trim", {
    "video_url": "https://media.sume.com/artifacts/artf_demo/brand-film-4k.mp4",
    "start": 0, "duration": 20,
    "output": {"width": 1920, "height": 1080, "fps": 30}}, "sb-1080-001")
print(status, res and res["video_url"], res and res["duration_seconds"])

Why 29.97 and 23.976 are on the list

Amazon's list includes the fractional rates 23.976, 23.98, 29.97 and 29.98 because broadcast and some cameras produce them. Sume's fps field takes whole numbers (24, 25, 30 or 60), so a clip that arrives at 29.97 can be conformed to 30, which Amazon also lists. A tiny change in rate is rarely visible, but it does mean the output is not frame-for-frame the same timing as the source, so keep an unchanged copy for editing.

If you omit output, the trim inherits the source's geometry and rate, so a 29.97 fps source stays at 29.97, which is also on Amazon's list. That can be the simplest path when the source is already 1920 x 1080: only set output when you need to change something, and read the result's output field to confirm what you got.

A short pre-upload checklist

Check the length first: 6 to 45 seconds, with 20 or less recommended. Check the shape next: 16:9 with square pixels, at one of the three resolutions. Check the frame rate against the list, then the file size against 500 MB. Finally, confirm the codec, profile and bit rate with an external probe, since those are the three rows Sume cannot set.

Write the result of each check next to the file name. A reviewer who sees six ticks and one open question about the profile knows exactly where to look, and the spec page's read date tells them how fresh the numbers are.

Check what you cannot set

Amazon's bit rate floor of 1 Mbps is easy to meet for a 1080p clip, but you cannot set it in Sume, so read the file size and divide by the length. A 20-second file of 2.5 MB is about 1 Mbps in total. Video inspect returns probe facts for a hosted clip, and its docs do not list a bit rate field, so use an external probe if you need the exact figure.

The profile row is the other unknown. Amazon names Main or Baseline, and the Sume docs do not say which profile the exact output uses. Upload a test and read the validation message from Amazon before you submit a campaign, and keep the settings that passed.