Facebook Reels API video length: 3 to 90 seconds, 24 to 60 fps
Meta's Reels publishing docs list 3–90 seconds, 9x16, 1080x1920 recommended, 24–60 fps, closed GOP and 48 kHz AAC. How Sume durations line up.

To publish a Reel on a Facebook Page through the Video API, the video must run 3 to 90 seconds, be 9x16, and run at 24 to 60 frames per second. Meta recommends 1080x1920 and lists 540x960 as the minimum.
Sume can reach that length range by joining clips in Timeline 1.0 at 24, 25, 30 or 60 fps; codec details are outside what Sume exposes. Values are from Meta's page as read on 2026-09-29.
What does the Reels publishing guide require?
The page recommends .mp4 and accepts H.264 or H.265 (VP9 and AV1 also listed), 4:2:0 chroma, a closed GOP of 2 to 5 seconds, and stereo AAC-LC audio at 128 kbps or higher, 48 kHz.
| Item | Value |
|---|---|
| Container | .mp4 recommended |
| Codec | H.264 / H.265 (VP9, AV1 also supported) |
| Ratio | 9x16 |
| Resolution | 1080x1920 recommended, 540x960 minimum |
| Duration | 3 to 90 seconds |
| Frame rate | 24 to 60 fps |
| Audio | AAC-LC stereo, 48 kHz, 128 kbps or higher |
Which Sume tools reach 90 seconds?
A single generation is short: seedance-2.5 lists 4 to 30 seconds and wan-3.0 lists 2 to 30. Most other models cap at 15 or less. For a 90-second Reel, build it from several clips: Timeline 1.0 takes an audio spine of 1 to 1800 seconds and 1 to 200 video[] slots.
Set output.width 1080, height 1920 and fps 30 (or 24, 25, 60) to stay in Meta's range.
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: fb-reel-90s-001" \
-d '{
"audio": {
"url": "https://media.sume.com/artifacts/artf_demo/voice.wav",
"duration_seconds": 24
},
"video": [
{ "source_url": "https://media.sume.com/artifacts/artf_demo/a.mp4", "start": 0, "duration": 12 },
{ "source_url": "https://media.sume.com/artifacts/artf_demo/b.mp4", "start": 12, "duration": 12 }
],
"output": { "width": 1080, "height": 1920, "fps": 30 }
}'What about the closed GOP and AAC rules?
Sume's docs do not list GOP length, chroma format or audio sample-rate controls, and callers cannot set codec, bitrate or CRF on Timeline. Render, then probe the result with POST /v1/video-inspect and compare with the table before you publish.
What are the limits of this answer?
This post covers the Facebook Page Reels API page only. Instagram has its own limits (3 s to 15 min); see the linked Instagram post.
Sources
Related posts
More in Use cases
- Financial advisor video marketing with AI, compliance first
Financial advisor video marketing with AI: short explainers from an avatar, scripts approved before rendering, exact on-screen text, and per-second costs.
- Floor plan to video AI: animate a plan, and what to check
Floor plan to video AI means image-to-video: the plan is the first frame and the prompt sets the camera. The clip is an illustration, not a survey.
- Gemini editing in YouTube Shorts: how does it work?
YouTube says you prompt a first draft, then refine by reordering, trimming pauses and syncing music. Here is which of those steps map to separate API calls.
- Gemini Omni in YouTube Create: countries, length and limits
Gemini Omni in YouTube Create makes vertical clips up to 10 seconds on mobile in five countries. Google's limits, and how to get a 9:16 clip from Sume instead.
Written by Sume