Which Sume video models clear Instagram's 720-pixel Reel minimum
Instagram lists a 720-pixel minimum for Reels. The Sume catalog shows which video models offer 720p or above, their clip lengths, and which fall short.
Instagram's help page lists a minimum resolution of 720 pixels for Reels. When you generate a clip for one, the resolution setting is the first thing to get right. Sume's video catalog lists the resolutions each model offers, and 480p and 360p options fall short of that minimum.
The requirement is from Reel size & aspect ratios on Instagram (read 2026-10-03). It names 720 pixels without saying which side. The Sume docs do not spell out the pixel size behind each resolution label either, so treat the table as a first filter and probe the file you get back.
What each model offers
The data below is from the Sume videos docs, which describe the limits as non-uniform and send you to GET /v1/catalog for the live values.
| Model | Resolutions | Clip length | Fails the minimum at |
|---|---|---|---|
| seedance-2.5 | 480p, 720p, 1080p | 4 to 30 s | 480p |
| wan-3.0 | 480p, 720p | 2 to 30 s | 480p |
| minimax-h3 | 480p, 768p | 5 to 15 s | 480p |
| minimax-h3-max | 480p, 768p, 1080p | 5 to 15 s | 480p |
| gemini-omni-flash-1.1 | 360p, 720p, 1080p, 4K | 3 to 10 s | 360p |
| h3-max-recast | 768p, 1080p | 5 to 30 s | None listed |
Notes on the table
- The docs say 768p on the MiniMax models is a native, first-class setting and not 720p. 768 is higher than 720, but probe the output to be sure.
- Gemini Omni Flash 1.1 takes 16:9 or 9:16 only, so it suits a vertical Reel directly.
- A 480p draft is useful for testing a prompt, but a file that small would fail the minimum, so regenerate it before publishing.
Ask for the resolution explicitly
A generation request to POST /v1/videos takes model, prompt, duration, resolution and aspect_ratio. Send an Idempotency-Key so a retry is safe. This one asks for a vertical 720p clip, the lowest rung that clears the minimum on the table.
curl -X POST https://api.sume.com/v1/videos \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: reel-720-001" \
-d '{
"model": "seedance-2.5",
"prompt": "A ceramic mug on a wooden desk, steam rising, soft window light",
"duration": 6,
"resolution": "720p",
"aspect_ratio": "9:16"
}'
Draft low, final high
A useful workflow is to test a prompt at the lowest resolution, then regenerate the winner at 720p or above. The catalog lists the resolutions for each model, so check it first and send a value the model accepts.
Sources
Related posts
More in Models
- Why sume/auto never picks H3 Max Recast, and what to send
A person swap needs a source video and photos. Sume's Auto router never routes to Recast, so you name h3-max-recast yourself. Here is the request.
- 1-second AI video API: nothing on Sume goes below 2 seconds
No Sume video model takes duration 1. The floor is 2 seconds on Wan 3.0; the rest start at 3, 4 or 5. How to get a 1-second beat anyway, with trim and cost.
- 11-second AI video API: what works past Omni's 10 s cap
Gemini Omni Flash 1.1 stops at 10 s, so an 11 s clip needs H3, H3 Max, Wan, Kling or Seedance. Which Sume ids accept 11 s and what each bills.
- 13-second AI video API: MiniMax H3 at 768p and other Sume ids
Thirteen seconds fits MiniMax H3 and H3 Max (5-15 s), Wan 3.0, Kling 3 and Seedance. Billed price per resolution for a 13 s clip on Sume.
Written by Sume