Threads 5 minutes and 1 GB: one render for feed and Threads
Threads video can run up to 5 minutes and 1 GB. Render one vertical master with Timeline 1.0, at $0.10 per output minute, and probe it before you post.

Threads accepts video up to 5 minutes and up to 1 GB, per Meta's Threads documentation. A five-minute vertical master is well inside what Sume's Timeline 1.0 can render (up to 1800 seconds), and at $0.10 per output minute it costs $0.50 to assemble; whether the same file is right for another feed depends on that feed's own limits, which I did not check.
Limits side by side
The Timeline rate is from Sume's docs, which also say to confirm it live in the catalog.
| Item | Threads | Sume Timeline 1.0 |
|---|---|---|
| Length | Up to 5 minutes | Audio 1 to 1800 s |
| File size | Up to 1 GB | Probe the render; no fixed output size is documented |
| Default output | Not covered | 1080x1920 MP4 |
| Cost | Not applicable | $0.10 per ceil output minute |
Make one master
Build the master as a vertical MP4 at the default 1080 by 1920, with a single audio spine of the final length. A plan call tells you duration, segment count and estimated cost before any billing. Render needs an Idempotency-Key, and the sources must be your media.sume.com files. Models cap individual clips (some at 30 s), so a five-minute video is a chain of slots on the spine.
curl -X POST https://api.sume.com/v1/timeline-1.0/plan \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"audio": { "url": "https://media.sume.com/artifacts/artf_demo/vo.wav", "duration_seconds": 300 },
"video": [
{ "source_url": "https://media.sume.com/artifacts/artf_demo/part1.mp4", "start": 0, "duration": 150 },
{ "source_url": "https://media.sume.com/artifacts/artf_demo/part2.mp4", "start": 150, "duration": 150, "transition": { "type": "fade", "duration": 0.25 } }
]
}'Probe before you post
Run video inspect with frames set to false to read duration and size without stills. Compare the duration with 300 seconds and the file size with 1 GB. Because the 5 minute figure is the platform's ceiling, aim a little under it to leave room for rounding; a 5:01 file fails where 4:58 passes.
- Keep the same master for other feeds only after you read their current limits.
- If a feed wants a different ratio, re-render with a different output width and height instead of cropping by hand.
- Read the live Threads page for codec, frame-rate and bitrate limits.
Sources
Related posts
More in Use cases
- TikTok Shop Good-tier listings: five images over 600x600, batched
TikTok Shop's listing quality tiers ask for five or more images above 600x600 and a clean main image. How to batch that set on Sume. Read 2026-10-03.
- TikTok Shop LIVE: stills may cover only half the screen
TikTok Shop seller guidance caps stills and slideshows at 50% of the screen during a LIVE. Plan overlay layouts with motion clips from Sume instead of stills.
- TikTok Shop main image: no digital renderings, and the real-model shot
TikTok Shop's listing guidance excludes digital renderings from the main image and asks for a real human model image. What that means for AI product shots.
- Turn a drawing into an image with GPT Image 2.5
Wikipedia says GPT Image 2.5 added Sketch, which turns drawings into images. Sume exposes GPT Image 2.5 with image references; here is how to send a drawing.
Written by Sume