Vimeo upload settings: H.264, 10-20 Mbps at 1080p, constant frame rate
Vimeo recommends H.264 High Profile, 10 to 20 Mbps at 1080p, constant frame rate and AAC-LC audio. What Sume can and cannot set for you.

Vimeo recommends H.264 High Profile with a constant frame rate, 10 to 20 Mbps for 1080p, and AAC-LC audio at 320 kb/s and 48 kHz. Sume lets you set resolution and frame rate on a render but lists no bitrate or codec field, so the bitrate target is yours to check after the render. Specs are from Vimeo Help, read 2026-10-01.
What bitrate does Vimeo recommend per resolution?
| Resolution | Recommended bitrate |
|---|---|
| SD | 2 to 5 Mbps |
| 720p | 5 to 10 Mbps |
| 1080p | 10 to 20 Mbps |
| 2K | 20 to 30 Mbps |
| 4K | 30 to 60 Mbps |
| 8K | 50 to 80 Mbps |
Which frame rates and audio does Vimeo want?
Vimeo asks for a constant frame rate of 23.98, 24, 25, 29.97, 30, 50, 59.94 or 60. Audio is AAC-LC at 320 kb/s and 48 kHz. Color is BT.709 or BT.2020, with 10-bit or more recommended. Its video formats are H.264 High Profile, Apple ProRes 422 (HQ) or H.265.
Which of those can I set with Sume?
Frame rate: Timeline's output.fps takes 24, 25, 30 or 60, and each is on Vimeo's list. Resolution: width and height are even integers from 256 to 2160, so 1080p fits, but 4K UHD (3840x2160) does not. Sume's docs list no bitrate or codec field. The render endpoints refuse codec, crf and filtergraph keys with a 400, so you cannot tune the encode from the request. Sume's docs say nothing about color space or audio bitrate.
curl -X POST https://api.sume.com/v1/timeline-1.0/render \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: vimeo-1080p-001" \
-d '{
"audio": { "mode": "silence", "duration_seconds": 30 },
"output": { "width": 1920, "height": 1080, "fps": 30 },
"video": [
{ "source_url": "https://media.sume.com/artifacts/artf_demo/shot.mp4",
"start": 0, "duration": 30, "fit": "cover" }
]
}'How do I check the result?
Probe the finished file with Video inspect 1.0. With frames: false it is a probe only, it is unbilled, and it reports width, height, container, fps and duration_seconds. It does not report file size, codec or bitrate, so check those with a local tool before you upload.
Bitrate is simply file size divided by duration, so a local check shows whether a 1080p file landed inside 10 to 20 Mbps.
What if the bitrate is below Vimeo's range?
Vimeo gives the ranges as recommendations. If a render comes out lighter, upload it and compare playback against your target before you re-render.
Sources
Related posts
More in Media tools
- Wistia export: H.264 MP4 at 5,000 to 8,000 kbps, 26 GB cap
Wistia accepts files up to 26 GB and recommends H.264 MP4, 5,000 to 8,000 kbps, constant 15 to 60 fps, AAC audio. What Sume can render for it.
- Yelp video ads: 2 minutes, 500 MB, and you upload the actual file
Yelp video ads allow up to 2 minutes and 500 MB in MP4, WMV, MOV or AVI, and YouTube or streaming links do not work. Render and trim a file with Sume.
- YouTube image posts in Shorts: up to 10 images, 16 MB each, 1:1
YouTube image posts take JPG, PNG, GIF or WEBP up to 16 MB, up to 10 images per post, with 1:1 suggested. How to make 1:1 images with Sume.
- How to assemble a long-form video with the Timeline 1.0 API
Timeline 1.0 renders one audio spine plus 1 to 200 ordered video slots into one MP4. Every URL must be Sume-hosted; the plan preflight is unbilled.
Written by Sume