How Much Headroom Do You Need Before Mastering? The -6 dB Myth, Explained (2026)

Short answer: no, you do not need to leave 6 dB of headroom before mastering. In a modern digital workflow the only level requirement that matters is that your mix does not clip. Export with true peaks at or below -1 dBTP and leave the mix-bus limiter off, and anything from about -12 dBTP up to -1 dBTP is equally workable, because the first thing any mastering process does is change the gain, and digital gain costs nothing. The -6 dB rule is not dangerous, it is just arbitrary: leaving exactly 6 dB does not make your master better, it only means you handed over a quieter file.

The advice survives because it is a simple instruction that produces an acceptable outcome. But it points at the wrong variable. What actually ruins a mix before mastering is not its peak level, it is damage that has already been printed into the file: clipped waveforms, and dynamics crushed by a limiter you left on the master bus. Neither is fixed by turning the fader down.

Where the -6 dB rule came from

The number is a fossil of analog practice. On an analog console the nominal operating level sits well below the point where the electronics distort, and that gap, typically somewhere around 18 to 20 dB, is real headroom that you genuinely can use up. Engineers trained on that gear learned to keep programme peaks a comfortable distance under the ceiling, because on analog the ceiling is soft, gradual, and easy to wander into.

Early digital reinforced the habit for different reasons. Sixteen-bit fixed-point recording had a much less forgiving noise floor, converters were more variable, and a hard digital ceiling punishes overshoot with instant, ugly distortion rather than gentle saturation. In that environment, telling people to stay well clear of 0 dBFS was sound advice.

The specific figure of 6 dB mostly comes from mastering houses writing submission guidelines. They were receiving mixes that had already been limited to within an inch of their lives, leaving nothing to work with. A precise, unambiguous instruction like leave 6 dB of headroom reliably produced un-squashed files from clients who would have ignored a paragraph about dynamics. It worked as a piece of client management. It was never a claim about what the mathematics requires.

Why the number is arbitrary now

Your mix is almost certainly being exported as 24-bit or 32-bit float, and your DAW is mixing internally in floating point. That changes the calculus completely.

• 24-bit gives you roughly 144 dB of theoretical dynamic range. The noise floor of the format is far below the noise floor of your room, your microphones, and your listeners' playback. Spending 6 dB of it on ceremony costs you nothing measurable, but it also buys you nothing.
• 32-bit float files cannot clip in the file itself. Values above 0 dBFS are stored and recovered intact, so a float export that reads +2 dBFS can simply be turned down later with no loss. Clipping happens at fixed-point conversion and at the converter, not in the float file.
• Gain is the cheapest operation in the chain. Turning a quiet mix up, or a hot one down, is a multiplication. It does not degrade the audio, add noise you can hear, or cost the mastering engineer anything but a moment.

So the difference between a mix peaking at -6 dBTP and one peaking at -2 dBTP is, in practice, nothing at all. Both get normalised to a working level before anything else happens.

What actually matters instead

Three things determine whether a mix is ready to be mastered, and none of them is the peak number on its own.

1. Nothing is clipped, including inter-sample peaks

Sample peak is the highest value in the file. True peak is the highest value the waveform actually reaches between samples, once it is reconstructed on playback or re-encoded to a lossy format. The two are not the same, and true peak is the one that bites: a file that reads exactly 0.0 dBFS on a sample-peak meter can overshoot by a decibel or more after MP3 or AAC encoding, which is where the crackle on streaming platforms comes from.

This is the whole reason -1 dBTP exists as a target. It is not superstition, it is a margin sized to absorb inter-sample overshoot and codec error. It is also, notably, one decibel, not six.

2. The dynamics are still there

This is the irreversible one, and it is what the old rule was really protecting. If you flatten your mix with a limiter on the master bus, the transients are gone from the file. No amount of headroom underneath that limiter puts them back. You can hand over a mix peaking at a dutiful -6 dBTP that has already been crushed to a 4 dB crest factor, and it will be far harder to master than a lively mix peaking at -1 dBTP.

Take the limiter off. Keep the compression that is part of the sound of the record, on individual tracks or buses, because that is a creative decision and not a level problem. What comes off is the thing whose only job was making the mix louder.

3. Level-dependent processing is fed sensibly

Here is the legitimate kernel inside gain-staging advice. Analog emulations, saturators, tape models, and compressors with fixed or partly fixed thresholds behave differently depending on how hard you drive them, and many are calibrated around a nominal level in the region of -18 dBFS. Feeding them a signal 15 dB hotter than they expect changes their character, sometimes badly.

But note where this applies: inside your mix, at each plugin, while you are working. It is an argument about internal gain staging, not about the peak level of the file you export at the end. The two questions get conflated constantly, and that conflation is most of why the -6 dB rule still sounds technical.

