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.

Meta's Facebook Feed video ad page lists the file type as MP4, MOV or GIF, and Sume's Timeline 1.0, video filter and video trim endpoints each return an MP4. For a Facebook Feed upload, MP4 is therefore the format you can deliver from Sume's editing endpoints.
What does each Sume endpoint return?
The docs describe these outputs; read on 2026-09-30.
| Sume endpoint | Output per docs | Meta accepts? |
|---|---|---|
| Timeline 1.0 render | One MP4 | Yes, MP4 is listed |
| Video filter | A new MP4 | Yes, MP4 is listed |
| Video trim | A new MP4 artifact | Yes, MP4 is listed |
| GIF or MOV | No docs page lists it as an output | Meta lists them; Sume does not produce them here |
Can Sume make a GIF or MOV for Meta?
The Timeline, video filter and video trim pages describe MP4 output only. No docs page lists MOV or GIF output for these endpoints, so a GIF or MOV would come from a tool outside Sume.
What else does Meta list beyond the file type?
The same page lists H.264 compression, square pixels, fixed frame rate, progressive scan and stereo AAC audio at 128kbps or higher, plus a 4GB maximum size. On the Sume side, the video trim docs say an exact trim re-encodes with libx264 and yuv420p and remuxes kept audio as AAC, but give no bitrate. The Timeline docs do not state the codec, and none of the docs state an output file size, so check a finished file against Meta's lines instead of assuming it passes.
Video captions and sound are marked optional but recommended, which matters if you render a silent Timeline.
How do I produce the MP4?
Timeline also sets the size, so a feed render is one call. Video filter has a free check route; on Timeline use the unbilled /plan first.
curl -X POST https://api.sume.com/v1/timeline-1.0/plan \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"audio": { "mode": "silence", "duration_seconds": 10 },
"video": [{
"source_url": "https://media.sume.com/artifacts/artf_demo/product.mp4",
"start": 0,
"duration": 10
}],
"output": { "width": 1440, "height": 1800 }
}'Sources
Related posts
More in Use cases
- 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.
- Google Merchant Center image size: 500x500 minimum, 1500x1500 advised
Google lists at least 500 x 500 pixels for product images and recommends 1500x1500 or above. Sume's gpt-image-2.5 can output 1536x1536, which meets the advice.
- Google Merchant Center 16 MB and 64 megapixel image limits vs Sume
Google lists no image over 64 megapixels and no file over 16 MB. Sume's gpt-image-2.5 caps output at 8,294,400 pixels; file size is not published.
Written by Sume