Podcast Audio Quality Checklist: 15 Checks Before Publishing

A repeatable release check is more useful than collecting “professional” presets. Keep the original recordings, the edit project and the exact delivered file. If something sounds wrong after publication, those versions make it easier to identify where it changed.

Recording and edit checks

1. Confirm the right source. Check that each participant used the intended microphone and that the recording is complete. Listen near the start, middle and end before investing in processing.
2. Check overloaded passages. Listen to laughter, loud emphasis and plosives in the original. Lowering an already clipped file changes level without reconstructing the missing waveform. Re-record important damaged lines when practical.
3. Compare speakers. Listen to consecutive turns at a fixed volume. Adjust individual clips or tracks when one person is consistently difficult to follow; do not make the entire episode louder to fix one guest.
4. Inspect background noise. Compare room tone with speech. If using noise reduction, preview both and listen for watery or metallic artifacts. Do not chase a universal noise-floor number at the expense of the voice.
5. Review edits in context. Listen across every major cut. Preserve intentional breaths and pauses; a rigid rule that deletes every pause over a fixed duration can alter the speaker’s meaning or rhythm.

Mix and processing checks

6. Keep speech intelligible under music. Compare an introduction and an ordinary spoken section. Adjust the bed relative to the voice before adding broad master gain.
7. Use EQ for an identified problem. Compare a small change with bypass at similar listening volume. Avoid assuming that every voice needs the same low-frequency cut or presence boost.
8. Check compression on quiet and loud delivery. Preview normal speech, emphasis and silence. Compression controls interact; listen for flattened consonants, pumping and newly obvious room noise.
9. Review channel layout. Check that a speaker is not accidentally isolated to one ear. Compare a mono fold-down when stereo effects or routing could affect intelligibility. Keep the intended layout consistent through export.
10. Listen to transitions. Check intro-to-speech, advertisements, inserted clips and the outro. A whole-episode average can conceal a startling transition or an unusually quiet segment.

Measurement and delivery checks

11. Measure the whole episode. Use integrated loudness and inspect shorter passages separately. Save the meter name, version and channel layout with the result. Our LUFS guide and measured examples explain what those readings do and do not establish.
12. Check true peak separately. A sample-peak meter does not estimate every reconstructed peak. Leave headroom appropriate to the actual delivery specification, and recheck the encoded file.
13. Use the destination’s supported format. Apple Podcasts accepts MP3 or AAC through RSS and recommends overall loudness near −16 LKFS, within 1 dB, with true peak no higher than its stated −1 dBFS limit. This is Apple-specific guidance, not a promise about how every podcast app normalizes playback. Its direct-upload formats differ from RSS formats.
14. Open the exact export. Check duration, start/end, channel balance and audible encoding artifacts. A setting in the project does not prove the exported file contains the expected mix. Keep a lossless master if your workflow allows it.
15. Verify the delivered episode. After upload, play the episode from the host’s preview or published player as appropriate. Check title, artwork, episode order and enclosure playback. Test the same speech and transition on headphones and a second everyday device without repeatedly adjusting the volume.

A release log you can copy

Record these values for each episode; fill them with measurements from the actual file rather than a template’s example numbers.

Field	What to record
Version	Episode identifier, final filename and export date
Delivery	Destination, RSS or direct upload, format and channels
Measurement	Meter/version, integrated LUFS and true peak
Listening	Devices and timestamps checked
Corrections	Any unresolved passage and who will address it
Distribution	Host playback checked; directory submissions or feed updates verified

If hosted with Spotify for Creators, its distribution guide explains that other directories require your own RSS submission. Uploading there does not automatically complete distribution everywhere.

Can a browser extension replace these checks?

Hearably’s extension can alter a listener’s supported browser tab; it does not modify the episode that subscribers download. Studio processes uploaded files, with Free and Pro limits shown on the pricing page. Use the free podcast tools guide to choose tools for recording, editing, measurement and hosting as separate tasks.

Keep the final listening comparison tied to the exported file. A more pleasant monitoring setup is useful, but the release decision should follow the sound your audience actually receives.