Podcast LUFS Standards: Real Targets for Every Major Platform
Podcast LUFS standards vary by platform, and loudness normalization doesn’t reward louder masters — it penalizes them. Here’s what the targets actually are, and why getting them wrong costs you more than volume.
The number most podcasters are chasing is the wrong one
A lot of podcast production guides still tell creators to master as loud as possible and let the platform normalize it down. That advice predates widespread loudness normalization, and it’s genuinely an oversimplification and misinterpretation of what is truly being done. When Apple Podcasts, Spotify, or YouTube normalize your episode downward, they’re usually not just turning a knob, they’re compressing the perceived dynamic range of everything you worked to preserve. Loud masters that get pulled down a lot sound squashed. Quiet masters that get pushed up pick up noise and problems become present that were not noticeable before. The target matters, and the target is a specific number, not a general direction.
This is a reference page for those numbers. It covers every major distribution platform, explains what true peak has to do with distortion on mobile speakers and earbuds, and flags where platform behavior has room for ambiguity. If you want the craft behind why these specs exist, the LUFS standards overview goes deeper on the psychoacoustic and technical foundations.
Podcast LUFS standards by platform
Apple Podcasts -16 LUFS integrated
Apple Podcasts normalizes to -16 LUFS integrated and is the most-cited podcast LUFS standard for a reason: Apple is one of the two dominant podcast platforms, and their target became the de facto cross-platform standard. If you’re mastering a single version for broad distribution RSS to Apple, Spotify, Amazon Music, Pocket Casts, Overcast, wherever -16 LUFS integrated is the right integrated loudness target.
True peak ceiling: -1 dBTP. This is not optional headroom. Don’t go tighter than that on a distribution master.
Spotify -14 LUFS for music, -16 LUFS for podcasts
Spotify operates two normalization systems that are easy to conflate. Their music streaming tier targets approximately -14 LUFS. For podcasts, Spotify doesn’t publish an explicit LUFS target the way Apple does so the practical approach is to treat podcast content as falling into the same ~-16 LUFS cross-platform norm. Treat that as a sound working assumption, not a documented spec.
The distinction matters if you’re producing a narrative podcast with heavy music-forward sequences full underscore, original score, or music-driven documentary work. Those episodes can feel quiet against the music library in a user’s playback queue. Mastering to -16 LUFS with good dynamic range will survive Spotify’s normalization intact. Mastering to -14 LUFS to chase music-tier loudness and then getting pulled down on Apple may cost you clarity in the low-mids where dialogue lives.
YouTube approximately -14 LUFS
YouTube’s loudness normalization targets approximately -14 LUFS integrated for standard video uploads (YouTube Music handles normalization differently). This puts YouTube closer to Spotify’s music tier than to the Apple Podcasts standard. If your podcast also lives as a video on YouTube which is increasingly common for interview shows, documentary series, and narrative podcasts with visual components you have two real options: master at -16 LUFS for broad distribution and accept that YouTube will push it up slightly, or deliver a separate YouTube master at -14 LUFS. For most podcast workflows, the -16 LUFS version performs acceptably on YouTube. For scripted or cinematic work where dynamics are part of the design, a separate -14 LUFS YouTube master is possibly worth the extra step.
Broadcast delivery European television, BBC, CBC, any network operating under EBU R128 targets -23 LUFS integrated with a true peak ceiling of -1 dBTP. This is significantly quieter than any podcast LUFS standard. Dialogue at -23 LUFS integrated sits comfortably amongst sound effects and lowered music. If your podcast has a broadcast distribution component then you may need to consider a separate mix pass. This spec is somewhat outdated but could still be expected in a delivery. It is best to speak with someone to be sure the spec isn’t something passed down but not matching the requirements.
My background is in broadcast television 37+ episodes of Air Crash Investigation / Mayday so EBU R128 delivery is a standard part of my audio post workflow. The jump between -16 LUFS podcast and -23 LUFS broadcast is not just a level adjustment; the mix balance can shift meaningfully, especially in scenes with wide dynamic range.
Why true peak is not the same as peak, and why it matters on earbuds
Sample-peak metering measures the amplitude at each discrete sample point. True peak metering measures the reconstructed continuous waveform what the signal actually does between samples during digital-to-analog conversion. On some content, especially material with fast transients and high-frequency content, the inter-sample peak can exceed 0 dBFS even when the sample peak reads safely below it. On a studio monitor, this may be inaudible. A Bluetooth earbud with a small driver will be less forgiving possibly resulting in audible distortion.
The -1 dBTP ceiling used across Apple Podcasts and most podcast distribution specs exists precisely to create a buffer for this inter-sample peak overshoot. If you’re only metering peak in your DAW and not true peak, you may be delivering content that clips on playback. Waves WLM and iZotope RX both display true peak alongside integrated LUFS use true peak metering on every final export, not just peak.
The measurement window matters: integrated vs. short-term vs. momentary
LUFS measurements come in three time windows, and the one that governs platform normalization is integrated meaning the average loudness across the entire duration of the file. Short-term LUFS (a three-second rolling window) and momentary LUFS (a 400ms window) are useful for mix decisions in the moment but are not what Apple or Spotify are measuring when they normalize your file.
This matters practically when your podcast has a cold open, a musical title sequence, a mid-roll baked-in ad, and a closing theme. Each of those sections will read differently on a short-term meter. What the platform sees is the integrated average across all of it. If your cold open is particularly loud and dense, it drags your integrated number higher than the body of the show. If your title music is -8 LUFS short-term for twenty seconds, it raises your integrated loudness average, which increases the amount of normalization the platform applies to the whole file. The podcast production workflow I use treats the integrated loudness target as a mix objective from session setup, not a post-export correction.
One file vs. multiple masters: what’s actually practical
The honest answer is that for most narrative and interview podcasts, a single -16 LUFS integrated / -1 dBTP master is the right podcast LUFS standard to follow for broad distribution. Apple gets exactly what it wants. Spotify applies mild normalization to podcast content anyway. YouTube pushes it up slightly but not destructively. You’re not leaving significant quality on the table with one master.
The case for multiple masters is narrower than most guides suggest. It’s real for productions with a genuine broadcast delivery requirement, productions where the creative loudness of a -14 LUFS YouTube master meaningfully serves the cinematic intent of the work, or productions doing primary distribution through a platform with a documented deviation from the -16 LUFS cross-platform norm, or possibly a deal that includes some legacy media. Outside of those cases, the complexity of managing multiple masters usually isn’t worth it at podcast budgets and schedules. You should spend the time to critically QC your files.
This page is meant as a working reference on podcast LUFS standards for production teams, producers, editors, and mixers who are making real decisions about deliverables something you can link a client to instead of re-explaining integrated loudness from scratch each time.
Sources
-
- Apple Podcasts (16 LUFS, 1 dBTP) Apple Podcasts audio requirements
-
- Spotify (14 LUFS playback normalization) Spotify loudness normalization
-
- EBU R 128 (broadcast, 23 LUFS) EBU Technical Recommendation R 128
-
- ITU-R BS.1770 (loudness & true-peak measurement) ITU-R Recommendation BS.1770
-
- YouTube (14 LUFS) community-measured; no official published spec.
For the broader picture across video and broadcast, see the LUFS standards guide.
Working on a scripted podcast, documentary series, or narrative audio project that needs broadcast-grade delivery? Send a rough cut or a spec question I’ll tell you what the deliverable actually needs to look like.