Temu detail video up to 180 s: stitch 30 s clips with Timeline
Temu detail video allows up to 180 s and 300 MB at 720p or higher. Sume clips top out at 30 s, so six clips stitched with Timeline cover the full length.

A 180-second detail video is six 30-second Sume clips joined by one Timeline render. A search summary of Temu's partner documentation says the detail video allows up to 180 seconds and 300 MB in 1:1, 4:3 or 16:9 at 720p or higher; confirm on Temu's page.
The arithmetic
seedance-2.5 accepts 4 to 30 seconds and wan-3.0 accepts 2 to 30 seconds. 180 divided by 30 is six clips. If 300 MB means 300 million bytes, 180 seconds at that cap is about 13 Mbit/s on average, so check the rendered file size before upload.
| Limit | Temu | Sume side |
|---|---|---|
| Length | Up to 180 s | 6 clips of up to 30 s |
| Size | 300 MB | Not set by a request field; check the result |
| Ratio | 1:1, 4:3, 16:9 | Choose per clip |
| Resolution | 720p or higher | 720p or 1080p on seedance-2.5 |
Stitching with Timeline
Timeline 1.0 takes an audio spine plus ordered video[] slots. With no voiceover yet, audio.mode: "silence" declares the length. Every URL must be a media.sume.com artifact, and Idempotency-Key is required. Starts must increase, and video[0].start must be 0. Use hard cuts or short fades.
curl -X POST https://api.sume.com/v1/timeline-1.0/render \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: temu-detail-001" \
-d '{
"audio": { "mode": "silence", "duration_seconds": 90 },
"video": [
{ "source_url": "https://media.sume.com/artifacts/artf_demo/c1.mp4", "start": 0, "duration": 30 },
{ "source_url": "https://media.sume.com/artifacts/artf_demo/c2.mp4", "start": 30, "duration": 30 },
{ "source_url": "https://media.sume.com/artifacts/artf_demo/c3.mp4", "start": 60, "duration": 30 }
],
"output": { "width": 1280, "height": 720 }
}'Scaling to 180 s
Extend video[] to six slots and set duration_seconds to 180. Timeline allows up to 1800 seconds and 200 slots. Docs say strategy: "single" with more than 12 slots is unsafe, which six slots avoid. Preflight with POST /v1/timeline-1.0/plan, which is unbilled and returns duration and estimated cost.
Consistency across clips
Separate generations will not match exactly. Give every clip the same product reference images and a similar prompt, and review the cuts before upload.
Sources
Related posts
More in Media tools
- TikTok trending API: browse without a query is flag-gated
Sume trending search needs a query on production. Browse with no query, limit up to 100 and relevance floors are dev-only until a flag is set. The differences.
- Transparent PNG: generate it or cut it out?
Sume lists a background option on ChatGPT Image 2.5: auto, transparent or opaque. Generate a transparent PNG directly, or cut out an existing image.
- Trim the silent lead-in: first spoken word from STT, then video trim
A clip that starts with two seconds of nothing loses viewers. Read the first word's start time from STT, then cut with video trim, exact or keyframe.
- Video analyses: include_transcript false leaves scene audio null
On the legacy Sume video-analyses resource, scene audio is null unless include_transcript was true. Handle both shapes, and know what replaces it for new work.
Written by Sume