Amazon Fire TV feature rotator video specs: 1920x1080, -24 LKFS

Amazon lists the Fire TV feature rotator video at 5–21 seconds, 16:9, 1920x1080, no borders, and loudness of -24 LKFS. What Sume can and cannot set.

4 min readSume
All posts

Amazon's Fire TV feature rotator video runs 5 to 21 seconds (up to 30 for Japan), 16:9 at a minimum of 1920x1080, with video bitrate of 2,000 kbps or higher, up to 500 MB and loudness of -24 LKFS plus or minus 2 dB with a true peak of -2 dB. No letterboxing or borders. Read 2026-09-29.

What does the rotator page list?

Formats are MOV, MP4, MPEG and M4V, with H.264 or ProRes and AAC audio. Amazon also asks for logos only inside the safe zone and no fake UI elements or permanent overlays.

Fire TV feature rotator values on Amazon's page (read 2026-09-29)
ItemValue
Duration5 to 21 seconds (30 for JP)
Ratio and size16:9, 1920x1080 minimum
File sizeUp to 500 MB
Bitrate2,000 kbps or higher
Loudness-24 LKFS +/- 2 dB, true peak -2 dB
LayoutKeep key content inside the safe zone; no borders

How do I generate a clean 1920x1080 clip?

Ask for 16:9 and resolution: "1080p", with a duration from 5 to 21. If you assemble in Timeline, its default output is 1080x1920, so set output.width and height to 1920 and 1080. Amazon says no black borders, so check the video[].fit choice (cover, contain, stretch or blur) on the rendered file.

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: rotator-001" \
  -d '{
    "model": "seedance-2.5",
    "prompt": "A barista pours latte art, close-up, slow push-in",
    "duration": 15,
    "resolution": "1080p",
    "aspect_ratio": "16:9"
  }'

Can Sume normalize loudness?

Sume's docs do not list loudness normalization or true-peak controls. Measure the audio in your own tools and adjust before delivery.

What are the limits of this answer?

Amazon's page says the rules apply to its Fire TV placement and may change; Sume does not submit creative.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume