Podcast Audio Export Settings 2026: MP3, AAC, Sample Rate and Bitrate
Last reviewed: August 29, 2026
Quick answer: For a spoken-word podcast distributed by RSS, export a clean MP3 or AAC file at 44.1 or 48 kHz. Use 64–128 kbps for mono speech or 128–192 kbps for stereo as practical starting points. Apple’s current guidance accepts MP3 or AAC and recommends 64–128 kbps for mono or 128–256 kbps for stereo at 44.1/48 kHz. Spotify for Creators accepts MP3, M4A and WAV for uploaded audio episodes. Keep a lossless master before creating the delivery file.
Recommended podcast export settings
| Content | Format | Sample rate | Channels | Practical bitrate |
|---|---|---|---|---|
| Voice-only show | MP3 or AAC | 44.1 or 48 kHz | Mono | 64–128 kbps |
| Interview with stereo music | MP3 or AAC | 44.1 or 48 kHz | Stereo | 128–192 kbps |
| Music-focused program | AAC or MP3 | 44.1 or 48 kHz | Stereo | 192–256 kbps |
| Archive/master | WAV | Native project rate | As mixed | Lossless |
The delivery bitrates above are production starting points, not universal rules. Apple publishes a broader recommended range and notes that AAC gives better quality than MP3 at the same bitrate. Your podcast host may transcode the file, so confirm its current requirements before building an automated export preset.
MP3, AAC or WAV?
MP3: the safest general delivery choice
MP3 is widely supported by podcast hosts, RSS workflows and playback apps. It is easy to inspect and produces manageable files. For a conventional spoken-word show, a well-encoded MP3 remains a dependable default.
AAC or M4A: efficient quality
AAC can retain better quality than MP3 at an equivalent bitrate, particularly at lower rates. Apple Podcasts accepts AAC through RSS, and Spotify for Creators lists M4A among supported audio upload types. Confirm that your host produces a valid RSS enclosure and does not unexpectedly convert the file.
WAV: keep it as the master
WAV preserves the mix without lossy compression and is useful for archiving and future edits. It is much larger, however, and RSS distribution compatibility depends on the host. Keep a WAV master, then create an MP3 or AAC delivery copy.
44.1 kHz or 48 kHz?
Both 44.1 and 48 kHz are normal podcast sample rates. Use the rate that matches the recording and editing project when possible. Repeatedly converting between them does not add quality and can complicate the workflow.
- 44.1 kHz: common in music and audio-only production.
- 48 kHz: common in video, broadcast and mixed audio/video workflows.
If a podcast is also published as video, 48 kHz keeps the audio aligned with standard video production. If the entire audio project was recorded and edited at 44.1 kHz, there is usually no reason to upsample at the final export.
Mono or stereo?
Mono is efficient for one or more centered voices. A 96 kbps mono file gives one channel the full bitrate, while a stereo file must represent two channels. Use stereo when music, atmosphere or spatial separation is part of the production.
Do not switch between mono and stereo during an episode. Check that both speakers remain audible after any downmix, especially when interviews were recorded on separate left and right tracks.
Choose a bitrate without wasting space
| Setting | Use it when | Watch for |
|---|---|---|
| 64 kbps mono | Clean speech and small files are the priority | Sibilance and music may sound rough |
| 96–128 kbps mono | Speech needs extra clarity | Larger files with diminishing returns |
| 128 kbps stereo | Conversation with light music | Complex music may need more |
| 192–256 kbps stereo | Music and detailed ambience matter | Upload and download size |
Listen to a difficult section after export: sharp “s” sounds, applause, room noise and music reveal compression problems faster than a quiet sentence. Higher bitrate cannot repair clipped, distorted or noisy source audio.
Loudness, peaks and dynamics
Platforms may normalize playback, but normalization does not fix an uneven mix. A practical spoken-word workflow often targets approximately −16 LUFS integrated for stereo or −19 LUFS for mono, with true peaks controlled around −1 dBTP. These are common production targets rather than the Apple and Spotify file-format limits cited above.
Measure the complete finished episode, not only the intro. Loudness meters can give the same integrated value to two programs that feel different, so listen for abrupt speaker changes, over-compression, background noise and tiring high frequencies.
Export workflow
- Edit at the project’s native sample rate.
- Remove obvious clicks, hum and long unwanted silence.
- Balance speakers before adding master compression.
- Check loudness and true peak across the full episode.
- Export a lossless WAV master.
- Create the MP3 or AAC delivery file from that master or the final timeline.
- Add only necessary metadata and artwork.
- Listen to the exported file from beginning to end or spot-check every section.
- Upload to the host and inspect the processed episode.
Metadata and artwork
Use consistent episode titles, show names and numbering. Spotify advises keeping embedded artwork, ID3v2 tags and other metadata small when uploading MP3 files. Oversized embedded images increase the file without improving the image shown by every podcast app, because show and episode artwork may also come from the RSS feed.
Do not place private notes, local file paths or client information in metadata fields. Inspect the final file with a media-information tool before publishing.
Why an upload fails
| Problem | Likely fix |
|---|---|
| Unsupported file | Export MP3 or AAC according to the host’s requirements |
| Upload stalls | Use a stable connection and a smaller delivery file |
| Only one speaker is audible | Check left/right routing and mono compatibility |
| Episode sounds quieter after publishing | Check loudness, peaks and platform normalization |
| Harsh “s” sounds | Review de-essing and use a higher-quality encode |
| Wrong duration | Inspect the exported file and remove timeline gaps |
Pre-publish checklist
- Lossless master safely stored
- MP3 or AAC delivery file accepted by the host
- 44.1 or 48 kHz chosen intentionally
- Mono/stereo choice matches the content
- Bitrate tested on speech and music
- No clipping, missing channel or accidental silence
- Loudness and true peaks measured
- Metadata, artwork and explicit-content fields checked
- Final processed episode tested on phone and headphones
Frequently asked questions
Is 320 kbps necessary for a podcast?
Usually not for spoken-word delivery. It creates a larger file, while clean recording, editing and sensible loudness have a greater effect. Music-heavy shows may benefit from a higher stereo bitrate.
Should every podcast be stereo?
No. Mono is efficient and appropriate for centered speech. Use stereo when the content contains meaningful stereo music or atmosphere.
Can I upload WAV directly?
Spotify for Creators lists WAV as supported for audio episodes, but RSS and hosting workflows vary. Keep WAV as the master and follow the destination host’s current delivery requirements.
Is AAC always better than MP3?
AAC is generally more efficient at the same bitrate, but MP3 offers extremely broad compatibility. Choose based on the host and distribution workflow, then test the processed result.
Bottom line
Keep a lossless master, then export a distribution copy that matches the podcast’s real content. For voice, mono MP3 or AAC at 44.1/48 kHz and 64–128 kbps is a practical start. For stereo productions, begin around 128–192 kbps and increase only when listening tests justify it. Always verify the host’s current rules and the final processed episode.