Threads video aspect ratio runs 0.01:1 to 10:1: Sume Timeline sizes
Meta's Threads page allows ratios from 0.01:1 to 10:1 with 9:16 recommended and 1920 px max width. Sizes that Sume Timeline can output inside those bounds.

Almost any shape works for Threads, and 1080x1920 is the safe pick. Meta's Threads API page lists aspect ratio "0.01:1 to 10:1" with 9:16 recommended, a maximum horizontal resolution of 1920 pixels, and 23 to 60 frames per second. Sume's Timeline renders 1080x1920 by default, which is 9:16 and under 1920 on its width. Choose other sizes only if the creative needs them.
Sizes that satisfy both sides
Each Sume size uses even integers inside Timeline's 256 to 2160 range.
| Output (w x h) | Ratio | Inside Threads limits? |
|---|---|---|
| 1080x1920 | 9:16 | Yes; recommended ratio, width 1080 |
| 1920x1080 | 16:9 | Yes; width exactly 1920 |
| 1080x1080 | 1:1 | Yes |
| 1080x1350 | 4:5 | Yes |
| 2160x1080 | 2:1 | No; width 2160 is above 1920 |
Steps
- Leave
outputunset for 1080x1920, or set width and height explicitly. - Set
output.fpsto 24, 25, 30 or 60. All four are inside the 23 to 60 range. - Use
fit: "cover"when the source already has the right shape,containwhen you must keep the whole frame, andblurwhen you want the leftover space filled. - Run the unbilled
POST /v1/timeline-1.0/planfirst. - Keep duration at 300 seconds or less.
Wide Timeline outputs above 1920 pixels are legal in Sume and not on Threads, so the Sume range is not the Threads range.
Picking a size for a feed post
Because Threads accepts such a wide range of ratios, the choice is a creative one. A 1080x1920 vertical gives the most screen height on a phone and matches Meta's stated recommendation of 9:16. A 1080x1080 square suits a product shot that must also work in a grid. A 1080x1350 4:5 sits between them.
Whichever you pick, keep the width at 1920 or less. Sume allows up to 2160 on either side, so it will happily render a wider file than Threads accepts. The unbilled plan call does not check against Threads, so the limit is yours to hold.
If the same video will go to other places, render the vertical first, then use the crop filter for the square and 4:5 versions, at $0.02 each.
Budget and detail
The 0.01:1 to 10:1 range on Meta's page is very wide, and it is a rule about what the API accepts, not advice about what looks good. A 10:1 strip would be 1920 by 192 pixels, which is legal on the Threads page but tiny on a phone. Pair the rule with a look at the result on a real device, and stay with the shapes people expect unless the creative needs something else. Sume's own limits sit inside the range: the smallest output side is 256, and the biggest is 2160.
What Sume does not do
Sume does not check the output against Threads' ratio rule. It also does not offer a letterbox-with-your-color mode; the four fit modes are cover, contain, stretch and blur.
Sources
Related posts
More in Developers
- TikTok 500 MB cap and 10 minutes: the bitrate that fits is 6.67 Mbps
TikTok's non-Spark in-feed ad page allows 10 minutes and 500 MB or less. A full 10 minute ad fits only at 6.67 Mbps or below. The arithmetic and a Sume render.
- TikTok 516 kbps minimum bitrate: a 30 second ad is at least 1.94 MB
TikTok's non-Spark spec lists bitrate of 516 kbps or more. The smallest file for 15, 30 and 60 seconds is shown with the math, plus how to check a Sume render.
- TikTok ad caption rules: no links, @ or hashtags, and a 4-line limit
TikTok's in-feed ad page says captions can't hold links, @ symbols or hashtags, and Spark captions max out at 4 lines. A Python lint to run before you submit.
- Timeline sizes for TikTok's three ad ratios: 540x960, 960x540, 640x640
TikTok's non-Spark minimums are 540x960 (9:16), 960x540 (16:9) and 640x640 (1:1). All three fit Timeline's even 256 to 2160 px output range at $0.10 a minute.
Written by Sume