What Is Audio Normalization?
Audio normalization adjusts the volume level of an audio file to meet a target standard. The goal is consistency — ensuring that listeners do not need to constantly adjust their volume when moving between tracks, episodes, or channels. A podcast episode at -8 LUFS followed by one at -24 LUFS creates a jarring experience. A playlist where one track blasts at peak level and the next whispers forces the listener to reach for the volume knob.
There are two fundamentally different approaches to normalization, and confusing them is one of the most common mistakes in audio production.
Peak normalization adjusts the audio so the loudest single sample reaches a target level (typically -1 dBTP or 0 dBFS). This says nothing about perceived loudness — a track with one brief spike at 0 dBFS and everything else at -20 dBFS is "peak normalized" but sounds very quiet.
Loudness normalization adjusts the audio so the integrated (average) loudness reaches a target level, measured in LUFS (Loudness Units Full Scale). This directly corresponds to perceived loudness and is the standard used by every major streaming platform, broadcast network, and podcast distributor.
Understanding Loudness Measurements
LUFS (Loudness Units Full Scale)
LUFS is the industry standard for measuring perceived loudness, defined by ITU-R BS.1770 and EBU R128. It uses a K-weighted frequency curve that models human hearing — we are more sensitive to mid-frequencies (1-4 kHz, where speech and instrument fundamentals live) and less sensitive to very low and very high frequencies.
LUFS measurements come in three time windows:
| Measurement | Window | Use |
|---|---|---|
| Integrated LUFS | Entire program duration | Primary loudness measurement |
| Short-term LUFS | 3-second sliding window | Track consistency analysis |
| Momentary LUFS | 400ms window | Real-time metering |
Integrated LUFS is the number platforms use. When Spotify says -14 LUFS, they mean the integrated loudness of the entire track.
True Peak (dBTP)
True peak measures the highest signal level including inter-sample peaks — signal values that occur between the discrete digital samples. A file can show 0 dBFS on a sample-based meter but actually peak at +1.5 dBTP when reconstructed by the DAC. Exceeding 0 dBTP causes clipping distortion on playback.
Most standards require true peak below -1 dBTP or -2 dBTP to provide headroom for lossy codec encoding (MP3 and AAC encoding can increase peak levels by 1-2 dB).
RMS (Root Mean Square)
RMS is an older averaging method that does not apply frequency weighting. It measures raw signal energy without modeling human perception. While still used in some contexts (analog mastering, technical measurement), LUFS has replaced RMS for loudness management because LUFS better correlates with how humans perceive loudness.
A track with heavy bass content might measure -10 dB RMS but only -14 LUFS because the K-weighting de-emphasizes low frequencies that humans perceive as less loud.
Platform Loudness Standards
| Platform | Target LUFS | True Peak | Normalization Type |
|---|---|---|---|
| Spotify | -14 LUFS | -1 dBTP | Turn down only (default) |
| Apple Music | -16 LUFS | -1 dBTP | Turn up and down |
| YouTube | -14 LUFS | -1 dBTP | Turn down only |
| Amazon Music | -14 LUFS | -2 dBTP | Turn up and down |
| Tidal | -14 LUFS | -1 dBTP | Turn down only |
| Netflix | -27 LUFS (dialogue) | -2 dBTP | Dolby standard |
| Podcast (general) | -16 to -14 LUFS | -1 dBTP | Varies by platform |
| EBU R128 (EU broadcast) | -23 LUFS | -1 dBTP | Regulatory requirement |
| ATSC A/85 (US broadcast) | -24 LKFS | -2 dBTP | FCC-referenced |
What "Turn Down Only" Means
Spotify's default normalization mode only reduces the volume of tracks louder than -14 LUFS. It does not boost quiet tracks. This means a track mastered at -14 LUFS plays at its original level, while a track mastered at -8 LUFS is turned down by 6 dB. The practical implication: mastering louder than -14 LUFS gains you nothing on Spotify — the platform just turns you down, and you have lost dynamic range for no benefit.
Apple Music's Sound Check normalizes in both directions — it will boost a -20 LUFS track to -16 LUFS and reduce a -10 LUFS track to -16 LUFS.
How to Normalize Audio
For Music Distribution
Target: -14 LUFS integrated, -1 dBTP
Master your track to -14 LUFS integrated loudness. This is the sweet spot that plays at intended volume on Spotify, YouTube, and Tidal without being turned down. On Apple Music (-16 LUFS target), you will be turned down by 2 dB — which is negligible.
Do not master louder than -14 LUFS just to be "loud." The loudness wars are over. Platforms normalize everything. A track at -8 LUFS sounds identical to one at -14 LUFS on Spotify — except the -8 LUFS version has crushed dynamics and audible distortion.
For Podcasts
Target: -16 LUFS integrated, -1 dBTP
Podcasts benefit from consistent loudness across episodes and between speakers. Use a compressor to reduce dynamic range (bring loud and quiet parts closer together), then normalize to -16 LUFS. This level works well across podcast platforms (Apple Podcasts, Spotify, Google Podcasts) and provides comfortable listening in noisy environments (cars, public transit).
For podcast format recommendations, see our best audio format for podcasts guide.
For Broadcast
Target: -23 LUFS (EBU R128) or -24 LKFS (ATSC A/85)
Broadcast standards are regulatory requirements, not suggestions. Content delivered outside these specifications will be rejected or automatically processed (often destructively). Use a loudness meter that reports integrated LUFS over the entire program duration, and verify true peak compliance.
For Video and Film
Target: -24 to -27 LUFS for dialogue, -2 dBTP
Film and episodic content uses dialogue normalization — the loudness is measured on the dialogue channel, not the full mix. Music, effects, and ambience are mixed relative to dialogue. This allows wide dynamic range (quiet whispers, loud explosions) while ensuring dialogue is consistently audible.
Quality and Settings Tips
Normalize at the final stage, not during recording. Record with healthy levels (peaking around -12 to -6 dBFS) and normalize during mastering or post-production. Normalizing a recording before editing limits your headroom for processing.
Use a proper loudness meter. Standard VU meters and dBFS peak meters do not show LUFS. Use a dedicated loudness meter plugin (Youlean Loudness Meter is free and excellent) that displays integrated, short-term, and momentary LUFS along with true peak.
Dynamic range matters more than loudness. A track with 10 dB of dynamic range at -14 LUFS sounds better, more musical, and more impactful than a brick-wall-limited track at -14 LUFS with 3 dB of dynamic range. The platforms will normalize loudness; they cannot restore dynamics that you crushed.
Normalize each episode or track individually. Do not apply the same gain adjustment to every file. Each track or episode has different content and different inherent loudness. Measure the integrated LUFS of each file independently, then apply the specific gain adjustment needed to reach your target.
For batch audio processing, our audio converter supports normalization options during format conversion. Convert and normalize in a single step.
Common Issues and Troubleshooting
Audio sounds distorted after normalization. You are boosting a quiet signal too aggressively, pushing peaks above 0 dBTP. Use a limiter after gain adjustment to catch peaks that exceed your true peak ceiling. Set the limiter ceiling to -1 dBTP.
Track sounds quieter than others on the platform. If the platform uses "turn down only" normalization (Spotify), a quiet track stays quiet. You may need to master louder — but with appropriate limiting and dynamic range preservation, not just "turn everything up." Target -14 LUFS exactly for optimal playback on Spotify.
Loudness reads differently in different tools. Verify that all tools are using the same measurement standard (ITU-R BS.1770-4 / EBU R128). Older tools may use BS.1770-1, which gives slightly different readings due to a different gate threshold implementation.
Normalization changed the tone of my audio. Loudness normalization should only change gain (volume) — it should not affect EQ, compression, or tonal character. If the tone changed, the normalization tool may have applied additional processing (automatic EQ, multiband compression). Use a tool that applies pure gain adjustment only.
Podcast levels are inconsistent between speakers. Record each speaker on a separate track, compress each track independently to reduce its dynamic range, then mix to a consistent level before normalizing the final stereo mix.
Conclusion
Loudness normalization to LUFS standards is mandatory for professional audio delivery in 2026. Target -14 LUFS for music distribution, -16 LUFS for podcasts, and -23/-24 LUFS for broadcast. Always check true peak compliance (-1 dBTP minimum). Prioritize dynamic range over loudness — streaming platforms normalize volume, but they cannot restore crushed dynamics.
Ready to process your audio? Try our free audio converter with normalization support — no registration required.



