Volume Normalisation Test

Click Play Clip A (Loud) and Play Clip B (Quiet) and the Volume Normalisation Test plays two clips at a fixed, known 20dB level relationship so you can judge whether that gap still sounds clearly audible or has been flattened. Report what you heard — B was clearly quieter than A, or they sounded about the same — and a flattened gap means something in your chain, such as Windows loudness equalisation, a browser extension, or your Bluetooth codec, is silently compressing dynamics without asking you. The free bass test gives you a clear answer instead of guessing.

Run a volume normalisation test and the number it hands back — usually somewhere between −8 and −23 LUFS — tells you more about how your track will actually sound to listeners than any peak meter ever could. That single reading predicts whether Spotify, YouTube, or Apple Music will turn your file down before anyone hears it, and by how much. Instead of guessing at levels, you get a concrete loudness target to master toward, so the mix you spent hours balancing survives the trip to every platform intact.

What Your Volume Normalisation Test Results Actually Mean

A loudness report like this doesn't just spit out one number — it measures your file several different ways at once, and each measurement answers a different question about how your audio will behave once it leaves your speakers. Before you can act on the results, it helps to know what each figure is actually telling you.

What LUFS, dBFS, and True Peak Actually Measure

Three figures show up in almost every loudness report, and they are not interchangeable. dBFS is a purely technical value — the momentary level of a signal relative to digital full scale. LUFS measures something different: how loud a signal is perceived to be over its entire duration, weighted the way human hearing responds to different frequencies.

LUFS (Loudness Units Full Scale)

The industry-standard unit for perceived loudness, used by every major music streaming and video platform to decide how much to turn your file down (or leave it alone).

dBFS (Decibels Full Scale)

A raw signal-level reading. Two files can share the same dBFS peak and still sound completely different in loudness — that gap is exactly what LUFS is built to capture.

True Peak

The highest actual peak level your file will reach after digital-to-analog reconstruction, including inter-sample peaks a standard meter can miss. Exceeding it causes clipping on playback even when your meters looked clean in the editor.

Loudness Range

A measure of dynamics — the spread between the quietest and loudest passages in the file. A narrow range signals a heavily compressed, brickwalled master; a wide one signals a dynamic mix.

The formal method behind the LUFS figure comes from the ITU-R BS.1770 loudness recommendation¹, which applies K-weighting to each channel before gating out silence and averaging:

where \(\overline{z_i}\) is the mean square signal level of channel i and \(G_i\) is that channel's weighting. You don't need to run this by hand — every loudness analyzer does it for you — but it explains why a loud, bass-heavy mix can measure quieter in LUFS than a brighter one at the same peak level.

Reading Your Loudness Penalty Score

If your report includes a loudness penalty figure, it's telling you how many dB a given platform will pull your file down by. A loudness penalty of −2.4 on YouTube means your song plays back 2.4 dB quieter than you exported it.

That's not a defect to panic over — it's informational. If the turned-down version still sounds good, there's nothing left to do.

How Streaming Platforms Handle Loudness Normalization

Once your file leaves your hands, most destinations apply their own loudness normalization pass automatically. Understanding each platform's target loudness lets you predict the outcome instead of being surprised by it. The check whether your stereo and polarity is working properly gives you a clear answer instead of guessing.

Music Streaming Targets by Platform

The table below summarizes what a handful of major music streaming and podcast platforms currently normalize toward. Values are approximate and platforms do update them over time.

Podcast, Broadcast, and DJ Pool Targets

Music isn't the only content type with a loudness ceiling. Podcast platforms and broadcast delivery apply their own rules, and they're often stricter than what music streaming platforms use.

Audiobook and spoken-word delivery commonly targets −18 LUFS, while television and radio broadcast delivery under EBU R128 sits around −23 LUFS — quiet enough that a file mastered for Spotify will sound noticeably hot if you submit it straight to a broadcaster. DJ pools and vinyl pressings, by contrast, apply no automatic normalization at all, which is part of why club masters still run louder than anything built for streaming platforms.

