LinkedIn video ad sizes for four ratios and the Timeline output to use

LinkedIn's video ad page lists a recommended, minimum and maximum size for four ratios. The sizes that appear on the page are 1920 x 1080 for 16:9, up to 1920 x 1920 for 1:1, 720 x 900 for 4:5 and 720 x 1280 for 9:16. Each is a valid Sume Timeline output, since Timeline accepts even widths and heights from 256 to 2160, and each render is $0.10 for a clip of 60 seconds or less.

Ranges on the LinkedIn page

The table lists what the page says for each ratio. Where a column is blank, the page did not state a value for it in the text read on 2026-10-08.

Pick an output inside each range

Use the recommended size where there is one. For 1:1 the page gives only the bounds, so 1080 x 1080 is a safe choice inside them. All of the numbers below are even integers between 256 and 2160, which is what Timeline accepts.

Two things the sizes do not cover

LinkedIn also asks for video under 30 FPS and a file between 75 KB and 500 MB, with a length from 3 seconds to 30 minutes. Set output.fps to 24 or 25 to stay under 30; Timeline accepts 24, 25, 30 and 60, and omitting it matches the sources, which could be 30 or higher.

The thumbnail has to match the video's aspect ratio and resolution, so render the thumbnail from the same output with video frames rather than from the master. LinkedIn also says ProRes is not supported and that you can upload at most 25 videos per 24 hours, so batch the four renders into one upload session rather than spreading retries across the day. A rejected upload counts as a try, so check each file's size and fps first.

• fps 24 or 25 keeps the file under 30 FPS.
• Four ratios at 60 s or less: 4 x $0.10 = $0.40.
• A thumbnail from video frames matches the output size.

Request

The 4:5 render below sets size and frame rate. Change width, height and the Idempotency-Key for the other ratios. The unbilled /plan call accepts the same body, so you can confirm all four requests compile before any render is charged. Keep the clip at 60 seconds or less per render to stay at $0.10; a 61 second output is billed as two minutes.

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: li-4x5-001" \
  -d '{"audio":{"mode":"silence","duration_seconds":30},"video":[{"source_url":"https://media.sume.com/artifacts/artf_demo/master.mp4","start":0,"duration":30,"fit":"cover"}],"output":{"width":720,"height":900,"fps":25}}'