Facebook Reels error 1363129: frame rate must be 24 to 60 fps
Error 1363129 means the average frame rate is outside 24-60 fps. Conform the file to a fixed 24, 25, 30 or 60 fps with Sume Video Trim or Timeline, then retry.

Error 1363129 means Facebook read the video's average frame rate as unsupported for Reels. The Reels page says the rate must be 24 to 60 frames per second and fixed. Re-encode the file at 24, 25, 30 or 60 fps and upload again; Sume's Video Trim output.fps and Timeline output.fps both accept exactly those four values.
Facebook facts are from its Reels publishing guide and Sume facts from Video Trim and Timeline 1.0, read 2026-10-01.
What does error 1363129 say?
Facebook reports it for a video whose average frame rate is not supported for this product. The guide's spec table lists 24 to 60 frames per second and Fixed frame rate, so a variable-rate file (common from screen recorders and phones) can fail even when its nominal rate looks fine.
Which Reels video settings does Facebook list?
| Property | Listed value |
|---|---|
| File type | .mp4 (recommended) |
| Aspect ratio | 9 x 16 |
| Frame rate | 24 to 60 frames per second |
| Frame rate mode | Fixed frame rate |
| Duration | 3 to 90 seconds |
| Compression | H.264, H.265 (VP9, AV1 also supported) |
| Chroma subsampling | 4:2:0 |
| Closed GOP | 2-5 seconds |
How do I conform the frame rate with Sume?
There are two routes, depending on whether the file is already on Sume. For a generated clip you want to cut, Video Trim takes an optional output of { width, height, fps }, with fps one of 24, 25, 30 or 60. This works only with precision: "exact", the default frame-accurate re-encode; asking for keyframe with an output is refused as video_trim_output_requires_exact. If you omit output, the file keeps the source rate, so a bad rate is not fixed by accident.
For several clips, Timeline 1.0 has output.fps with the same four values. If you omit it, the output matches the sources, so set it explicitly when a source is off-range. Timeline's default output is 1080x1920 MP4, which matches the Reels recommendation. Both tools accept only media on the Sume media host; import other files first.
Does changing the frame rate cost quality?
The Timeline docs warn that meeting a rate different from a source's is done by repeating or dropping frames, which can show as judder. Pick the rate nearest the source (25 for a 25 fps file, 30 for 29.97) rather than a distant one.
What should I check before retrying the upload?
Confirm the output is 24, 25, 30 or 60 fps and 3 to 90 seconds, then run the upload again from the start session step. See also Reels length limits and Reels ad specs.
Sources
Related posts
More in Developers
- Facebook Page story API: media from an earlier post is rejected
Meta's Stories API says a story's photo or video cannot have been used in a published post. Make the story variant a new file with a Sume job, not the old URL.
- edge_fades_exceed_output: fade in and out too long for the video
Timeline 1.0 refuses fades that are too long: each edge fade is 0 to 5 seconds and fade in plus fade out must not exceed the output length.
- Faded matte-black video look by API: raise the colorlevels black point
Sume's video filter allowlists colorlevels. Raising the output black point (romin, gomin, bomin) lifts pure black to dark gray for a faded, matte look.
- fal content_policy_violation 422 vs Sume generation_rejected
fal returns content_policy_violation as a non-retryable 422. Sume's closest job error category is generation_rejected: inspect events and fix the input.
Written by Sume