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.

3 min readSume
All posts

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.

Threads video and Sume Timeline limits (Threads per Meta docs; read 2026-10-03)
ItemThreadsSume Timeline 1.0
LengthUp to 5 minutesAudio 1 to 1800 s
File sizeUp to 1 GBProbe the render; no fixed output size is documented
Default outputNot covered1080x1920 MP4
CostNot 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

All Use cases posts

Written by Sume