LinkedIn video ad vs Page video: which numbers differ

LinkedIn Page video and LinkedIn video ads are two different specifications, and a file that passes one can fail the other. Per LinkedIn's own pages (read 2026-10-08): Page video runs 3 seconds to 10 minutes and up to 5 GB, with ratios from 1:2.4 to 2.4:1; video ads run 3 seconds to 30 minutes and 75 KB to 500 MB, with ratios from 9:16 to 16:9.

Side by side

The two pages disagree in both directions. Ads allow a longer video but a much smaller file, and Page video allows wider and taller frames.

Where a file fails

A 21:9 cinematic clip is valid as Page video, because 2.4:1 is wider than 21:9, and invalid as an ad, since 16:9 is the widest ad ratio. A 3-hour webinar fails both. A 700 MB clip of 8 minutes passes as Page video and fails as an ad on size. A 2160-pixel-tall export passes the Page limit of 2304 but exceeds the ad limit of 1920 per side.

The Sume fix for each

For ratio, use video filter with a crop op. Crop values are fractions of the frame: x and y between 0 and 1, width and height between 0.05 and 1, with x + width at most 1. For a 21:9 clip turned into 16:9, the width fraction is (16/9)/(21/9) = 0.762. For length, use video trim, which outputs up to 900 seconds. Filter source clips may be 300 seconds at most and cost $0.02 per encode; a free /check call validates the request first.

For size, shorten or lower the resolution, since Sume has no bitrate field. Probe the result and read size_bytes against 500 MB before you upload as an ad.

{
  "video_url": "https://media.sume.com/artifacts/artf_demo/cinema-21x9.mp4",
  "ops": [
    { "op": "crop", "x": 0.119, "y": 0, "width": 0.762, "height": 1 }
  ]
}

Choosing one export

If a clip must run in both places, build to the narrower of each pair. That means a ratio between 9:16 and 16:9, a size under 500 MB, a frame size within 360 to 1920 pixels per side, and a length of 10 minutes or less if the Page version is to match. A 1080x1920 or 1920x1080 MP4 at 30 fps meets every line in the table.

Do not assume the Page numbers from the ad page or the reverse. LinkedIn publishes them on separate help pages, and the Page troubleshooting article gives a different container story from the specification page, so treat the table as a starting point and open the pages before a launch. Sume's probe returns container, fps, width, height and size_bytes, which is enough to check the file against either column.