Reels ad: use an existing post or upload a new video? Sume 9:16 file
Meta's Reels ads page offers native video, image ads and existing Reels posts. Which route fits an AI video from Sume, and what file to prepare for each.

Meta's Reels ads page lists three ways to bring an asset: upload a native video, use an image ad, or run an existing Reels post with "Use existing post". For an AI video made on Sume, upload the final 9:16 file as a native video if it is new, and use the existing post route only after the organic Reel is already live with the right label.
The options are from Meta's Reels ads page, read on 2026-10-07. Meta recommends 9:16 vertical for this placement.
The three routes
This table keeps to what the Meta page states, plus what Sume can supply.
| Route | Meta page says | From Sume |
|---|---|---|
| Native video | Upload a video made for Reels; 9:16 recommended | A 9:16 file from a video job, with sound if the model lists it |
| Image ad | Advantage+ Creative can add music automatically | A still from an image model, or a video if you want motion |
| Existing post | Use an existing Reels post as the ad via "Use existing post" | Post the Sume file organically first, then pick the post |
Make the file
Check which models make 9:16 before you spend credits. GET /v1/videos/models returns supported_aspect_ratios, and the video guide states that Gemini Omni Flash 1.1 takes 16:9 or 9:16 with native audio, 3 to 10 seconds, and that Seedance 2 lists 9:16 among its ratios for 4 to 15 seconds.
Meta's page says Reels default to sound on, so use a model with audio or add a track. Then probe the result with video inspect and read probe.has_audio and the dimensions before you upload.
Pick the route
Use these rules of thumb; they are ours, not Meta's.
- New AI video, paid only: native video upload. You control the exact file and the AI disclosure at upload.
- Video that already earned organic attention: existing post, so the ad keeps the post's social proof. Set the AI label on the organic post first.
- Only a product still: an image ad, and let Meta's music option do the audio, or turn the still into a video first. See the image-to-9:16 post.
Where Sume stops
Sume makes and checks the file. The docs we read do not describe posting to Meta Ads Manager, so the upload or post selection is a step in Meta's tools. Store the media.sume.com URL as the media inputs guide advises. For safe-zone and sound rules see the Reels ads brief, and for pixel limits see Facebook Reels ads specs.
Sources
Related posts
More in Integrations
- Video generation MCP connector: six questions before you connect
Before you let an agent spend money through any MCP connector, ask six questions. Here are Sume's hosted MCP answers on auth, scopes, idempotency and spend.
- Voiceover plus a Lyria bed for a reel in one agent session over MCP
Ask an MCP client to run tts_create and music_create on Sume, then check the take with stt_create. Which tool does which job, and where the agent must wait.
- VS Code 1.141 shows discovered MCP servers: where is the Sume entry?
VS Code 1.141 (Oct 7, 2026) lists MCP servers found outside your mcp.json in the Customizations editor. Check there for Sume's URL and the credential it uses.
- Zed 1.23.2 optional MCP fields fix: read Sume's tools_schema anyway
Zed 1.23.2 fixed OpenAI model calls to MCP servers that treated optional fields as required. For Sume, tools_schema shows which fields are required.
Written by Sume