Apple Podcasts audio specs vs Sume TTS mp3 44.1 kHz 128 kbps
Apple Podcasts wants 44.1 kHz audio, about -16 LKFS and, for WAV or FLAC, stereo. What Sume TTS mp3 output meets and what you must still measure yourself.

Apple's audio requirements page for podcasters asks for WAV, FLAC or MP3 uploads at a minimum of 44.1 kHz, and loudness around -16 LKFS with a true peak at or below -1 dBFS. Sume TTS 1.0 defaults to mp3 at 44.1 kHz and 128 kbps, which matches the sample-rate minimum and sits inside Apple's recommended MP3 bit-rate range. Sume's docs do not state a channel layout or loudness normalization, so measure both before you publish.
What Apple's page says
Apple lists separate rules by format. The table keeps the lines relevant to a TTS-made episode.
| Format | Requirement |
|---|---|
| Accepted files | WAV, FLAC or MP3 in Podcasts Connect; MP3 or AAC through RSS |
| WAV and FLAC | 44.1 kHz minimum, 16 or 24 bit, stereo required (single channel rejected) |
| MP3 mono | 44.1 kHz and 32 kbps minimum; 96 to 128 kbps recommended |
| MP3 stereo | 64 kbps minimum; 128 to 256 kbps recommended |
| Loudness | About -16 dB LKFS plus or minus 1; true peak not above -1 dBFS |
Make the file with Sume
Sume's output_format offers 44.1 kHz and 48 kHz, mp3 bit rates up to 192 kbps, and wav. The request below pins the documented mp3 default explicitly.
import os, requests
r = requests.post(
"https://api.sume.com/v1/tts-1.0/generate",
headers={"Authorization": f"Bearer {os.environ['SUME_API_KEY']}",
"Idempotency-Key": "tts-demo-001"},
json={"transcript": "Welcome back. Today we cover three updates.",
"avatar_id": os.environ["SUME_AVATAR_ID"],
"generation_config": {"speed": 0.95, "emotion": "warm"},
"output_format": {"container": "mp3", "sample_rate": 44100,
"bit_rate": 128000}},
)
print(r.status_code, r.json())Measure what the docs do not promise
Run the file through ffprobe to read its channel count, and a loudness meter for integrated loudness and true peak. If it is mono and you want WAV or FLAC, convert to stereo in your editor first. If loudness is off, normalize in your editor; do not assume the TTS output lands at -16 LKFS.
Worked example
A quick measurement routine avoids a rejected upload.
- Run
ffprobeon the file and read the sample rate, channels and bit rate. - Measure integrated loudness and true peak in your editor or an ebu-r128 tool.
- If you need WAV, export stereo at 44.1 kHz and 16 or 24 bit.
Checklist before you commit
Apple's loudness lines are targets, not guarantees that every file passes; a mixed episode with music needs its own measurement.
- Pick MP3 or AAC for RSS delivery.
- Pick WAV or FLAC only if your files are stereo.
- Check the page again for changes before each season.
Sources
Related posts
More in Use cases
- Apple Podcasts host-read video ads: cut the spot with Sume trim
Apple Podcasts lets creators insert video ads including host-read spots. Cut a host-read spot from an episode with Sume's exact-precision video trim.
- AI Act marking exemption for B2B and industrial output: how narrow
The Commission FAQ says a narrow Article 50(2) marking exemption is envisaged for B2B or industrial outputs, with conditions in the guidelines. What it lists.
- AI Act Article 50 fines: up to EUR 15M or 3%, and who enforces it
The Commission's Article 50 FAQ says fines can reach 15 million euros or 3% of worldwide turnover, enforced mainly by national market surveillance authorities.
- AI Act Article 50 for non-EU providers: output used in the EU
The Commission FAQ says providers outside the EU are subject to the AI Act if their system's output is used in the EU. How it defines provider and deployer.
Written by Sume