From Loudness Penalty Analyzer Score to a Cleaner Master

A loudness penalty analyzer only tells you where you stand — it doesn't fix anything by itself. Once you know your gap to the target, the next step happens in your mastering chain, not in the meter. In music production, a good loudness penalty score isn't the finish line, it's a checkpoint before mastering.

Compression, Saturation, and EQ: How Mastering Engineers Manage Loudness

Reaching a target loudness without crushing your mix flat comes down to a handful of well-worn mastering techniques, usually applied in this order:

1. Set a target loudness that matches the destination platform before you start processing
2. Apply gentle multiband compression to control dynamics without flattening transients
3. Use saturation to add perceived loudness and harmonic density without raising true peak
4. Recheck true peak and loudness range, then export once the numbers hold

Saturation in particular is doing a lot of the work here: it makes a mix feel louder and denser to the ear without pushing the true peak any higher, which is exactly the trade-off a target-loudness ceiling forces on you. A single stage of compression rarely gets there cleanly — most engineers stage two or three lighter moves rather than one heavy one, since aggressive EQ or compression on a single band tends to introduce audible artifacts before it meaningfully changes the LUFS reading.

Why True Peak and Dynamic Range Still Matter

Chasing a loud LUFS number at the cost of dynamics is an old habit. Some releases from the peak of the loudness war, like Metallica's Death Magnetic, pushed dynamic range down to the point where critics and fans both noticed the fatigue.

Modern references sit all over the map deliberately: Skrillex's Bangarang and Travis Scott's SICKO MODE both master in the −7 to −8 LUFS range for club and download impact, while plenty of indie and acoustic records sit ten LUFS quieter by choice, preserving far more dynamics. Neither approach is wrong — the point of a check like this is to tell you where your file actually lands, not to hand you a single correct answer.

True peak matters here because a mix can measure a healthy loudness in LUFS while still clipping on playback if inter-sample peaks weren't checked. Keeping true peak at or below −1 dBTP gives lossy encoders (the AAC and MP3 conversions almost every platform performs) enough headroom that the encode itself doesn't introduce distortion the original file never had.

Confirming the Results With a Loudness Analyzer and Real Playback Checks

Numbers from a loudness analyzer are only half the picture. The other half is how the file actually sounds once it leaves a pair of studio monitors and hits the real-world systems your listeners use.

Car Check and Sound Check: Testing Across Real Playback Systems

A mix that sounds full on flat studio monitors can turn into something unrecognizable on a phone speaker or a car stereo. A car check or sound check pass — previewing your master through speaker simulation for car systems, laptop speakers, and headphones — catches problems a loudness meter alone never will, since every one of those systems colors frequency response differently: car stereos boost bass, phone speakers cut nearly everything below 200 Hz, and laptop speakers emphasize the midrange. Testing across all of them, not just your reference headphones, is what separates a mix that works everywhere from one that only works in the room you mixed it in.

Exporting the Right Audio File Format

Once your loudness numbers and playback checks both hold up, export. Most tools let you drag and drop the file straight back in afterward to confirm the fix actually took hold before you upload anywhere.

• MP3 — the smallest audio file size, still the safest default for most upload forms
• WAV — uncompressed and lossless, the right choice when a platform re-encodes on its end anyway
• AAC — better quality per kilobit than MP3, and what most streaming platforms transcode to internally
• FLAC — lossless and compressed, useful for archiving your final master

Whichever format you land on, re-run the volume normalisation test on the exported file, not just the project file in your DAW — encoding can shift true peak by a fraction of a dB, and that's the last check before the file is genuinely done.

None of this replaces judgment, and a good loudness reading is a means to an end, not the goal itself. The same discipline underpins audio engineering and sound design more broadly — whether you're mixing and mastering a full record, editing a podcast for podcasting distribution, or handling routine audio editing on a batch of files. Every one of those workflows in digital audio ultimately answers to the same question: does the finished file hold its sound quality wherever someone actually plays it?

¹ ITU-R BS.1770, the loudness measurement recommendation nearly every streaming platform's normalization is built on.