What to actually export

1. WAV or AIFF, 24-bit or 32-bit float. Never 16-bit for something that will be processed further. If your DAW offers 32-bit float and the destination accepts it, use it.
2. The session sample rate, unchanged. Do not resample on the way out. Sample-rate conversion is a step best done once, at the end, by the mastering stage.
3. True peaks at or below -1 dBTP. Check on a true-peak meter, not a sample-peak meter. If you are exporting 32-bit float this matters less, but it is a good habit and it costs nothing.
4. Mix-bus limiter off, mix-bus clipper off. If you have been mixing into a limiter and the mix genuinely depends on it, say so explicitly rather than quietly printing it.
5. No dither. Dither belongs at the final reduction to a lower bit depth. Applying it to an intermediate file just adds noise that later stages will process.
6. Full length, with tails intact. Let reverbs and delays ring out. Do not print a hard fade that a mastering stage might want to place differently.

When leaving real headroom does matter

The rule is not universally wrong, it is context-dependent, and the contexts where it earns its keep are narrower than its popularity suggests.

• Hybrid and analog chains: if the master is going out through converters into outboard gear, input levels are a genuine constraint and the engineer will have a specific number they want. Ask them.
• Heavily calibrated analog emulation: chains built around plugins expecting a nominal -18 dBFS operating level do want to be fed near that level.
• A mastering engineer with written specs: if a human has told you what they want, their number beats a general rule every time, including this article. Submission specs exist to make their workflow predictable.
• Automated services with undocumented behaviour: some automated mastering tools respond differently to different input levels. If you cannot find documentation, a moderate export level around -3 to -6 dBTP is a reasonable hedge, which is probably the strongest honest case for the old rule.

The mistake that actually costs you

The most common real failure is not too little headroom, it is trying to create headroom after the fact. A mix that clipped somewhere upstream does not become unclipped when you pull the master fader down. The waveform is already flat-topped and the distortion is already printed; lowering the level just makes the distortion quieter. If a meter tells you the mix clipped, the fix is upstream, at whichever channel or bus overloaded, not on the output.

The second most common failure is assuming headroom buys loudness. It does not. Final loudness is set at the mastering stage, and streaming platforms normalise playback anyway, so a master pushed 3 dB louder mostly arrives at the listener turned back down, minus the dynamics you spent to get there.

If loudness targets are the actual question behind your headroom question, that is a different topic and we wrote it up separately: LUFS targets for Spotify, Apple Music and YouTube covers what each platform normalises to and what that means for how hard you should push.

Frequently asked questions

Should I leave 6 dB of headroom before mastering?

You do not need to. Aim for true peaks at or below -1 dBTP with no limiter on the mix bus. Anything in the range of roughly -12 to -1 dBTP works equally well, because the level gets set at the mastering stage anyway. Follow a specific number only when a mastering engineer or service has actually asked for one.

What dBFS should I export my mix at?

Export 24-bit or 32-bit float at the session sample rate, with true peaks at or below -1 dBTP. The exact peak value below that ceiling is not important. What matters far more is that the file is unclipped and unlimited.

Is -3 dB of headroom enough?

Yes. So is -1 dB, and so is -10 dB. Any of these give a mastering stage everything it needs. The number only becomes meaningful if you are feeding analog gear or a chain calibrated to a specific operating level.

Does more headroom make my master louder?

No. Headroom in the mix has no effect on achievable master loudness. Loudness is limited by how much dynamic range you are willing to give up at the mastering stage, and by platform normalisation on playback, not by where your mix peaked.

Should I turn off my mix-bus limiter before mastering?

Yes, in almost every case. A limiter on the mix bus removes transients permanently, and that is the single hardest thing for a mastering stage to work around. If the mix genuinely relies on mix-bus compression for its character, keep that but back it off, and flag it.

What is the difference between sample peak and true peak?

Sample peak is the largest stored sample value. True peak estimates the actual peak of the reconstructed analog waveform between samples, which can be higher. Lossy encoding raises it further. This is why true peak targets sit below 0 dBFS: the margin absorbs overshoot that a sample-peak meter never shows you.

Stop guessing at your headroom and measure it

Every number in this article is measurable, and guessing at them is the actual problem. Upload a mix to Mozonic and you get its sample peak, its true peak in dBTP, its integrated loudness in LUFS, its dynamic range and crest factor, and its stereo width, along with an overall score and a plain-language list of what is standing between the track and release-ready. If the mix really is short of headroom, or has been limited harder than you realised, it gets flagged explicitly rather than left for you to infer.

Five analyses a month are free and no card is required. It takes about a minute, and it replaces an argument about a rule of thumb with a number you can act on.