X video minimum 0.5 seconds: keep Sume trim cuts at 0.5 s or more

X video must be at least 0.5 seconds, while Sume's video-trim accepts cuts as short as 0.2 seconds. So Sume can hand you a clip that X will refuse: for X, set duration to 0.5 or more.

X numbers are from its media best-practices page and Sume numbers from the Video trim docs, read 2026-10-01.

What are the two limits side by side?

The X page states the floor for Post video (categories tweet_video and amplify_video) as 0.5 seconds, with a 20-minute default maximum and 125 minutes for Premium or verified accounts. Sume's trim docs give its own bounds.

How do I keep a trim at or above 0.5 seconds?

Pass start and exactly one of end or duration. The duration field is the length of the cut in seconds, 0.2 to 900. Pick 0.5 or higher in your own code, because nothing in the trim docs knows about X's floor. If you send both end and duration, or neither, you get video_trim_range_conflict or video_trim_range_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: x-short-cut-001" \
  -d '{
    "video_url": "https://media.sume.com/artifacts/artf_demo/talk.mp4",
    "start": 2,
    "duration": 0.5
  }'

What happens for a cut under 0.2 seconds?

The docs state the floor as output of at least 0.2 seconds but do not name a separate refusal code for it; the documented video_trim_range_empty covers end at or before start, or a range longer than 900 s. Validate the length on your side before you submit, and check the returned duration_seconds on the result against X's 0.5 second minimum.

Does the same floor apply elsewhere?

No. Other platforms set their own floors; see Instagram Reels' 3-second minimum for a longer one. Treat each destination's number as its own check.