Facebook Reels error 1363127: resolution below 540x960
Error 1363127 means the Reels video is under the 540 x 960 minimum. Facebook recommends 1080 x 1920; in Sume use the 720p or 1080p tier in 9:16, not 360p.

Error 1363127 means Facebook judged the resolution unsupported for Reels. The minimum is 540 x 960 pixels and 1080 x 1920 is recommended, so a 9:16 video at 360p is too small. Ask Sume for a 720p or 1080p tier in 9:16, or render with Timeline 1.0, whose default output is 1080x1920.
Facebook's numbers come from its Reels publishing guide; Sume's from Video generation, Video Router and Timeline 1.0, read 2026-10-01.
What does the Reels guide say about resolution?
The spec table lists 1080 x 1920 pixels as recommended and 540 x 960 as the minimum, with a 9 x 16 aspect ratio. A processing response in the guide shows the message Resolution too low. Video must have a minimum resolution of 540p. under processing_phase.
Which Sume resolution tiers clear the minimum?
| Source | Value | Against 540 x 960 |
|---|---|---|
| Facebook minimum | 540 x 960 | The floor |
| Facebook recommended | 1080 x 1920 | Recommended |
| Video Router Auto default | 720p, 8s | Tier names 720p; check the output size before upload |
| Gemini Omni Flash 1.1 tiers | 360p, 720p, 1080p, 4K in 16:9 or 9:16 | Skip 360p |
| Timeline 1.0 default | 1080x1920 MP4 | Matches the recommendation |
How do I request 9:16 at a safe size?
Video Router Auto defaults to 720p and 8 seconds. Models list their own aspect ratios; the supported_aspect_ratios field on a model includes 9:16. Where a model exposes a resolution choice, send 720p or 1080p. The 360p tier is only a draft size for this destination.
A tier name is not the same as a pixel count: 720p in 9:16 is about 720 pixels on the short side only if the model defines it that way. Read width and height on the finished job and compare against 540 x 960 before you upload.
Can Timeline fix an undersized clip?
Timeline 1.0 composes to a canvas whose default is 1080x1920 and its output.width and output.height take even integers from 256 to 2160. It can place a smaller clip on a 1080x1920 canvas with fit such as cover, but that scales pixels up and does not add detail. Regenerating at a higher tier is the cleaner fix.
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