TikTok API accepts MP4, WebM or MOV: which format Sume returns
TikTok's media guide lists MP4 (recommended), WebM and MOV. Sume video trim and timeline write an MP4, so a Sume result already matches the recommended type.

Sume's trim and timeline jobs return an MP4, and TikTok's media transfer guide lists "MP4 (recommended), WebM, MOV" as supported formats, so no conversion step is needed for the container. The guide text quoted here lists no codec, so this post makes no codec claim about TikTok.
What does each side say?
Only formats and one size are compared, because those are the numbers both pages give.
| Item | TikTok | Sume |
|---|---|---|
| Container | MP4 (recommended), WebM, MOV | MP4 from trim and timeline |
| Maximum size | 4GB | No size stated |
| Video encode | Not quoted | libx264 in yuv420p (trim exact) |
Which Sume jobs write an MP4?
Video trim returns "a new MP4 artifact", and Timeline 1.0 returns "one MP4". Trim's exact precision re-encodes with libx264 in yuv420p and remuxes kept audio as AAC. With keyframe it copies the stream instead, so the codec stays whatever the source used.
What if my generated clip is not an MP4?
Run it through Timeline 1.0 or an exact trim, which write MP4. A video-inspect probe (free with frames: false) shows what a file contains before you decide.
curl -X POST https://api.sume.com/v1/video-trim \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: to-mp4-001" \
-d '{
"video_url": "https://media.sume.com/artifacts/artf_demo/source.mp4",
"start": 0,
"duration": 30,
"precision": "exact"
}'What should I still check?
Read the result's duration_seconds and check the length against the creator's allowed maximum on TikTok. Also check the size against the 4GB maximum on the file itself, since Sume states none. Sume does not post to TikTok; the upload call is yours.
Should I use keyframe or exact precision?
Use exact when the source's codec is unknown or unusual, because the output is then a known H.264 MP4 in yuv420p. Use keyframe only when you accept that the cut may start a GOP early and that the stream is copied unchanged. The result reports actual_start_seconds so you can see where a keyframe cut really began.
For joining clips, Timeline 1.0 takes an audio spine of 1 to 1800 seconds and up to 200 video slots and writes one MP4, priced at $0.10 per output minute.
exact: frame-accurate re-encode,libx264,yuv420p.keyframe: stream copy, cut may start a GOP early.- Both write a new MP4 artifact and leave the source alone.
- Neither takes
codec,crforpreset; those are refused.
Sources
Related posts
More in Use cases
- TikTok upload chunk size: 5-64 MB and 1000 chunks for AI video
TikTok's media guide sets 5 MB to 64 MB chunks, 1 to 1000 chunks and a 4GB maximum. Sume gives no file size control, so measure the MP4 before you split it.
- TikTok title 2200 UTF-16 runes vs burned-in captions from Sume
TikTok's Direct Post title allows 2200 UTF-16 runes. Burned-in captions are separate video pixels: Sume's video-captions job burns the exact cues text you pass.
- TikTok video_cover_timestamp_ms: pick the cover frame in seconds
TikTok's Direct Post field video_cover_timestamp_ms takes milliseconds. Preview candidate frames with Sume video-frames, then multiply the chosen time by 1000.
- AI-made captions on YouTube: is a disclosure label required?
YouTube lists caption creation among edits that need no altered-content disclosure. What that covers, and how a Sume burned-in caption job fits.
Written by Sume