LinkedIn 1200x675 video ad: Sume needs even sizes, so use 1280x720

You cannot render exactly 1200x675 with Sume. LinkedIn's video ad page lists 1200x675 as one of two recommended 16:9 sizes, but Sume's timeline accepts only even integers for output width and height, and 675 is odd. Render 1280x720 instead. It is also 16:9 and sits inside LinkedIn's stated range of 640x360 to 1920x1080 (LinkedIn page and Sume Timeline docs, read 2026-10-09).

What LinkedIn lists for horizontal video

For 16:9, the LinkedIn page gives a minimum of 640x360, a maximum of 1920x1080, and two recommended sizes: 1920x1080 or 1200x675. Both recommended sizes are exactly 16:9. 1200 divided by 16 is 75, and 75 times 9 is 675, so the ratio is exact; only the height is odd.

Why Sume refuses odd sizes

The Timeline 1.0 docs list output.width and output.height as even integers between 256 and 2160. The same docs say callers never send codec or filtergraph fields; Sume compiles the encode itself. Even dimensions are the usual constraint for 4:2:0 H.264 output, and Sume's video filter docs say the compiler rounds crop results to even values for yuv420p for the same reason. A request with an odd height will not render, so pick a size before you submit.

Pick 1280x720 or 1920x1080

Both are listed or inside the range, and both are exact 16:9. 1920x1080 matches the other recommended size and is the page's maximum, so it is the safest if your source is HD. 1280x720 is the smaller option and keeps the file lighter. You do not need to chase 1200x675: LinkedIn lists it as a recommendation, not a requirement, and the page's hard limits are the minimum and maximum above.

A timeline render costs $0.10 per output minute, rounded up, so a 30-second ad is one billable minute whether it is 1280x720 or 1920x1080 (Sume Timeline docs, read 2026-10-09). The size choice does not change the price.

Check frame rate in the same pass

The LinkedIn page also says frame rate must be less than 30 FPS. Sume's output.fps takes 24, 25, 30 or 60, so set 24 or 25 in the same request if your sources run at 30. If you omit fps, the render follows the source rate. See the under-30 fps post for that rule. For clips that are not 16:9, the centered-crop fractions post shows how to cut to another LinkedIn ratio first.

What to send

Import your clip and audio first, because Sume reads only media.sume.com URLs from your workspace. Then call the unbilled plan endpoint to confirm the document, and render. In the body set output.width to 1280 and output.height to 720, add output.fps of 25, and keep video[].fit at cover (the default) if the source is already 16:9.