MiniMax H3 4-second clips: MiniMax says 4, Sume says 5
MiniMax lists 4–15 seconds for H3, but Sume's docs and pricing code start at 5 seconds. Send 5 or more, and trim to 4 afterwards if you need it.

Can MiniMax H3 make a 4-second clip? MiniMax's own page lists 4–15 seconds, but on Sume minimax-h3 accepts 5–15 seconds, so 4 is below its range. Request 5 seconds and cut the clip to 4 afterwards with Sume's video trim.
The MiniMax figure is from its open-source announcement, read 2026-09-29. Sume's range is from Video generation and its pricing code. The two disagree, so a request built from MiniMax's table alone can miss Sume's range.
What are the two ranges?
| Source | Output duration |
|---|---|
| MiniMax's open-source announcement (H3) | 4–15 seconds |
Sume docs, minimax-h3 | 5–15 seconds |
Sume docs, minimax-h3-max | 5–15 seconds |
What is the default length on Sume?
In Sume's pricing code the minimum is 5 seconds, the maximum 15 and the default 5. A request with no duration is priced as a 5-second clip. Send duration as a whole number of seconds from 5 to 15.
How do I get a 4-second clip?
Generate 5 seconds, wait for the job to complete, then cut. Sume's video trim takes one Sume-hosted clip, such as the output of an earlier Sume job, plus start and exactly one of end or duration, and returns a new MP4 holding [start, end). Trimming does not change the source. It needs an Idempotency-Key, so give each trim its own key, and it answers with a job you poll like any other.
curl -X POST https://api.sume.com/v1/video-trim \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: h3-trim-4s-001" \
-d '{
"video_url": "https://media.sume.com/artifacts/artf_demo/h3-clip.mp4",
"start": 0,
"duration": 4
}'Why not just ask for 4 seconds?
A 4 is outside the range Sume documents for the model, and this post does not promise how a request outside it is handled. Send a value inside the documented range. If you send both end and duration to trim, that is a range conflict; see Video trim range conflict.
Do I pay for the extra second?
Sume's pricing code has a per-output-second rate table for minimax-h3, and the request is for 5 seconds, so expect the generation to be priced as 5 seconds even if you keep 4 of them. This post does not cover what the trim job itself costs. MiniMax H3 pricing per second has the rates by resolution.
Which Sume video models start below 5 seconds?
If a native 4-second clip matters more than the model, Sume's docs list lower minimums elsewhere: seedance-2.5 accepts 4–30 seconds, wan-3.0 accepts 2–30 seconds and gemini-omni-flash-1.1 accepts 3–10 seconds. Read supported_durations for the exact set before you pick, because the models differ in inputs and sound, not only length.
How do I check the range before I submit?
Call GET /v1/videos/models and read supported_durations for the id. It lists the whole seconds the model accepts, so it answers the question for whatever the catalog says on the day you call.
Sources
Related posts
More in Developers
- MiniMax H3 aspect ratios: 21:9 to 9:16, and when adaptive works
MiniMax H3 makes six aspect ratios, from 21:9 to 9:16. Which ones Sume accepts, where adaptive is allowed, and how frame images set the ratio.
- MiniMax H3 in ComfyUI or through a hosted API: what differs
ComfyUI documents three MiniMax H3 workflows with local model files; a hosted API returns a job. The limits that change between the two, from the docs.
- First and last frame to video with MiniMax H3: request and rules
MiniMax H3 fills the motion between an opening and a closing image. On Sume send frame_images with first_frame and last_frame; ratio, length and price rules.
- Multi-shot AI video prompts: MiniMax H3 shot labels and timecodes
MiniMax H3 models multiple shots natively. Write [Shot 1] labels or timecoded blocks in the prompt; syntax from the vendor guides and a Sume request.
Written by Sume