Facebook Feed is 4:5, Instagram Feed 9:16: render both for $0.20

Meta lists two different shapes for feed video: 4:5 at 1440 x 1800 for Facebook Feed and 9:16 at 1080 x 1920 for Instagram Feed. One master cannot be both, so render two files. On Sume that is two Timeline renders at $0.10 each for a clip of 60 seconds or less, $0.20 in total.

The two Meta pages side by side

The numbers come from the two Meta ads guide pages, read on 2026-10-08. Several of them differ, including the longest allowed video, so a file that is legal on one feed can be refused on the other.

Render both from one master

Timeline 1.0 takes output.width and output.height as even integers from 256 to 2160, so both sizes are accepted. Each slot has a fit setting: cover crops to fill the frame, contain letterboxes, blur fills the sides with a blurred copy, stretch distorts. Pick cover for most ads and check the crop.

The request below makes the 4:5 file. For the 9:16 file send the same body with width 1080, height 1920 and a new Idempotency-Key.

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-feed-4x5-001" \
  -d '{"audio":{"mode":"silence","duration_seconds":30},"video":[{"source_url":"https://media.sume.com/artifacts/artf_demo/master.mp4","start":0,"duration":30,"fit":"cover"}],"output":{"width":1440,"height":1800}}'

Check the crop and the tolerance

Instagram's page gives a 1% aspect tolerance, so a 1080 x 1920 output is well inside it. A source that is not 9:16 and is stretched to fit would not be, which is why cover or blur is the better choice than stretch.

After each render, pull a frame from the first second with video frames and look at where the subject sits. A 16:9 master cropped to 9:16 keeps only about a third of the width, so a subject near either edge is lost.

• Cost for 30 seconds each: 2 x $0.10 = $0.20.
• At 61 seconds each the price doubles to 2 x $0.20 = $0.40.
• The free /plan call checks the request before you pay.

What Sume does not decide

Which placement your campaign uses, and whether Meta crops a given file on a surface not covered here, is decided in Meta's ad tools. Sume produces the files. Reread both Meta pages before a launch, because they were read on 2026-10-08 and can change. Keep the two outputs under separate Idempotency-Keys, for example fb-feed-4x5 and ig-feed-9x16, so a retry returns the right job. If your campaign also runs in Stories or Reels, those specs are not covered here: the Meta pages for them could not be fetched on the read date, so this post makes no claim about them.