Threads podcast video highlight: cut the clip with video trim
Threads now lets podcasters share highlights as video posts. Cut one standout moment from a long episode into a new MP4 with Sume video trim at $0.02 per job.

Meta's Threads podcast toolkit lets you broadcast highlights as transcript, video and guest card posts. To make the video post from a full episode file, cut the standout moment with Sume POST /v1/video-trim: it returns a new MP4 holding only [start, end), at $0.02 per job.
Threads details are from Meta's announcement; trim details from Video trim, read 2026-10-01.
Where does the highlight video come from?
Meta's announcement says under "Broadcast the highlights" that you can share standout moments with video posts, and gives no length or format rules for them in that text. Check the Threads composer for limits; Threads video upload limits covers that separately. Your job is the cut itself: pick a start time from the episode and a length.
How do I cut the highlight?
Send the source, an in-point start in seconds, and exactly one of end or duration. The source must already be a media.sume.com clip: there is no open-internet fetch, so import first with POST /v1/media-imports. An Idempotency-Key is required.
curl -X POST https://api.sume.com/v1/video-trim \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: threads-highlight-001" \
-d '{
"video_url": "https://media.sume.com/artifacts/artf_demo/episode.mp4",
"start": 1325.5,
"duration": 45
}'What are the limits?
| Item | Value |
|---|---|
duration | 0.2 to 900 seconds |
| Source length | Up to 1800 seconds |
| Price | $0.02 per job; confirm live in GET /v1/catalog |
Default mode | async; poll GET /v1/jobs/:id/status and /result |
What if the source is longer than 1800 seconds?
It fails with source_duration_exceeded. A very long episode needs to be split before import. The result's video_url is a new artifact, never the source, and actual_start_seconds tells you where a keyframe-mode cut really began; with the default exact precision the cut is a frame-accurate re-encode.
Sources
Related posts
More in Use cases
- TikTok Ad Network asset specs: banner 640x100 and where Sume stops
TikTok Ad Network wants video at 1280x720, 720x1280 or 720x720 and banners at 600x500, 640x200 or 640x100. What Sume renders natively and what needs a crop.
- TikTok carousel ad specs: 2-35 images and three sizes
A standard TikTok carousel takes 2 to 35 JPG or PNG images at 1200x628, 640x640 or 720x1280. Here is how to map those onto Sume image settings.
- TikTok carousel ad music: mp3 required, silent on Ad Network
TikTok carousel ads need an .mp3 of 2 s or more, up to 10M. Library music is silent on Ad Network placements, so upload your own file there.
- TikTok Global App Bundle image ad sizes: 9:16, 16:9, 1:1
TikTok's Global App Bundle image ads need 9:16 at 720x1280 or more, 16:9 at 1280x720 or more, or 1:1 at 640x640 or more, as JPG or PNG within 100 MB.
Written by Sume