Meta feed video ads start at 1 second; so does Sume Timeline

Meta's Facebook feed and Instagram feed video pages both list a minimum of 1 second. Sume's Timeline 1.0 accepts audio.duration_seconds from 1 to 1800, so a 1-second render is allowed, and it bills one output minute, $0.10, because the rate is per rounded-up minute.

The limits side by side

How a 1-second render works

In the Timeline docs, audio.duration_seconds is the output length. You can set audio.mode to silence to declare a length with no audio file. A video slot's duration must be at least 0.2 seconds, and coverage can stop at most 0.5 seconds before the end of the spine. The reserve is ceil(duration / 60) minutes, so one second reserves one minute.

Models start higher. The video generation docs show Seedance 2.5 accepting 4 to 30 seconds, so a 1-second clip comes from cutting a longer one, with the slot's duration field and a source_in offset.

Is a 1-second ad worth making

The page says it is allowed. It does not say it performs. A 1-second video is a logo hit or a motion tease, and any caption would be on screen for a blink, so plan for a single image or word. If you need the full message, aim for the length of the sentence you want to say.

What Sume does not do

Sume does not check your file against Meta's pages, and it does not guarantee a platform accepts a 1-second render. Upload the file in Ads Manager and read any rejection message before changing the render.

If you are making many short variants, the arithmetic is simple: each one-minute-or-less render is $0.10, so twenty variants are $2.00 before any model generation. The plan endpoint returns billable minutes without creating a job, so you can confirm that figure on a draft first.