Facebook Feed video ad 4:5 at 1440x1800: render it with Timeline
Meta's Facebook Feed video spec lists 4:5 at 1440 x 1800. No Sume video model lists 4:5, but a Timeline 1.0 render can output 1440x1800. Steps and limits.

Meta's Facebook Feed video ad page lists a 4:5 aspect ratio at 1440 x 1800 pixels. No Sume video model lists 4:5, so generate at 9:16 or another listed ratio and render the final file with Timeline 1.0, whose output accepts a width of 1440 and a height of 1800.
What does Meta's Facebook Feed page list?
The page read on 2026-09-30 gives these values for Awareness video ads in Facebook Feed.
| Item | Meta lists | Sume Timeline |
|---|---|---|
| Aspect ratio | 4:5 | Any output size, both sides even, 256 to 2160 |
| Resolution | 1440 x 1800 pixels | 1440 and 1800 are both inside that range |
| Duration | 1 second to 241 minutes | Audio spine 1 to 1800 seconds |
| Minimum size | 120 x 120 pixels | Output side minimum is 256 |
Which Sume video model gives 4:5?
None does. The video generation docs list aspect ratios such as 16:9, 9:16, 1:1, 3:4 and 4:3, and each model advertises its own subset in supported_aspect_ratios. Read that field from GET /v1/videos/models before you pin a ratio.
So the 4:5 file is a Timeline output, not a generation setting.
How do I render 1440x1800?
Timeline 1.0 only takes URLs that are already this workspace's media.sume.com artifacts or assets, so a completed Sume generation can go straight in, and a file from anywhere else must be imported first (POST /v1/media-imports; the Timeline docs do not show its request body). output.width and output.height must be even integers from 256 to 2160, and fit chooses cover (crop to fill), contain, stretch or blur. audio.mode of silence declares a length with no audio file; use audio.url for a music or voice file instead.
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: feed-45-001" \
-d '{
"audio": { "mode": "silence", "duration_seconds": 15 },
"video": [{
"source_url": "https://media.sume.com/artifacts/artf_demo/product.mp4",
"start": 0,
"duration": 15,
"fit": "cover"
}],
"output": { "width": 1440, "height": 1800 }
}'What should I check before I upload?
Run POST /v1/timeline-1.0/plan first; it is unbilled and returns duration_seconds and billable_minutes. Render is priced at $0.10 per output minute, rounded up (confirm live in GET /v1/catalog).
A silent render carries no audio, and Meta marks video sound as optional but recommended, so add a spine if the placement needs sound. Meta also lists H.264 and stereo AAC settings; the Timeline docs do not state the codec of the output, so verify the finished file against Meta's page. Pages change, so re-read before delivery.
Sources
Related posts
More in Use cases
- Facebook Feed video captions: burn them onto a clip with no speech
Meta marks captions optional but recommended for Facebook Feed video ads. Sume's caption job fails on a silent clip unless you pass your own cues.
- Facebook Feed video ad file type: MP4, MOV or GIF from Sume?
Meta lists MP4, MOV or GIF for Facebook Feed video ads. Sume Timeline, video-filter and video-trim each return an MP4, so MP4 is the format to plan around.
- Flow Music edits a song by section: how to do it by API
Google Flow Music edits songs by section; its Lyria API page says multi-prompt editing is unsupported. On Sume, cut two takes and join the parts you keep.
- Google Merchant apparel images worn by people: reference-guided images
Google asks for apparel product images worn by people. gpt-image-2.5 on Sume takes up to 16 reference images, so a garment photo can guide the image.
Written by Sume