LUFS, True Peak, and What They Actually Tell You
Two numbers show up on every mastering report and get treated like a pass/fail test more often than they should. LUFS and true peak aren't a target to hit so a track "counts" as properly mastered, they're measurements that tell you specific, limited things, and knowing what they don't tell you matters as much as knowing what they do.
LUFS: loudness, not quality
Integrated LUFS measures perceived loudness across the whole track. Something landing around -14 LUFS-I is common on a lot of contemporary streaming masters, but that's a description of where things often sit, not a rule to chase. A track sitting quieter than that isn't automatically unfinished. A track pushed louder than that isn't automatically more competitive, it's often just more compressed.
Streaming platforms normalize loudness anyway, turning quieter tracks up and louder tracks down toward their own target. Once that happens, the loudness war that used to matter enormously on physical and download releases matters a lot less than people assume. What normalization can't undo is a track that got flattened chasing a number, the dynamics are gone either way, turning the level back down afterward doesn't bring the movement back.
True peak: headroom, not a finish line
True peak measures the highest point the waveform actually reaches, including peaks that happen between samples that a basic peak meter can miss entirely. Most platforms use something close to -1 dBTP as a safety ceiling, and that number exists for a real reason: lossy codecs used in streaming, AAC, Ogg Vorbis, and similar formats, can introduce a small amount of overshoot during transcoding. A file that's technically clean at -1.0 dBTP can come out the other side of a lossy encode slightly hotter than that.
This is why a little extra margin, pulling the ceiling back to -1.5 or -2.0 dBTP, costs nothing audible and removes even that small remaining risk. It's not a fix for anything wrong with your file, it's insurance against a step in the pipeline you don't control.
What these numbers don't tell you
Neither one says anything about whether a track sounds good. A perfectly compliant file at -14 LUFS and -1.2 dBTP can still have a muddy low end, a harsh top end, or artifacts nobody caught. These are safety and consistency checks, not a quality score. Treat them as the floor a finished master needs to clear, not the goal it's aiming for.
The actual goal is still the same as it's always been: a track that sounds right on the systems people will actually hear it on. LUFS and true peak just make sure the technical delivery doesn't get in the way of that.
— Josh Founder, JG BeatsLab
