How to Normalize Audio for Spotify, YouTube, and Apple Music
You spend hours mixing and mastering a track. It sounds great in your DAW. You upload it to Spotify, hit play, and... it sounds quieter than everything else in the playlist. Or worse, it sounds squashed and lifeless compared to the track before it.
The problem is loudness normalization. Every major streaming platform automatically adjusts the volume of your audio to match a target loudness level. If you don't prepare your audio for this, the platform does it for you — and the result is often not what you intended.
The good news: once you understand how it works, it takes about 30 seconds to get it right. This guide covers everything you need to know, including a free tool that does the normalization for you right in your browser.
What is loudness normalization?
Loudness normalization is the process of adjusting the overall volume of an audio file so it matches a specific target level. But it's not just about turning the volume knob up or down — it's about measuring perceived loudness, which is how loud something actually sounds to the human ear.
The measurement standard used by streaming platforms is called LUFS — Loudness Units Full Scale. Unlike simple peak levels (which just measure the loudest single sample) or RMS (which measures average signal level), LUFS uses something called K-weighting. This is a filter curve that accounts for the fact that human ears are more sensitive to certain frequencies than others. We hear midrange frequencies louder than bass and extreme highs, and K-weighting adjusts the measurement accordingly.
LUFS is based on the international standard ITU-R BS.1770, adopted by broadcast and streaming industries worldwide. When Spotify says your track should be at -14 LUFS, they mean the integrated (full-track average) loudness should measure -14 LUFS according to this standard.
What LUFS target should you use?
Each streaming platform has its own loudness target. Here are the current standards:
| Platform | Target LUFS | True Peak |
|---|---|---|
| Spotify | -14 LUFS | -1 dBTP |
| YouTube | -14 LUFS | -1 dBTP |
| Apple Music / iTunes | -16 LUFS | -1 dBTP |
| Amazon Music | -14 LUFS | -2 dBTP |
| Tidal | -14 LUFS | -1 dBTP |
| Podcasts (Apple/Spotify) | -16 to -19 LUFS | -1 dBTP |
The key thing to understand: if your track is louder than the target, the platform turns it down. Spotify, YouTube, Apple Music — all of them will reduce the volume of your audio to match their target. There's no way to be "louder than everyone else" on these platforms.
If your track is quieter than the target, the behavior varies. Spotify will turn it up (they call this "normalization" in their settings). YouTube generally does not — your quiet track stays quiet. Apple Music uses Sound Check, which can boost quieter tracks. This inconsistency is another reason to normalize yourself: you control the result.
What happens if you don't normalize?
Let's look at three common scenarios to understand why this matters:
Scenario 1: Your track is too loud
Say you have a modern pop master that measures -8 LUFS. That's typical for current commercial pop — heavily compressed, pushed loud. On Spotify (target: -14 LUFS), the platform turns your track down by 6 dB. You lose the loudness advantage you were trying to achieve, but you keep all the downsides of heavy compression — reduced dynamic range, a squashed, fatiguing sound. The track just sounds flat and lifeless compared to music that was mastered with streaming in mind.
Scenario 2: Your track is too quiet
Your acoustic recording sits at -20 LUFS. On Spotify, it gets turned up by 6 dB — great, it matches the playlist volume. But on YouTube, it stays at -20 LUFS while other videos play at -14 LUFS. Your video sounds noticeably quieter, and viewers reach for the volume knob (or just click away).
Scenario 3: Inconsistent album
You release an album where the ballad sits at -18 LUFS and the rock tracks are at -9 LUFS. On Spotify, each track gets individually normalized to -14 LUFS. That means the ballad gets boosted and the rock tracks get turned down. The dynamic contrast you intended between the quiet and loud songs? Gone. Each track ends up at roughly the same loudness.
How to normalize audio (step by step)
Here's the simplest way to get your audio properly normalized for any streaming platform using SoniqTools Volume & Loudness Normalizer:
- Open the SoniqTools Normalizer in your browser. No account needed, no software to install.
- Drop your audio file onto the page (or click to browse). It accepts WAV, FLAC, MP3, AAC, OGG, and more.
- Check the analysis results. The tool instantly measures your file's current integrated LUFS, peak level, true peak, and dynamic range. This tells you where your audio sits right now.
- Select a platform preset — Spotify, YouTube, Apple Music — or enter a custom LUFS target. The preset automatically sets both the LUFS target and the true peak ceiling for that platform.
- Enable the Peak Limiter if your audio needs gain applied. When the tool increases volume to reach the target, peaks can exceed 0 dBFS. The limiter catches those peaks and prevents clipping.
- Click "Apply Changes." The normalization happens entirely in your browser — your audio never leaves your computer.
- Compare the result. Use the built-in preview players to hear the original and processed versions side by side. Check the new LUFS reading to confirm it matches your target.
- Download your file. The output automatically matches your source format — drop in a WAV, get a WAV back.
That's it. The whole process takes under a minute, and you get a file that's ready for upload to any streaming platform.
Normalize your audio right now
Drop your file into the SoniqTools Normalizer. See your LUFS, pick a platform target, and download the result. Free, private, browser-based.
Open the NormalizerPeak normalization vs LUFS normalization
These are two fundamentally different things, and confusing them is one of the most common mistakes in audio preparation.
Peak normalization adjusts the volume so the loudest single sample in your file hits a specific level (e.g., -1 dBFS). It only looks at the maximum peak — it doesn't care how loud the track sounds overall. A whisper with one loud click and a wall-of-sound master could both be peak-normalized to -1 dBFS, but they'd sound completely different in terms of loudness.
LUFS normalization adjusts the volume so the perceived overall loudness matches a specific target. It measures the entire track (integrated LUFS) and calculates the gain change needed to reach the target. Two very different-sounding tracks both normalized to -14 LUFS will sound roughly equally loud to a listener, even if their peaks are completely different.
Here's why this distinction matters: a heavily compressed pop track and a dynamic classical recording can have the same peak level but wildly different LUFS readings. The pop track might measure -8 LUFS with peaks at -1 dBFS. The classical piece might measure -22 LUFS with peaks at -1 dBFS. Same peak, 14 LUFS of difference in perceived loudness. Peak normalization wouldn't change either of them. LUFS normalization would bring them both to the same perceived loudness.
Streaming platforms use LUFS normalization. This is the standard. Peak normalization is still useful in specific contexts (gain staging during mixing, for example), but for preparing audio for streaming, LUFS is what matters.
What about true peak?
You'll notice every platform in the table above specifies a true peak limit alongside the LUFS target. This is usually -1 dBTP (decibels true peak) or -2 dBTP. But what does "true peak" mean, and why is it different from regular peak?
When digital audio is played back, the digital-to-analog converter (DAC) reconstructs a continuous waveform from the discrete samples stored in your file. The thing is, the reconstructed waveform can peak higher between samples than any individual sample value. This is called an inter-sample peak.
A file with regular peaks at -0.5 dBFS might actually have inter-sample peaks hitting +0.8 dBFS when reconstructed. That causes clipping in the DAC, which produces audible distortion — clicks, harshness, a "crunchy" quality on loud transients. Most listeners won't consciously identify it, but it degrades the listening experience.
True peak measurement uses oversampling (typically 4x) to estimate these inter-sample peaks. When platforms require true peak below -1 dBTP, they're ensuring your audio won't clip during playback on any device.
The SoniqTools Normalizer measures true peak automatically and includes a peak limiter that catches inter-sample peaks when applying gain. So you don't need a separate tool or extra step — it's handled in the same workflow.
Frequently asked questions
Will normalization change my audio quality?
No. LUFS normalization is a simple gain adjustment — it multiplies every sample by the same value. When working with floating-point audio (which SoniqTools uses internally), this operation is mathematically lossless. No EQ, no compression, no processing artifacts. It's the same audio, just louder or quieter. The only scenario where quality could be affected is if you're boosting a very quiet file and the peak limiter engages — but the limiter is transparent and only catches the highest peaks.
Should I normalize before or after mastering?
After. Mastering sets your tone, dynamics, EQ balance, and stereo image. Loudness normalization is the final step — it just adjusts the overall volume to match your target platform. Think of mastering as shaping the sound, and normalization as setting the volume. If you normalize before mastering, the mastering engineer will just change the level anyway.
Can I normalize a whole album to the same loudness?
Yes. Use batch mode to process multiple tracks at once. Each track gets normalized independently to the same LUFS target. This ensures consistent loudness across your release, which is exactly what streaming platforms expect. Some mastering engineers use "album normalization" (adjusting all tracks by the same gain offset to preserve relative loudness differences), but for streaming, per-track normalization is the standard approach.
Should I normalize differently for each platform?
In practice, -14 LUFS with -1 dBTP true peak is a safe target that works well across all platforms. Spotify, YouTube, Tidal, and Amazon Music all target -14 LUFS. Apple Music targets -16 LUFS, but a -14 LUFS file will only be turned down by 2 dB on Apple — a negligible difference that preserves your dynamics. If you're primarily targeting Apple Music or podcasting, you might want to aim for -16 LUFS instead. But for most music releases, -14 LUFS is the universal sweet spot.
Get your audio streaming-ready
Loudness normalization isn't complicated once you understand the basics. Every streaming platform has a target, and your job is to hit it before uploading so you stay in control of how your music sounds.
The fastest way to do this: open the SoniqTools Normalizer, drop your file, select your platform, and download the result. It measures your LUFS, applies the right gain, handles true peak limiting, and gives you a file that's ready for any streaming service — all without leaving your browser.
Ready to normalize your audio?
The SoniqTools Normalizer measures your LUFS, matches any platform target, and handles true peak limiting. Free, private, and entirely browser-based — no uploads, no accounts.
Open the Normalizer