LinkedIn video ads max out at 1920 px per edge: set the size

LinkedIn lists a minimum of 360 pixels and a maximum of 1920 pixels for both width and height of video ads. Sume Timeline allows even edges up to 2160, so a render could exceed LinkedIn's maximum; set output width and height explicitly to 1920 x 1080, 1080 x 1920, 1080 x 1080 or 1080 x 1350.

The LinkedIn figures are from its video ad specs page (read 2026-10-10). The Timeline limits are from its docs page.

LinkedIn's size rules

The page lists aspect ratios 4:5, 9:16, 16:9 and 1:1, minimum width and height of 360 pixels, maximum width and height of 1920 pixels, a file size of 75 KB to 500 MB, a duration of 3 seconds to 30 minutes, MP4 files and a recommended 30 frames per second. It also says the sound format is AAC or MPEG4 and lists a sound rate of less than 64 KHz.

Timeline sizes against the window

Timeline's default is 1080 x 1920 and its output width and height are even integers from 256 to 2160. The overlap with LinkedIn's 360 to 1920 window is the range 360 to 1920 per edge, so any size inside that overlap works for both. Sizes outside it fail on one side or the other.

Why the explicit size matters

Leaving output unset gives 1080 x 1920 by default, which fits LinkedIn. The risk comes when you set a larger size for another platform and reuse the request. A 2160 x 2160 request is valid for Timeline and not for LinkedIn. Keep a small table of per-platform sizes in your own code, and pick from it by name instead of copying numbers.

Frame rate is the second setting. If you omit output.fps, the render follows the sources; LinkedIn recommends 30, so setting fps to 30 is straightforward, with the caveat that Sume warns output_fps_resamples_sources when the requested rate differs from the sources and frames are repeated or dropped.

• Set output.width and output.height explicitly.
• Set output.fps to 30 if your sources are 30 fps; otherwise expect a resample warning.
• Check the result duration_seconds against 3 seconds to 30 minutes.

Edge cases

The 75 KB minimum is no problem for real video, and the 500 MB maximum matters for long 1080p renders. Sume cannot tune the bitrate, so measure the file after rendering. Audio sound rate is a codec detail Sume does not expose; if the page's audio rule matters for your account, check a rendered file with your own tooling.

A related trap is odd edges. Timeline requires even integers for width and height, which is why a 16:9 size such as 2160 x 1215 fails, and why you should derive sizes from a short list instead of calculating them on the fly. A table with four or five approved sizes per platform removes the guesswork and makes reviews quick.

If you are rendering one master for several placements, remember that LinkedIn lists four ratios, and the other platforms in this series list different ones. Rendering the 1080 x 1920 vertical and the 1920 x 1080 horizontal as separate Timeline jobs, each with cover fit, is more reliable than trying to make one file serve every placement.

Finally, remember that these checks are cheap compared with a failed upload. A render is $0.10 per output minute rounded up, so a 30-second ad costs $0.10, and re-rendering at the right size is a small cost. The expensive mistake is finding out after you have queued a campaign, so check sizes before you hand the file to anyone.