Spotify video audio channels: mono upmixed, 5.1 downmixed
Spotify upmixes mono to stereo, downmixes 5.1, and rejects multi-channel. Sume audio detach offers only channels source or mono; it cannot mix to stereo.

Spotify for Creators handles channel layout for you: its Video specs say mono is upmixed to stereo, surround 5.1 is downmixed to stereo, and multi-channel is not supported. Sume audio detach has one channel choice, channels of source (default) or mono, so it can keep the layout or collapse to mono but cannot mix up to stereo or 5.1.
Spotify's rules are from its Video specs page; Sume's from Audio detach, read 2026-10-01.
What does Spotify do to each layout?
| Your audio | Spotify says |
|---|---|
| Mono | Will be upmixed to stereo |
| Surround 5.1 | Will be downmixed to stereo |
| Other multi-channel | Not supported |
What does audio detach give me?
POST /v1/audio-detach pulls the audio track of a Sume-hosted video into a new file. format is wav (default, pcm_s16le sample-exact) or mp3 (128 kbps). sample_rate is 16000, 44100 or 48000, or omitted to inherit the source. The result reports channels, so you can read back what you got.
Should I pick source or mono?
Leave channels at source when you only want the track out unchanged; Spotify will do its own upmix or downmix on upload. Choose mono when a later step, such as speech-to-text, wants one channel; the docs call 16000 with mono the speech-to-text shape. See keep source channels and sample rate.
Why does detach fail on my file?
A source with no audio track fails with detach_source_has_no_audio. Check probe.has_audio with video inspect first. If the file fails on Spotify's side instead, the layout rows above are the first thing to check.
Sources
Related posts
More in Developers
- sync-3 image formats JPEG PNG WebP vs Sume image URL rules
sync-3 accepts JPEG, PNG and WebP stills. Sume's docs set URL rules instead: a fetchable public HTTPS image, with private and signed URLs rejected.
- Sync Labs batch API (20 to 500) vs Sume bulk runs (1 to 100)
Sync Labs batch takes 20 to 500 lip sync generations in one JSONL file on Scale and Enterprise. Sume bulk runs queue 1 to 100 Format runs with a 1 to 16 window.
- Sync Labs API rate limit: 100 per minute, and Sume headers
Sync Labs allows 100 POST /v2/generate and 600 GETs a minute. Sume has a per-plan requests-per-minute budget; read ratelimit headers and retry-after.
- Synthesia Billing API credit usage vs Sume's /v1/usage ledger
Synthesia added a Billing API endpoint for credit usage. Sume's equivalent is GET /v1/usage: reservations, captures and refunds, filterable by run or job.
Written by Sume