Master Too Quiet? Why and How to Fix It

Updated August 2026 · by Loopin

A master that’s too quiet almost always means it was never brought up to a streaming loudness target — too much headroom was left, or the limiter is barely doing anything. The fix is straightforward: use a true-peak limiter with a −1 dBTP ceiling and push the input until you reach about −14 LUFS integrated. You can do exactly that, free, in Loopin’s browser mastering.

Why your master sounds too quiet

Quiet masters come from one of a few places, and none of them are mysterious. Most of the time the track simply wasn’t brought up to a loudness target, so it sits well below where streaming tracks land. If nothing in your chain is actively raising the level toward a target, the master stays at whatever level the mix bounced out at — which is usually far too low.

The other common cause is a limiter that’s in the chain but barely working — the input never pushes hard enough to raise the average level. The peaks might be controlled, but the perceived loudness stays low. A limiter only adds loudness when you drive signal into it; parked with the input untouched, it just sits there as a safety net doing nothing for level.

No loudness target: the master was never brought up to about −14 LUFS
Too much headroom left: peaks sit far below the ceiling, so nothing raises the average
Limiter barely working: the input isn’t pushed enough to add gain
Judging by peaks, not loudness: a −1 dBFS peak can still be a very quiet integrated level

Loudness is an average, not a peak

This is the misunderstanding at the root of most quiet masters. Your peak meter can read close to 0 while the integrated loudness — the full-song average of perceived loudness — is far below where it should be. Peaks tell you about the loudest instants; loudness tells you how the whole song actually feels, and those two numbers can be very far apart.

Streaming platforms normalize by integrated loudness, around −14 LUFS. If your master’s integrated reading is well under that, the platform turns it up, but a track that started too quiet still feels flat and small next to commercial references. A very dynamic mix — big peaks, low average — is the classic case: it looks loud on a peak meter and measures quiet on a loudness meter.

Integrated LUFS: full-song average — this is what platforms measure
True peak (dBTP): the highest inter-sample level — controls clipping, not loudness
A high peak with low LUFS = a dynamic but quiet-feeling master
Aim to move the average up to about −14 LUFS, not just the peaks

The fix: push into a true-peak limiter

Raising loudness the right way means driving level into a true-peak limiter set to a safe ceiling, then letting it catch the peaks while the average comes up. As you feed more signal in, the limiter shaves the tops off the loudest transients and the integrated reading climbs — that’s how a track gets loud without the peaks ever crossing the ceiling. Here are the targets to hit:

True-peak ceiling: −1 dBTP
Integrated loudness goal: about −14 LUFS
Method: increase input into the limiter until the integrated reading reaches target
Restraint: stop at −14 LUFS — louder isn’t the goal, matched loudness is

Fix a too-quiet master step by step

Here’s the fastest reliable path from a quiet bounce to a properly-leveled master:

Bounce your mix to WAV with headroom — peaks near −6 dB and no mix-bus limiter.
Open Loopin’s free mastering tool and drop the file in.
Let the chain drive loudness toward about −14 LUFS integrated with a −1 dBTP true-peak ceiling.
A/B against your original — the master should feel fuller and sit at a normal level, not squashed.
Confirm the true peak lands at −1 dBTP, then download the 16-bit WAV.
Compare it to a commercial reference track in the same genre to sanity-check the level.

Don’t confuse ‘quiet’ with Spotify turning you down

This is a crucial distinction. If you master louder than the streaming reference and then notice your track playing back softer on Spotify, that’s not a quiet master — that’s normalization turning a loud master down.

Spotify plays everything back toward about −14 LUFS. A master hotter than that gets negative gain applied, so it sounds quieter on playback even though the file itself is loud. That’s the opposite problem from a genuinely under-leveled master, and the fix is different: master to −14 LUFS, not louder.

Genuinely too quiet: integrated LUFS is well below −14 — bring it up
Turned down by Spotify: integrated LUFS is above −14 — you were too hot, not too quiet
The cure for the second case is less loudness, aiming at −14 LUFS
Always check your integrated LUFS before deciding which problem you have

Common mistakes

Judging loudness by the peak meter — a −1 dBFS peak can still be a very quiet integrated level.
Leaving the limiter in but not driving it — if the input never pushes, the average never rises.
Chasing loudness past −14 LUFS — that just gets turned down on streaming and bakes in distortion.
Fixing loudness in the mix by turning everything up — loudness targeting belongs on the whole stereo file at the master stage.
Ignoring true peak while raising level — without a −1 dBTP ceiling, louder can mean inter-sample clipping.

Is it a mix problem or a master problem?

Sometimes a ‘quiet’ master is really a mix that can’t get loud — if the mix is dynamically uneven or has one instrument spiking the peaks, the limiter clamps down on that one spike before the average can rise. You end up with the limiter working hard on a single snare hit or vocal peak while the rest of the track stays quiet. That’s a mix-balance issue, not a loudness-target issue.

Mastering acts on the whole stereo file, so it can only do so much with a spiky mix. Tame runaway peaks in the mix first (gentle bus compression, controlling the loudest element), then let the master stage bring the average up cleanly. A more even mix lets the limiter raise everything together instead of chasing one peak. Either way, Loopin’s mastering tool handles the loudness-targeting step for you.

Fix it free

Loopin’s online mastering pushes your track toward about −14 LUFS integrated with a −1 dBTP true-peak ceiling, all in your browser — free, no signup, nothing uploaded, no watermark. Drop in your quiet mix, A/B it against the original, and download a properly-leveled 16-bit WAV in a couple of minutes.

Frequently asked questions

Why is my master too quiet?

Usually it was never brought up to a streaming loudness target, too much headroom was left, or the limiter is barely working. Push the input into a true-peak limiter set to −1 dBTP until your integrated loudness reaches about −14 LUFS.

How loud should my master be?

Aim for about −14 LUFS integrated with a −1 dBTP true-peak ceiling. That matches how streaming platforms normalize, so your track sits at a normal level next to commercial releases without being crushed.

Why does my loud master still sound quiet on Spotify?

That’s different from a quiet master — it’s Spotify normalization turning a loud master down. If your integrated LUFS is above −14, Spotify applies negative gain on playback. The fix is to master to about −14 LUFS, not louder.

Can I just turn up the volume to fix a quiet master?

Raising level without a true-peak limiter risks clipping. The right way is to drive into a limiter with a −1 dBTP ceiling so peaks stay controlled while the integrated loudness rises to about −14 LUFS.

Can I fix a too-quiet master for free?

Yes. Loopin’s free browser mastering drives your track toward about −14 LUFS integrated with a −1 dBTP ceiling, runs entirely in your browser with nothing uploaded, and exports a 16-bit WAV.