How Loud Should Your Master Be? Stop Guessing and Benchmark It
You bounce the master. You drop it into a playlist next to the records that made you want to produce. And your track sounds small.
Not bad. Small. A little quieter, a little thinner, a little less dense in the chorus. So you push the limiter another dB and bounce again. Now it's loud, but the drums stopped hitting. Somewhere between those two bounces is the master you wanted, and you're hunting for it by feel.
Stop guessing. Measure it.
A LUFS Number Is Not an Answer
Every meter can tell you your track sits at -8.3 LUFS. None of them can tell you whether that's competitive. Competitive against what? Against the tracks your listeners hear ten seconds before and ten seconds after yours. That's the only comparison that counts.
Search "how loud should my master be" and you'll drown in the same recycled advice: master to -14 LUFS because Spotify normalizes to -14. It sounds logical. It's wrong, and we'll get to why. But the deeper problem is that no single number answers the question. Two masters at the exact same LUFS can sound worlds apart, because one is denser, wider, and better balanced than the other.
You don't need a number. You need a benchmark.
Drop a Track, Get a Score
That's what we built. The BeatSync Loudness Benchmark is a free tool that measures your master and compares it against commercially released, competitively mastered tracks, all measured the exact same way.
Drag in a WAV, AIFF or FLAC (MP3 and AAC work too, but they read hotter on true peak). The analysis runs in your browser. Your audio never leaves your machine; only the measured numbers reach the benchmark. A few seconds later you get a competitive score and five gauges:
| Gauge | What it measures | What it tells you |
|---|---|---|
| Loudness | LUFS of your loudest 20% | Whether your choruses hang with the benchmark |
| Punch | PSR (peak to short-term ratio) | How hard you're limiting compared to the pros |
| Width | Side/mid in the loudest sections | Too narrow, too wide, or right in range |
| Tone | Spectral tilt, bright vs dark | Whether your overall balance translates |
| Low end | Sub 20-60 Hz share of energy | If your sub weight matches release-ready masters |
Each gauge shows the benchmark average, the spread around it, and where your track lands. Green inside the range, red below, amber above. No decoding required.
Want to see one before you try it? Here's a full sample report from a real run: a 98 score, an inter-sample peak warning, and a bass band running 2.2 dB heavy.
Choruses Are Where You Compete
Here's the part most loudness meters miss completely.
Streaming platforms normalize on your whole track. Listeners don't. Nobody skips your song because the intro is quiet. They compare your chorus against the last chorus they heard. So the benchmark measures both: the loudest 20% of your track (effectively the choruses and drops) and the integrated whole.
That split tells you where a gap actually lives. Choruses matching while the whole track lags behind? Your mastering is fine. The gap is arrangement: long quiet sections dragging the integrated number down. That's an automation fix, not another limiter.
About That -14 LUFS Myth
Spotify pulls a -8 LUFS master down by 6 dB. It leaves a -14 LUFS master alone. Both play at the same volume. Case closed for -14, right?
Wrong. Normalization changes level, not density. The -8 master was limited, saturated, and shaped to feel dense, and after the 6 dB pulldown all that density is still there. The -14 master plays at the same loudness and feels polite next to it. This is why commercial masters still land around -8 to -9 LUFS in the normalization era, and why the benchmark compares density and tone, not just level.
The report shows this directly: a platform table with the exact gain Spotify, Apple Music, YouTube and the rest apply to your track versus the benchmark average.
Findings You Can Act On, in Order
A score without a fix list is a grade, not a tool. Every report ends with findings sorted by severity: critical (costs you level or translation, fix first), warning (a trade-off that needs a decision), info (a difference that may be intentional), and good (confirmed in the benchmark range).
And the fixes follow the order that actually works:
- Get true peak under the ceiling: -1 dBTP for lossy platforms, -0.3 dBTP if you accept some overs.
- Mono the low end below 100-150 Hz, high-pass below 30-40 Hz. This is where your headroom is hiding.
- Fix tonal balance per the band findings before you push level.
- Add density with clipping on the drums and saturation before the limiter. Limiter last.
- Automate section levels if the whole-track gap is arrangement.
Then the loop is simple. Drop the track. Fix the top finding. Re-export. Drop it again. Watch the score move.
When the Fix List Points at Mastering
Some findings you fix in the mix. Others are exactly what a mastering stage is for: the ceiling, the density, the final tonal balance. That's the moment to upload your track to BeatSync Mastering, flip between original and master, then run the result through the benchmark again. AAC masters are free during launch, so testing the difference costs you nothing.
And if the report says the problem starts before mastering, start here instead: how to prepare your mix for mastering, or the sixty-second do's and don'ts checklist.
Your track gets compared every time somebody presses play. Now you can run the comparison first.
