Vidyard upload: raw files up to 20 GB, H.264 up to 4K
Vidyard accepts raw video up to 20 GB, then encodes H.264 MP4 derivatives from 360p to 2160p with AAC audio. What to render with Sume.

Vidyard keeps the raw file you upload, up to 20 GB, and encodes MP4 derivatives itself: H.264, progressive, at the source frame rate and a variable bitrate, from 360p up to 2160p. Audio is AAC, 2-channel stereo, 48 kHz. Videos with multiple audio tracks must be uploaded as H.264/AAC in an .mp4. This is from Vidyard, read 2026-10-01.
What does Vidyard do with an upload?
| Item | Vidyard says |
|---|---|
| Raw file | Same as source, up to 20 GB |
| Derivative container | MP4 |
| Video | H.264, progressive, source frame rate, variable bitrate |
| Audio | AAC, 2-channel stereo, 48 kHz |
| Resolutions | 360p up to 2160p |
| Multiple audio tracks | Upload as H.264/AAC in an .mp4 |
Do I need to tune the encode before I upload?
Vidyard says it handles optimization of encoding settings for you. That suits Sume, which has no bitrate or codec field: you choose size, frame rate and length, and Vidyard re-encodes. Frame rate carries through, so pick 24, 25, 30 or 60 deliberately.
How do I render a 1080p file for Vidyard?
Timeline 1.0 (POST /v1/timeline-1.0/render) takes output.width and output.height as even integers from 256 to 2160 and output.fps of 24, 25, 30 or 60, or omits fps to match the sources. It needs an Idempotency-Key, accepts only media.sume.com sources, and returns one MP4 at $0.10 per output minute, rounded up. The unbilled POST /v1/timeline-1.0/plan previews the cost first.
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: vidyard-1080p-001" \
-d '{
"audio": { "mode": "silence", "duration_seconds": 90 },
"output": { "width": 1920, "height": 1080, "fps": 30 },
"video": [
{ "source_url": "https://media.sume.com/artifacts/artf_demo/shot.mp4",
"start": 0, "duration": 90, "fit": "cover" }
]
}'Can I get a 2160p derivative?
Vidyard lists resolutions up to 2160p. Timeline's width and height stop at 2160 each, so a 16:9 frame at 3840x2160 cannot be requested. 1920x1080 is the practical maximum for a landscape clip, and 2160x3840 is also past the cap.
How do I check audio and size?
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.
Sources
Related posts
More in Media tools
- 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.
- 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.
Written by Sume