Roku ad frame rates: only three allowed, probe first

Roku's creative technical requirements page lists only three frame rates: 23.98, 25 and 29.97 fps. Check your file's frame rate before you upload, because an AI-generated clip may not use one of them. Sume's video inspect returns probe facts for a hosted clip.

The reported spec

These values come from Roku's creative technical requirements page, read on 2026-10-03. Specs change, so recheck the page before you submit.

Probe with Sume

POST /v1/video-inspect reads one clip that already lives on media.sume.com in your workspace; import first with POST /v1/media-imports, since there is no open-internet fetch. An Idempotency-Key is required. Set frames to false for probe only, with no stills. The finished resource carries a probe object; read the clip's duration and technical facts there. If frame rate is not in the probe fields you see, check it with your own tooling before upload.

Default mode is sync, which waits up to 30 seconds and returns 200 with the finished inspect or 202 with the queued job to poll.

curl -X POST https://api.sume.com/v1/video-inspect \
  -H "x-api-key: $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: roku-probe-001" \
  -d '{
    "video_url": "https://media.sume.com/artifacts/artf_demo/spot.mp4",
    "frames": false
  }'

If the clip is out of range

For length, POST /v1/video-trim cuts a [start, end) range into a new MP4 and leaves the source untouched. It needs video_url, start, and exactly one of end or duration. Trim does not change the frame rate, so a wrong frame rate needs a re-encode outside Sume's documented tools.

Remember that generative video models have their own aspect-ratio and length limits. Roku's table lists a minimum of 1920x1080; check that the catalog row for your model supports it.