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.

Wistia accepts files up to 26 GB and recommends an H.264 MP4, 640 to 3840 px wide, at 5,000 to 8,000 kbps and a constant 15 to 60 fps. Audio is AAC, 44.1 kHz, 2-channel stereo. ProRes is converted to H.264 on upload. Specs are from Wistia Support, read 2026-10-01.
What does Wistia recommend?
| Setting | Wistia says |
|---|---|
| Max upload | 26 GB, larger files fail |
| File type | MP4 recommended |
| Codec | H.264/AVC required, ProRes converted |
| Width | 640 to 3840 px |
| Bitrate | 5,000 to 8,000 kbps, 6,000 to 8,000 for standard video |
| Frame rate | Constant, 15 to 60 fps |
| Audio | AAC, 44.1 kHz, 2-channel stereo |
What can Sume match, and what can it not?
Frame rate and size: output.fps of 24, 25, 30 or 60 sits inside 15 to 60, and width up to 2160 sits inside 640 to 3840 (3840 itself is out of range). 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.
How do I render a 1080p MP4?
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: wistia-1080p-001" \
-d '{
"audio": { "mode": "silence", "duration_seconds": 120 },
"output": { "width": 1920, "height": 1080, "fps": 30 },
"video": [
{ "source_url": "https://media.sume.com/artifacts/artf_demo/shot.mp4",
"start": 0, "duration": 120, "fit": "cover" }
]
}'How do I verify bitrate?
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.
Wistia says it recommends these settings primarily to reduce file size and upload time, so a test upload is the quickest check.
Is the 26 GB cap a concern?
No for Sume renders. A Timeline output is at most 30 minutes (audio.duration_seconds up to 1800).
Sources
Related posts
More in Media tools
- 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.
- How to burn captions onto a video with the Sume API
Send a public HTTPS video URL to POST /v1/video-captions and get a job-backed captioned video, timed by speech-to-text or by text you supply.
Written by Sume