DOOH 1080x1920 10 s master: a render checklist
An example vertical DOOH master (1080x1920, H.264 MP4, 10 s, 25 to 30 fps). What a Sume video request controls and what you must check yourself.

A vertical digital out-of-home (DOOH) master is often specified as 1080x1920, MP4 with H.264, a 10-second runtime, 25 to 30 fps and a modest bitrate and file size. Specs vary by network and I could not confirm these numbers on a vendor page, so treat them as a working example and use the spec sheet of the network that will run your ad.
What a Sume request controls
Sume's video request exposes duration, resolution and aspect_ratio. It does not list a frame-rate or bitrate field in the request parameters, and every v1 model reports supported_sizes: null, so size is rejected with 400 unsupported_parameter. That means you can ask for a 9:16 clip at 1080p and a duration of 10 seconds, but you cannot dictate pixels, fps or bitrate at generation time. Video trim can conform width, height and fps afterward: its output option takes fps of 24, 25, 30 or 60 with precision exact.
Checklist
Treat the generated file as a source, then check and, if needed, conform it.
| Spec (summary) | Sume request field | Action |
|---|---|---|
| 1080x1920 | resolution 1080p, aspect_ratio 9:16 | Probe the output for real dimensions; trim output can conform width and height |
| 10 s master | duration 10 | Pick a model that accepts 10 s |
| 25 to 30 fps | None listed | Probe; conform with video trim output.fps (exact only) if off |
| Under 5 Mbps, 10 to 25 MB | None listed | Check file size, re-encode if over |
Probe the file
Video inspect probes one Sume-hosted clip without re-encoding it. Call it with frames: false for a probe-only read, and read the probe object in the response. The docs name probe.has_audio explicitly; check the rest of the probe fields in a live response before you rely on them. Many DOOH screens play without sound, but some networks reject files with an audio track, so confirm that too.
Submit a 10-second vertical job on a model that accepts it. seedance-2 accepts 4 to 15 seconds and offers 1080p:
curl -X POST https://api.sume.com/v1/videos \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: dooh-master-001" \
-d '{"model":"seedance-2","prompt":"Slow push-in on a product on a pedestal, clean studio light","duration":10,"resolution":"1080p","aspect_ratio":"9:16"}'Sources
Related posts
More in Use cases
- Dribbble shot image: 1600 px wide, 10 MB, PNG JPG or GIF
Dribbble recommends images at least 1600 px wide and takes PNG, JPG or GIF up to 10MB. Sizes Sume can generate at 1600 wide, and a script to check the file.
- Dribbble shot video: 20 MB limit and the bitrate budget
Dribbble allows MOV or MP4 video up to 20MB and recommends 1600 px width. What 20MB means in average Mbps by clip length, and which Sume Timeline fields help.
- Dub a 60-second clip into Hindi: Sume step costs before translation
A 60-second dub on Sume is four steps. Detach audio $0.01, STT $0.01, translate with your own tool, then TTS in Hindi: about $0.0628 for 900 characters.
- eBay AI listing photos: the seller owns accuracy
eBay's User Agreement makes sellers responsible for listing accuracy, including generative AI content. Generate 1:1 stills from your real photo and check them.
Written by Sume