· 5 min read
How to Measure LUFS Loudness Range of an Audio File
Heshan Fernando
Co-founder & COO
You’ve mixed a podcast episode, a video’s audio track, or a piece of music, and you’re about to upload it to a platform with a stated loudness target — Spotify, YouTube, a podcast host, a broadcast spec — but peak level (what a standard VU meter or waveform view shows you) isn’t the same measurement those platforms actually use. They normalize based on LUFS (Loudness Units Full Scale), a perceptual loudness measurement, and if your file doesn’t match their target, it either gets turned down automatically (making a carefully mixed track sound quieter and less punchy than intended) or flagged for being too loud.
Peak level and perceived loudness aren’t the same thing — two tracks can have identical peak levels but sound noticeably different in loudness depending on their dynamics and average energy, which is exactly the gap LUFS measurement is designed to close.
What LUFS and loudness range measurement actually involves
Integrated LUFS is a time-weighted average loudness measurement across an entire audio file, using a perceptual model closer to how loudness is actually perceived than a simple peak or RMS measurement. Loudness range (LU) separately measures the spread between quiet and loud passages within the file — a track with a wide loudness range has more dynamic variation between its quietest and loudest moments, while a heavily compressed track has a narrow range. Together, these two numbers are what platform normalization algorithms actually check against their target specs.
Why people get stuck here
- Assuming peak level and loudness are the same thing. A file can peak at the same level as another but measure meaningfully louder or quieter in LUFS, depending on how dense and sustained the audio content is.
- Not knowing the target LUFS for a specific platform. Different platforms and formats (podcasts, streaming music, broadcast) have different conventional loudness targets, and mixing without a target in mind risks the platform’s normalization working against your intended mix.
- Over-compressing to hit a loudness target. Squashing dynamic range to push average loudness up can technically hit a LUFS target while making the track sound fatiguing or lifeless compared to a more dynamic mix.
- Not checking loudness range alongside integrated loudness. A file can be at the right average loudness but still sound inconsistent if its loudness range is unusually wide or narrow for the content type.
What a good loudness meter looks like
Measures integrated loudness the way platforms actually do
Using the same LUFS methodology that streaming and broadcast normalization systems rely on gives you a measurement that actually predicts how your file will be treated on that platform.
Reports loudness range alongside integrated loudness
Seeing both numbers together tells you not just how loud the file is on average, but how much dynamic variation exists within it — useful context a single loudness number doesn’t capture.
Works directly on your file without needing dedicated mixing software
A quick, browser-based check lets you verify loudness before export without opening a full DAW just to confirm a number.
| Content Type | Typical Target | Why |
|---|---|---|
| Streaming music | around -14 LUFS | Matches common platform normalization targets |
| Podcasts | around -16 to -19 LUFS | Consistent, comfortable spoken-word listening level |
| Broadcast | Platform/region-specific standard | Regulatory and platform loudness compliance |
Common mistakes to avoid
- Mixing purely by peak level or by ear without ever checking integrated LUFS against your target platform’s convention.
- Over-compressing a mix specifically to inflate loudness, sacrificing the dynamic range that often makes a mix sound more engaging.
- Assuming one loudness target applies universally across every platform and content type — targets genuinely differ by context.
- Ignoring loudness range entirely and only checking the single integrated loudness number, missing useful information about internal dynamic consistency.
- Re-checking loudness only after final export instead of during the mixing process, when adjustments are still easy to make.
How to do it with Audio Loudness Range Meter
Online Tool Store’s Audio Loudness Range Meter analyzes your file entirely in your browser.
- Open the Audio Loudness Range Meter tool.
- Upload your audio file.
- Review the integrated LUFS measurement and loudness range (LU).
- Compare against your target platform’s typical loudness spec and adjust your mix if needed.
Frequently asked questions
What’s the difference between LUFS and dB?
Decibels (dB) measure raw signal level, while LUFS applies a perceptual weighting model designed to approximate how loud audio actually sounds to human hearing over time — two clips at the same peak dB level can measure at noticeably different LUFS values depending on their content.
Why does my track sound quieter after uploading to a streaming platform?
Most major platforms apply loudness normalization, turning down tracks that exceed their target LUFS level to keep listening volume consistent across different content. If your mix is louder than the platform’s target, it gets turned down automatically, which can make a heavily compressed mix sound flatter than intended.
Is a wider loudness range always better?
Not necessarily — it depends on the content. A film score or dynamic music mix often benefits from a wider loudness range for expressive impact, while a podcast or dialogue-heavy track usually benefits from a narrower, more consistent range for comfortable, fatigue-free listening.
Final thought
Checking LUFS and loudness range before you export tells you how your mix will actually be treated by the platform you’re publishing to — worth doing before upload, not after you notice it sounds different than you intended.