Spotify video podcast specs: MP4, 1080p 16:9, H.264

Spotify for Creators recommends a 16:9 MP4 at 1080p or higher, H.264 and AAC-LC, 24 to 60 FPS, one video and one audio track. How to render and check it.

5 min readSume
All posts

Spotify for Creators recommends a 16:9 MP4 at 1080p or higher, encoded as H.264 with AAC-LC audio, at 24, 25, 30, 50 or 60 FPS, with exactly one video track and one audio track of the same duration. MOV is also compatible. These are the specs for uploading a video episode, not for Spotify ads or a Canvas loop. Everything below is from Spotify's video specs, read 2026-09-29.

What are Spotify's video podcast specs?

Spotify video episode specs, from Spotify for Creators, read 2026-09-29.
ItemRecommendedAlso compatible
File sizeLess than 10 GBUp to 60 GB
DurationLess than 4 hoursUp to 12 hours
ContainerMP4MOV (FLV and AVI discouraged)
Video codecH.264H.265 (HEVC), many others
Resolution1080p or higher180p or higher
Aspect ratio16:9Any, with letterboxing or pillarboxing
Frame rate24, 25, 30, 50 or 60 FPS-
Video bitrate25 Mbit/s CBR (1080p), 35 Mbit/s CBR (4K)Any within the size range
AudioAAC-LC, 128 Kbps or higher, stereoFLAC and others; mono is upmixed

Does Spotify have a file size limit?

The two Spotify pages read differently. The specs page recommends under 10 GB and accepts up to 60 GB. The publishing page says Spotify for Creators has no file size limit, but that larger files take longer to process and are more likely to fail if your connection drops. It also says the file cannot be longer than 12 hours, that you can only upload video on the web, and that on platforms other than Spotify your episode will be audio-only.

How do I render a Spotify-ready video with Sume?

Timeline 1.0 sets the frame: output.width and output.height are even integers from 256 to 2160, so 1920x1080 is valid, while a 3840x2160 frame is outside the range. output.fps takes 24, 25, 30 or 60, which covers four of Spotify's five rates and not 50. The audio length, audio.duration_seconds, runs from 1 to 1800 seconds, so one render tops out at 30 minutes, well under Spotify's 4-hour recommendation; a longer episode would need another tool.

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: spotify-episode-001" \
  -d '{
    "audio": { "url": "https://media.sume.com/artifacts/artf_demo/episode.wav",
               "duration_seconds": 600 },
    "output": { "width": 1920, "height": 1080, "fps": 30 },
    "video": [
      { "source_url": "https://media.sume.com/artifacts/artf_demo/cover.mp4",
        "start": 0, "duration": 600, "fit": "cover" }
    ]
  }'

Which Spotify specs can Sume not set?

Timeline's documented output fields are size, frame rate and fades. The docs list no video bitrate, CBR or codec field, so the 25 Mbit/s CBR and the H.264 recommendation cannot be requested by you; Spotify says any bitrate is compatible within the size range, and H.265 and many other codecs are listed as compatible. Read what you got with Video inspect 1.0, whose probe reports width, height, fps, container, video_codec, has_audio, duration_seconds and size_bytes without billing. If the probe shows a different codec than you want, re-encode with your own editor. For a Canvas loop or ads rather than an episode, see Spotify video ad specs.

Sources

Related posts

More in Media tools

All Media tools posts

Written by Sume