Liftoff video creative specs: 1080x1920, 300 MB, 180 s

Liftoff lists portrait video at 1080x1920 up to 300 MB and 180 s, landscape at 1920x1080, plus a 1 MB end card image. How to cut both with Sume.

5 min readSume
All posts

Liftoff's creative guidelines list portrait video at 9:16 and 1080 by 1920, MP4 or MOV, up to 300 MB and 180 seconds, and landscape video at 16:9 and 1920 by 1080. Sume's Timeline 1.0 renders 1080 by 1920 by default and can render 1920 by 1080 when you set the output size, so one project can feed both.

Liftoff's table

Liftoff's page gives no maximum file size or duration for landscape and no audio requirements, so do not assume the portrait limits carry over. It also lists a portrait end card image at 1080 by 1920 in PNG, JPG or GIF with a 1 MB cap.

Liftoff video and end card specs, read 2026-10-03
AssetAspect and sizeFormatsLimits
Portrait video9:16, 1080x1920MP4, MOV300 MB, 180 s
Landscape video16:9, 1920x1080MP4, MOVNot specified
Portrait end card image1080x1920PNG, JPG, GIF1 MB

One cut, two orientations

Timeline video clips carry a fit of cover, contain, stretch or blur. For a landscape source going into a portrait frame, blur fills the bars with a blurred copy and cover crops to fill. Pick by looking at the still: a product on a table survives cover less often than a face does.

Output width and height accept 256 to 2160 and fps accepts 24, 25, 30 or 60, so both of Liftoff's sizes are inside the range. The price is $0.10 per ceil output minute, so a 30 second portrait render and a 30 second landscape render are $0.20 together.

Limits to plan for

Sume's timeline audio spine runs 1 to 1800 seconds, so the 180 second portrait ceiling is inside what a timeline can hold.

Sume does not give you a size field, so check the exported file against 300 MB. The end card is a still: make it with the Images API at a 9:16 aspect and check the PNG against the 1 MB cap yourself, because the Images docs publish aspect_ratio per model, not file weight.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume