Prime Video ad specs: Amazon's streaming TV video rules

Amazon's Prime Video ad specs call for a 16:9 video of at least 1920x1080 with a video bitrate of at least 15 Mbps, a constant 23.976 (recommended), 24, 25, or 29.97 fps, and AAC audio of at least 192 kbps at 44.1 or 48 kHz on at least two channels, in a file of up to 500 MB. In the US, Prime Video ads run 15, 30, 45, or 60 seconds. A Sume Timeline 1.0 render can set the size, a 24 or 25 fps rate, and the exact length, but not the bitrate, so check every file before submitting it.

Amazon's figures are quoted from its Streaming TV & Prime Video ad specs page, read on 2026-09-27; Amazon can change them. Sume facts come from the Timeline 1.0 and Video inspect docs, the Sume API reference, and Sume's media compiler as it works today. For ads on Amazon's own pages, see Amazon Sponsored Brands video specs.

What are Amazon's Prime Video ad specs?

Streaming TV ads are full-screen, non-skippable video ads that play before, during, or after TV shows, movies, and live entertainment on Prime Video, Twitch, Fire TV Channels, and third-party TV publishers. The bitrate floor and the lengths differ by supply source.

How long can a Prime Video ad be?

Prime Video takes fixed lengths, listed per country. For other lengths, Amazon says to contact your Amazon Ads representative.

• US and Canada: 15, 30, 45, or 60 seconds.
• UK, Germany, Austria, France, Italy, Spain, Brazil, and India: 10, 15, 20, 30, 40, or 60 seconds.
• Mexico and Australia: 15, 20, 30, 40, or 60 seconds.
• Japan: 15 or 30 seconds.

How do I make a Prime Video ad with Sume?

Generate 16:9 shots, then conform them in one POST /v1/timeline-1.0/render. It reads only your workspace's media.sume.com files, such as earlier Sume outputs, needs an Idempotency-Key, and writes MP4, its only output container. How to assemble a long-form video covers the rest of the request.

• output: width 1920 and height 1080 (even integers from 256 to 2160).
• output.fps: 24 or 25. Timeline renders at 24, 25, 30, or 60 fps, with no 23.976 or 29.97 option; omitted, the rate follows your clips (30 for stills only), and Amazon doesn't list 30. A rate that differs from a clip's is met by repeating or dropping a frame every few frames, which can judder on motion. Today the compiler hands FFmpeg that rate as one fixed output rate, which FFmpeg's docs say it holds constant.
• audio.duration_seconds: 15, 30, 45, or 60. The output always runs exactly that long.
• fit: keep the default cover, which today fills the frame and crops the overflow; contain pads with black bars.

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: prime-video-30s-001" \
  -d '{
    "audio": {
      "url": "https://media.sume.com/artifacts/artf_demo/voiceover.wav",
      "duration_seconds": 30
    },
    "video": [
      { "source_url": "https://media.sume.com/artifacts/artf_demo/shot-1.mp4", "start": 0, "duration": 15 },
      { "source_url": "https://media.sume.com/artifacts/artf_demo/shot-2.mp4", "start": 15, "duration": 15 }
    ],
    "output": { "width": 1920, "height": 1080, "fps": 24 }
  }'

Can a Sume render meet the 15 Mbps bitrate floor?

Not on request. Today Timeline encodes H.264 with libx264 in CRF mode, which FFmpeg's docs call constant quality mode. The bitrate follows the footage, and Timeline refuses crf, codec, and other encoder keys with a 400. So measure each render:

• Run POST /v1/video-inspect with frames: false on the render's video_url. That probe is unbilled and reports size_bytes and duration_seconds.
• Average bitrate is size_bytes × 8 ÷ duration_seconds, audio included. A 30-second render smaller than about 57 MB can't hold 15 Mbps of video plus 192 kbps of audio.
• If it falls short, re-encode it at 15 Mbps or more in your own encoder before you submit it. How to check a video's bitrate covers the measurement.

Does the audio meet Amazon's minimums?

The codec does, and the bitrate sits right at the line: today Timeline encodes AAC at 192 kbps, exactly Amazon's minimum. The sample rate and channel count are not settings. The Sume API reference says the master inherits both from the audio spine file, and the probe reports them as audio_sample_rate and audio_channels.

• Sample rate: use a spine at 44,100 or 48,000 Hz. TTS 1.0 output_format.sample_rate accepts both, and its default mp3 is 44,100 Hz.
• Channels: a mono voiceover spine gives a mono master, under Amazon's two-channel minimum. Timeline has no channel setting, and audio detach can only keep the source's channels or downmix to mono, so check audio_channels and fix a mono master in your own editor before you submit it.

What else does Amazon ask of the creative?

• No click prompts in non-interactive ads, which run in non-clickable environments: leave out elements such as a button shape that says “learn more”.
• Keep important visuals inside Action Safe, the area Amazon's downloadable safe-zone image marks as safe from overscan.
• Avoid pillarbox and letterbox bars, which Amazon strongly discourages; they can conflict with interactive ad overlays.