Snap ad video size: API says 1080x1920, ad specs page says 720x1280

Snap's Ads API lists 1080x1920 for top snap video while its ad specs page lists 720x1280. Render one 9:16 file at 1080p and check the pixels with Sume.

4 min readSume
All posts

Render 1080x1920 (9:16). Snap's Ads API media page lists 1080x1920 for a top snap video, while the ad specs page for the main formats lists 720x1280. A 1080x1920 file is the same 9:16 shape, so one export covers both numbers.

What each Snap page says

The two pages were read on 2026-10-03. Neither page explains why the numbers differ. The ad specs page covers the main ad formats, and the API page covers media uploaded through the Marketing API.

Snap video specs by source (read 2026-10-03)
SourceSizeLengthFile sizeContainer
Ad specs page (Single Image or Video, Story, Collection, Sponsored Snaps)720x1280, 9:163-180 snot listed hereH.264 for Commercials
Ads API, top snap video1080x19203 s min, 1800 s max32 MB max, 1 GB with chunked uploadMP4 or MOV

Pick the larger frame

If you upload through the API, the stated size is 1080x1920, so that is the safe target. If you upload in the Ads Manager UI, a 1080x1920 file still has the 9:16 ratio the page asks for.

Rendering larger costs file size. The API note gives 32 MB as the single-request ceiling for a top snap video, with chunked upload up to 1 GB, so a 1080x1920 clip of a few seconds will normally upload in one request. Check the byte size of the finished file before you choose the upload path.

Render it with Sume

Sume's video generation API takes resolution and aspect_ratio on POST /v1/videos. Each model advertises the values it accepts in supported_resolutions and supported_aspect_ratios, so list the models first. seedance-2 lists 1080p and 9:16 in the docs example.

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "seedance-2",
    "prompt": "Vertical product clip, hand sets a mug on a wooden desk, soft daylight",
    "resolution": "1080p",
    "aspect_ratio": "9:16",
    "duration": 6
  }'

Verify the pixels before upload

Do not assume the delivered frame matches the request. Import the finished clip as a Sume asset and run video inspect. It returns a probe and stills as frames[{t,url,width,height}], so you can read the width and height of a sampled frame and compare it with 1080x1920.

Keep the check cheap: one inspect per batch template, then spot-check later runs. If the numbers ever differ from what Snap's API page states, trust the API page for API uploads and re-render.

  • Target 1080x1920, 9:16, MP4.
  • Keep the clip between 3 s and the length of the placement you buy.
  • Check size on disk against the 32 MB single-upload ceiling.
  • Re-read both Snap pages before a large batch; specs change.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume