Voiceover spine: wav or mp3? 1,800 s is 158.76 MB or 28.8 MB
Timeline audio returns wav (sample-exact) or mp3 (smaller, padding at each edge). 1,800 s is 158.76 MB as 44.1 kHz mono wav vs 28.8 MB at 128 kbps.

Keep a voiceover spine as wav while you are still joining and editing it, and make mp3 only for the last copy. Sume's Timeline audio returns wav (pcm_s16le, sample-exact) by default or mp3 (smaller, but it adds priming padding again at every edge), so a 20-part mp3 concat has 19 seams that each carry padding. At the 1,800-second maximum a 44.1 kHz mono wav is about 158.76 MB and a 128 kbps mp3 is about 28.8 MB.
Sizes at 1,800 seconds
These are arithmetic from the sample formats in the docs (16-bit samples, the listed sample rates, and the 128 kbps rate the audio detach docs give for mp3). Real files add a small header, and mp3 sizes vary slightly with the encoder, so treat them as estimates.
| Format | Bytes per second | 1,800 seconds |
|---|---|---|
| wav pcm_s16le, 44.1 kHz mono | 88,200 B/s | 158.76 MB |
| wav pcm_s16le, 44.1 kHz stereo | 176,400 B/s | 317.52 MB |
| wav pcm_s16le, 48 kHz mono | 96,000 B/s | 172.80 MB |
| mp3 at 128 kbps | 16,000 B/s | 28.80 MB |
| wav pcm_s16le, 16 kHz mono (STT shape) | 32,000 B/s | 57.60 MB |
Which seams matter
The Timeline audio docs say to keep wav if the file will be joined again or if it drives lip-sync, because each mp3 edge adds priming padding. A concat of 20 parts, with the 20-part maximum, makes 19 internal joins. If those parts are mp3, the padding adds up across the joins; if they are wav, the join is gapless in the sample domain.
Joins cost $0.01 per job whatever the format, so the choice is about quality and storage, not price.
A practical rule
Generate and join in wav. Detach audio from video in wav at 16 kHz mono when the only reader is STT (32,000 bytes a second, 19.2 MB per 600 seconds). Export mp3 once, from the finished spine, when file size matters for delivery.
Storage over a catalog
Sizes add up. A library of 200 spines at the 1,800-second maximum is 200 x 158.76 MB = 31.75 GB as 44.1 kHz mono wav and 200 x 28.8 MB = 5.76 GB as 128 kbps mp3, a ratio of 5.5 to 1. Most spines are far shorter than the maximum, so scale by your average length. If storage matters, keep wav for the spines still in production and re-export the finished ones.
The size is also a transfer time. At 25 MB a second the 158.76 MB file takes about 6.4 seconds to move and the mp3 about 1.2 seconds, which matters little for a render but adds up in a loop over many files. These two transfer times are arithmetic at an assumed link speed, not measurements.
The practical advice is short: keep wav while you are still editing seams, because it is sample-exact, and choose mp3 only for the final delivery copy where size matters more than seam accuracy. Because mp3 frames add padding at each edge, 19 joins in a 20-part chain accumulate 19 small offsets that wav does not have.
Sources
Related posts
More in Media tools
- Wan 3.0 at 480p plus video upscale, 20 s: $1.43 vs $5.00 native 1080p
A 20 s Wan 3.0 clip at 480p plus a Sume video upscale costs $1.43 ($1.25 + $0.18) against $5.00 for native 1080p, if the upscale output size meets your need.
- wav or mp3 for joined audio: priming padding at every edge
Sume timeline audio outputs wav by default and mp3 as an option. Keep wav if you join again or lip-sync: mp3 adds priming padding at every edge.
- Which AI video models make a 20-second clip in one job on Sume?
Seedance 2.5 (4-30 s) and Wan 3.0 (2-30 s) cover 20 seconds in one job on Sume. Omni Flash 1.1 stops at 10 s, MiniMax H3 at 15 s. Full duration table.
- 10-minute ad at 8 Mbps is 600 MB: over TikTok and LinkedIn caps
8 Mbps for 600 seconds is 600 MB. That exceeds TikTok's and LinkedIn's 500 MB caps but fits Pinterest's 2 GB. Sume has no bitrate field, so shorten the cut.
Written by Sume