Amazon lists 3840x2160, but Sume output tops out at 2160: what to do
Amazon Sponsored Brands video allows 3840x2160. Sume Timeline sides cap at 2160, so a 4K UHD frame is out. Here is the 1920x1080 route and what you give up.
You cannot make a 3840x2160 Amazon Sponsored Brands video with Sume's Timeline or trim output, because both document a limit of 256 to 2160 on each side. Amazon's page lists three resolutions: 1280x720, 1920x1080 and 3840x2160. Two of the three are reachable, so render 1920x1080 and treat it as the production setting. Amazon's own page does not say the 4K option is better for delivery; it just lists it.
Which resolution fits which tool
The limits below are what each page states, nothing measured.
| Amazon option | Reachable with Timeline output | Reachable with trim output |
|---|---|---|
| 1280x720 | Yes, width 1280 and height 720 | Yes |
| 1920x1080 | Yes, width 1920 and height 1080 | Yes |
| 3840x2160 | No, width 3840 is above 2160 | No, width 3840 is above 2160 |
Steps
- Set the output to 1920x1080 in Timeline, which is a legal pair of even integers inside 256 to 2160.
- Use
fit: "cover"if the source is 16:9, orblurif it is not. - Run
POST /v1/timeline-1.0/planfirst. It is unbilled and returnsbillable_minutesandestimated_cost_usd_micros. - Render, then read the result URL. A 30-second video bills as one output minute, which at $0.10 is ten cents per the docs.
- If a reviewer insists on 4K UHD, make that file in your own editor. Do not upscale and re-label.
An upscaled 1080p source does not gain detail by being placed in a bigger frame anyway. If you generate the picture on Sume, the video models have their own resolution tiers, listed in the video router doc, and those are separate from Timeline's output limit.
Why 1080p is a sound default here
The practical question is whether a 4K file is worth the effort for this placement. Amazon's page lists the option, but the page text I read gives no rule that favours it. The same page gives a minimum video bit rate of 1 Mbps and recommends 4 Mbps or higher, and a maximum file size of 500MB. A 3840x2160 file would use much more of that file budget than a 1920x1080 one, so the headroom shrinks as the length grows.
For a 20-second ad, the size difference is small. For a 45-second ad, check the downloaded file against 500MB regardless of the resolution you pick. Sume does not report the output file size in the docs I read, so read it from the file after the download.
If your source footage is 4K and you want to keep the detail, cut and filter it on your own tools. If your footage was generated at 1080p or 720p, a bigger canvas adds nothing. Match the resolution to the source and to what Sume can output.
What Sume does not do
Sume does not write a 3840-pixel-wide Timeline or trim output today, and I found no setting that raises the 2160 side limit. If that changes, the Timeline page will say so. Also confirm the 500MB file cap and the codec on your final file, because Sume does not report them.
Sources
Related posts
More in Comparisons
- Amazon no-text lower-right rule vs Walmart contrast: where captions go
Amazon Sponsored Brands bans text in the lower right; Walmart wants 4.5:1 contrast. How to move Sume burned-in captions up with anchor ratios and check a still.
- Ad audio spec table: YouTube 48 kHz, Meta AAC 128 kbps, LinkedIn AAC
What YouTube, Meta Facebook Feed and LinkedIn say about video ad audio, and the Sume settings that keep, drop or extract it: trim audio, detach, timeline gain.
- Avatar face swap or talking video: recorded presenter vs scripted one
Sume has two ways to put an avatar on screen: face swap onto a 4 to 15 second source clip you recorded, or a script-driven talking video. How to choose.
- Six stills and a logo clip as references: Wan 3.0, Omni, H3 or Kling?
For a brand-kit video with six stills and one logo clip, Wan 3.0 and MiniMax H3 fit; Omni caps clips at 3 s; Kling 3 takes no references. 8 s prices inside.
Written by Sume