One 1920x1080, 24 fps, 20 s master for Amazon, LinkedIn and Threads

One 1920x1080, 24 fps, 20-second MP4 sits inside the listed rules of Amazon Sponsored Brands video, LinkedIn video ads and the Threads API, based on each vendor page I read on 2026-10-08. Amazon is the tightest on shape (16:9 only) and LinkedIn is the tightest on frame rate (under 30 fps), so those two choose the settings. In Sume, set Timeline output to 1920x1080 and fps to 24, and render 20 seconds.

The overlap

Each column is that vendor's stated limit; the last column is the master.

Steps

• Import the footage to Sume.
• Render with Timeline: output: {"width": 1920, "height": 1080, "fps": 24}, audio.duration_seconds: 20, and fit: "cover" or blur for each slot.
• Run the unbilled plan call first, then render for $0.10, the public rate per ceil output minute.
• Check codec and file size on the download. Amazon lists H.264 or H.265, LinkedIn lists H.264 or VP8, and Threads lists H.264 or HEVC. H.264 is on all three lists.
• Upload through each platform's own tool.

The master does not cover captions. LinkedIn's page asks for a text-only SRT for captions, so that is a separate file. Amazon and Threads pages as I read them do not mention caption files.

Where the overlap breaks

The overlap works because these three placements allow landscape. It breaks the moment you add a placement that expects vertical, and the pages I did not manage to fetch are not part of this table. Amazon's 16:9-only rule is also strict about pixel shape: it says square pixel, so avoid anamorphic sources.

It also breaks on length if you stretch past Amazon's 45 seconds. Within 6 to 45 seconds, the 20-second recommendation from Amazon and the 15 to 30 second recommendation from LinkedIn point at the same range, so 20 seconds is a fair middle.

For the render, a 20-second timeline bills one output minute. If you also need a captioned version for LinkedIn as an SRT, that is a separate step with video_inspect, because Amazon's page lists no caption file and Sume burns captions into the pixels.

What Sume does not do

Sume does not document the Timeline output codec, so you must confirm H.264 yourself. It does not upload to any of these platforms or check ad review rules. The vertical formats, which suit many holiday placements, need a second render.