Substack video upload: 1080p H.264 at 8 Mbps or below
Substack's fastest-processing tips are 1080p or 1440p or smaller, H.264, 8 Mbps or below, 5 to 120 fps and AAC. What Sume can render for it.

For the fastest processing on Substack, use 1080p or 1440p or smaller, H.264, a bitrate of 8 Mbps or below, 5 to 120 fps and AAC audio. The recommended maximum is 20 GB. Video posts get AI transcripts and a free-preview paywall. Specs are from Substack Support, read 2026-10-01.
What are Substack's fastest-processing settings?
| Setting | Substack tip |
|---|---|
| Resolution | 1080p or 1440p, or smaller |
| Codec | H.264 |
| Bitrate | 8 Mbps or below |
| Frame rate | 5 to 120 fps |
| Audio | AAC |
| Size | Recommended maximum 20 GB |
Can Sume render 1440p?
No. Timeline's output.width and output.height stop at 2160, and a 16:9 1440p frame is 2560x1440, whose long edge is past that. 1920x1080 fits, and Substack lists 1080p.
How do I render a 1080p file?
Frame rate is easy: 24, 25, 30 and 60 all sit inside Substack's 5 to 120 range. 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: substack-1080p-001" \
-d '{
"audio": { "mode": "silence", "duration_seconds": 300 },
"output": { "width": 1920, "height": 1080, "fps": 30 },
"video": [
{ "source_url": "https://media.sume.com/artifacts/artf_demo/shot.mp4",
"start": 0, "duration": 300, "fit": "cover" }
]
}'How do I keep the bitrate at 8 Mbps or below?
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. Compare file size per second after a test render. 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.
Do I get transcripts from Sume?
Substack makes its own AI transcripts for video posts. Sume's Video inspect also has an optional transcript, which is billed, but you do not need it to publish on Substack.
Sources
Related posts
More in Media tools
- Suno's EQ and compressor tips vs Sume Timeline mix controls
Suno published guides on EQ and compression for AI tracks. Sume Timeline has gain and ducking but no EQ or compressor. What you can and cannot do.
- Teachable video files: MP4, MOV or AVI, 2 GB each, 1080p
Teachable recommends MP4, MOV or AVI, 1080p at 24 to 30 fps, with 2 GB per file and 20 GB overall. How to render a fitting lesson with Sume.
- Thinkific video upload: 3 GB, H.264 MP4, 5,000 to 8,000 kbps
Thinkific takes videos under 3 GB, H.264 MP4 at 5,000 to 8,000 kbps, constant 15 to 60 fps, up to 1080p. What Sume can render for it.
- Topaz Starlight Fast 3 vs Sume Video Upscale: what you can set
Topaz says Starlight Fast 3 runs at 4x the speed of Precise. Sume Video Upscale 1.0 has its own fast, standard and pro tiers, priced per input second.
Written by Sume