One 1080x1920 render against five platform video limits

A default Sume Timeline render is 1080x1920 MP4. Check it against the numeric limits TikTok, YouTube Shorts, LinkedIn, Pinterest and X publish themselves.

6 min readSume
All posts

Yes for the sizes and ratios, with length as the real constraint: a default Sume Timeline render is a 1080x1920 MP4, and that frame shape sits inside the numbers each platform below publishes. What changes per platform is how long the video may run. The table uses only figures from each platform's own page; where a page did not state a number, the cell says so.

Published video limits by platform (read 2026-10-13)
PlatformLengthFile sizeFrame rateOther stated limit
TikTok APIUp to 10 minutes4 GB23 to 60 fps360 to 4096 px; MP4, WebM, MOV
YouTube ShortsUp to 3 minutesNot on that pageNot on that pageMaximum resolution 1080p
LinkedIn3 s to 30 minutes75 KB to 500 MBNot on that pageMP4
Pinterest4 s to 15 minutesUp to 2 GBNot on that pageRatios between 1:2 and 1.91:1; H.264 or H.265
X (default account)Up to 20 minutesUp to 8 GBNot on that pagePremium: 125 minutes, 16 GB

What 1080x1920 means for each row

1080 and 1920 sit inside TikTok's 360 to 4096 px window. YouTube's Shorts page names 1080p as the maximum resolution; it does not say how that is measured for a vertical frame, so confirm 1080x1920 with a test upload. 9:16 is one of the ratios Pinterest suggests. LinkedIn and X pages in this table state no frame-size rule, so there is nothing to check for them beyond length and bytes.

The Sume side is documented in Timeline 1.0: default output 1080x1920, width and height as even integers from 256 to 2160, output.fps of 24, 25, 30 or 60, and an audio spine of 1 to 1800 s.

Where it can still fail

Length is first: a 5-minute render is fine on TikTok and LinkedIn but too long for Shorts. Size is second: the Sume docs do not publish a file size or bitrate for a render, and codec fields are rejected by the API, so you cannot tune bytes with crf. Measure the file after the job, and compare it with the smallest cap you target; LinkedIn's 500 MB is the lowest in this table.

The YouTube row is thin on purpose. The Shorts help page gave a length and a resolution cap but no aspect-ratio or frame-rate statement, so none is claimed here.

Sources

Related posts

More in Comparisons

All Comparisons posts

Written by Sume