LinkedIn video minimums 360x360, 360x450, 360x640: Sume floor is 256
LinkedIn's smallest accepted video sizes are 360 px on the short side. Sume timeline output can go down to 256 px, so set the size yourself and stay above 360.

LinkedIn lists a minimum size for each ratio: 640x360 for 16:9, 360x360 for 1:1, 360x450 for 4:5 and 360x640 for 9:16. Sume lets you set output sizes down to 256 on each side, so Sume will not stop you from rendering a file LinkedIn's page says is too small. Check the size you pass in output against the table below before you render (LinkedIn page and Sume docs, read 2026-10-09).
LinkedIn minimums and maximums
The LinkedIn page gives these ranges for video ads. The maximum column matters as much as the minimum, because the same page caps each ratio.
| Ratio | LinkedIn minimum | LinkedIn maximum | LinkedIn recommended |
|---|---|---|---|
| 16:9 | 640x360 | 1920x1080 | 1920x1080 or 1200x675 |
| 1:1 | 360x360 | 1920x1920 | not listed |
| 4:5 | 360x450 | 1080x1350 | 720x900 |
| 9:16 | 360x640 | 1080x1920 | 720x1280 |
What Sume allows
For both timeline output and trim output, the Timeline 1.0 and Video trim docs give width and height as 256 to 2160, with even values for the timeline. So 320x568 is a legal Sume size and an illegal LinkedIn size. Sume does not know which platform you are targeting; it validates only its own range.
This matters mostly for drafts. A common habit is to render a small 9:16 preview for quick review. A 270x480 preview is fine for review, but it is below the LinkedIn minimum of 360x640, so it is not an upload candidate.
Rendering to a LinkedIn minimum
You rarely want the minimum, but you may want something close for a throwaway test of the upload flow. These are even and legal in both systems: 640x360, 360x360, 360x450 and 360x640. All four are exactly the LinkedIn minimums, and each is above Sume's 256 floor.
You can also lean on the free checks Sume already has. The timeline plan returns duration_seconds, segment_count and billable_minutes without creating a job, which is enough to confirm the length and cost before you spend anything. Only the LinkedIn size window needs your own guard.
A guard to add
The cheap fix is a lookup in your own code. Keep a small table with the minimum and maximum per ratio, and check output.width and output.height before you call the render. An unbilled plan call tells you the document is valid for Sume, but it knows nothing about LinkedIn's limits. For the 3-second length floor on the same page, see the shortest ad lengths post. For a first crop to the right ratio, see centered crop fractions.
Sources
Related posts
More in Media tools
- 3.9-second reply: H3 Max needs 5 s, Fabric bills 4 s ($0.40)
A 3.9 s reply is under H3 Max Lip Sync's 5 s floor on Sume. Fabric bills 4 s: $0.40 at 480p, $0.75 at 720p. Padded to 5 s, H3 Max is $0.3125 at 480p.
- Lip sync still aspect ratio 0.4 to 2.5: which shapes pass
Sume's H3 Max Lip Sync takes a public HTTPS still with aspect ratio 0.4 to 2.5. 9:16 and 21:9 pass; 1:3 and 32:9 do not. Crop numbers inside.
- The longest single Timeline render: 30 minutes, 200 slots, $3.00
Timeline 1.0 allows audio.duration_seconds up to 1800 and 200 video slots per render. At $0.10 per minute the ceiling is 30 x $0.10 = $3.00.
- Luma Ray3.2 reframe costs 6 to 36 cents a second; Sume crop is $0.02
Luma lists reframe at $0.06, $0.12 and $0.36 a second by resolution. Sume's video filter crops a clip for $0.02 a job. What each does and does not change.
Written by Sume