Podcast Loudness Normalizer LUFS Calculator
Calculate the gain needed to reach a target LUFS such as -16 for podcasts, check true-peak headroom at -1 dBTP and get a compression ratio when needed.
Podcast Loudness Normalizer LUFS Calculator
Calculator
Adjust values & calculateEnter your values below. Every result is computed in your browser โ no data is sent to any server.
Formula: Gain (dB) = Target LUFS - Current LUFS; Safe Gain = min(Gain, Gain + (-1.0 - (TruePeak + Gain)))
Worked example โ Need compression (2.5:1 ratio) before normalizing to avoid clipping. Safe gain without compression: +2.0 dB
Formula
Gain (dB) = Target LUFS - Current LUFS; Safe Gain = min(Gain, Gain + (-1.0 - (TruePeak + Gain)))
The required gain is simply the difference between your target and current LUFS levels. However, if applying that gain would push the true peak above -1.0 dBTP (the standard limit), the safe gain is reduced to maintain headroom. When dynamic range exceeds 8 LU, a compressor ratio is suggested as 1 + (DR - 8) / 4.
Worked Examples
Example 1: Quiet Podcast Normalization
Problem:A podcast episode measures -22 LUFS with a true peak of -3.0 dBTP and 14 LU dynamic range. Target is -16 LUFS.
Solution:Gain needed = -16 - (-22) = +6.0 dB New true peak = -3.0 + 6.0 = +3.0 dBTP (CLIPS!) Safe gain = 6.0 + (-1.0 - 3.0) = 6.0 - 4.0 = +2.0 dB Achievable LUFS = -22 + 2.0 = -20.0 LUFS Compressor ratio needed: 1 + (14-8)/4 = 2.5:1 Solution: Apply compression first to reduce dynamic range, then normalize.
Result:Need compression (2.5:1 ratio) before normalizing to avoid clipping. Safe gain without compression: +2.0 dB
Example 2: Well-Recorded Podcast Fine-Tuning
Problem:A podcast episode measures -18 LUFS with true peak of -2.5 dBTP and 8 LU dynamic range. Target is -16 LUFS.
Solution:Gain needed = -16 - (-18) = +2.0 dB New true peak = -2.5 + 2.0 = -0.5 dBTP (clips at -1.0 limit) Safe gain = 2.0 + (-1.0 - (-0.5)) = 2.0 - 0.5 = +1.5 dB Achievable LUFS = -18 + 1.5 = -16.5 LUFS Dynamic range 8 LU is fine, no compression needed.
Result:Apply +1.5 dB safe gain for -16.5 LUFS, or use a limiter to achieve full -16 LUFS target
Frequently Asked Questions
What is LUFS and why does it matter for podcasts?
LUFS (Loudness Units Full Scale) is an internationally standardized measurement of perceived audio loudness defined in ITU-R BS.1770. Unlike peak metering which only measures the highest signal level, LUFS accounts for how the human ear actually perceives loudness across different frequencies. For podcasts, this matters because listeners often switch between different shows, and inconsistent loudness forces them to constantly adjust their volume. The standard target for podcasts is -16 LUFS, which Apple Podcasts, Spotify, and most major platforms recommend. Broadcasting standards use -23 LUFS (EBU R128) or -24 LUFS (ATSC A/85).
What is true peak and why should I care about headroom?
True peak measures the actual maximum amplitude of the audio signal, including inter-sample peaks that can occur between discrete digital samples. Standard peak meters can miss these inter-sample peaks, which may cause distortion when the audio is converted to analog or transcoded to lossy formats like MP3 or AAC. The recommended true peak limit for podcasts is -1.0 dBTP (decibels True Peak). This headroom prevents clipping artifacts during encoding. If normalizing your audio would push the true peak above -1.0 dBTP, you need to either apply a limiter or reduce the gain adjustment.
How does dynamic range affect podcast listening experience?
Dynamic range is the difference between the loudest and quietest parts of your audio, measured in LU (Loudness Units). A podcast with too much dynamic range (above 12 LU) means quiet passages may be inaudible in noisy environments like cars or public transit, while loud moments may be jarring. Too little dynamic range (below 4 LU) sounds flat and fatiguing over long listening sessions. The sweet spot for podcasts is typically 6-10 LU. If your dynamic range is too wide, a compressor with a gentle ratio of 2:1 to 4:1 can bring it under control before applying loudness normalization.
Should I normalize before or after compression and EQ?
The recommended signal chain is: noise reduction first, then EQ, then compression, and loudness normalization last. Normalizing after all other processing ensures your final output meets the target LUFS accurately. If you normalize first and then apply EQ or compression, those processes will change the loudness level. Many DAWs and podcast editors like Adobe Audition, Audacity, and Hindenburg offer integrated loudness normalization as a final mastering step. Some tools like Auphonic can handle the entire chain automatically with AI-driven processing.
What happens when platforms auto-normalize my podcast?
Most streaming platforms apply their own loudness normalization. Spotify normalizes to -14 LUFS, Apple Podcasts to -16 LUFS, and YouTube to -14 LUFS. If your podcast is louder than the target, the platform will turn it down (no quality loss). If it is quieter, the platform may turn it up, which can amplify noise floor and artifacts. This is why targeting -16 LUFS yourself gives the best results: it matches Apple Podcasts exactly, and Spotify will only reduce it by 2 dB rather than amplifying a quiet signal. Always normalizing to the standard yourself ensures the best quality across all platforms.
How do K-weighting and gating shape the LUFS reading?
BS.1770 first passes the signal through a two-stage K-weighting filter: a high-shelf boost that approximates head diffraction plus a high-pass roll-off that discounts very low frequencies. It then mean-squares each channel, sums them with fixed weights and converts to a logarithmic value. Gating removes silence from the average, using an absolute gate at -70 LUFS and a relative gate 10 LU below the ungated mean, so pauses between sentences do not drag a spoken-word programme's integrated reading downward.
What is the difference between LUFS and dBFS peak or RMS metering?
A dBFS peak meter reports the highest sample value and says nothing about perceived level; a bright, heavily limited track and a dull one can both peak at -1 dBFS yet sound very different. RMS averages energy but applies no frequency weighting or gating. LUFS applies K-weighting so the measure tracks hearing, and gating so silence is excluded. That is why gain here is computed from LUFS while true peak is checked separately: they constrain different things.
When should I read momentary, short-term, or integrated loudness?
Momentary uses a 400 ms window and short-term a 3 s window, both ungated; integrated runs over the whole programme with gating applied. Integrated is the number to enter as current loudness, because it is what platforms compare against their target. Momentary and short-term are for spotting problems inside the episode, such as one guest sitting several LU below the host, which shows up as an excessive loudness range rather than a wrong integrated value.
Should I apply a true-peak limiter or accept the quieter safe gain?
When the required gain would push true peak past -1.0 dBTP, the calculator reduces the gain and reports a quieter achievable loudness. A limiter lets you reach the full target instead, by catching only the few peaks that would cross the ceiling. For speech that usually means shaving occasional plosives and laughs, which is inaudible. Accept the quieter result when the peaks are musical or frequent enough that limiting them would audibly flatten the programme.
Why does the same recording measure differently in mono and stereo?
BS.1770 sums the weighted mean square of each channel, so loudness depends on how many channels carry the signal. A mono file duplicated to left and right on playback delivers roughly 3 dB more energy than the single-channel file measured on its own, and reads correspondingly louder. Decide whether you are metering the delivered stereo file or the mono stem, meter the version listeners actually receive, and keep that choice consistent across episodes.
References
Background & Theory
History
Reviewed for accuracy by Daniel Agrici, Founder & Lead Developer ยท Editorial policy
Related Calculators
๐งฎExam Score Normalizer Curving
Calculate exam score normalizer curving with inputs, formulas, and instant results.
๐งฎColor Palette Balance AI
Calculate color palette balance ai with inputs, formulas, and instant results.
๐งฎEV Route Charge Planner Range AI
Calculate ev route charge planner range ai with inputs, formulas, and instant results.
๐งฎWork Break Pomodoro Planner AI
Calculate work break pomodoro planner ai with inputs, formulas, and instant results.
๐งฎ3D Print Time Support Estimator
Calculate 3d print time support estimator with inputs, formulas, and instant results.
๐งฎA B Test Significance Power Analyzer
Calculate a b test significance power analyzer with inputs, formulas, and instant results.
๐งฎAccessibility Contrast Optimizer WCAG
Calculate accessibility contrast optimizer wcag with inputs, formulas, and instant results.
๐งฎAd Spend Allocator Multi Channel ROAS
Calculate ad spend allocator multi channel roas with inputs, formulas, and instant results.