LinkedIn landscape video ad maxes at 1920x1080; Sume allows up to 2160

LinkedIn's video ad page sets the landscape range at 640 by 360 pixels minimum and 1920 by 1080 maximum, so a 4K export is out of range. Sume's timeline render takes output sizes from 256 to 2160 on each side, which means it will happily render something LinkedIn does not accept. Set 1920 by 1080 explicitly and verify the result.

LinkedIn's size table

The LinkedIn Help page lists recommended and range sizes for four ratios. The recommended sizes are the ones to render; the range is what the platform will take.

Where Sume's limits sit

Per Sume's timeline docs, output.width and output.height are even integers from 256 to 2160, and the default output is 1080 by 1920. That default is the exact maximum for LinkedIn's 9:16 row, so a default render passes at the top of the range. A landscape render needs the output block: width 1920, height 1080.

Two Sume sizes are traps. A 2160 by 3840 vertical is not possible (2160 is the cap per side), but a 2160 by 2160 square would pass Sume and fail LinkedIn's 1920 by 1920 maximum. And 2560 by 1440 landscape passes Sume and fails LinkedIn. Neither is a sensible choice for a feed ad, but a template that scales to 2160 can produce them by accident.

Verifying

After the render, call video inspect on video_url with frames set to false. The probe has width and height as integers, plus rotation. If rotation is not zero, the displayed size is swapped, so read both. Compare to the table above before you upload.

Remember the other LinkedIn rows on the same page: MP4 only, H.264 or VP8, frame rate under 30 FPS (so choose 24 or 25 on Sume, since output.fps accepts 24, 25, 30 or 60 and 30 is not under 30), and 3 seconds to 30 minutes. A timeline render costs $0.10 per output minute rounded up (Sume catalog, read 2026-10-08).

A pre-upload checklist

Put the checks in the order that fails fastest. Width and height first, because a wrong size means a re-render. Then duration and size_bytes against LinkedIn's 3 seconds to 30 minutes and 75 KB to 500 MB. Then codec and container, which should read h264 and an MP4 family container. Last, the frame rate.

If you generate several ratios from one master, run the same probe on every output and compare against its own row of the table, not against one global rule. A 1080 by 1350 vertical file is correct for 4:5 and one pixel taller than the 9:16 maximum width allows nothing; each ratio has its own ceiling.

Re-probe after every render. A file that passes the width and height check can still fail on duration or size, and a probe is cheap compared with a rejected upload and a second round of review.