True Peak Is a Constraint, Not a Target

A digital peak meter tells us the level of the samples in a file.

It does not necessarily tell us the highest level the signal can reach when those samples are reconstructed into a continuous waveform.

That difference is the reason true-peak measurement exists.

It is also the source of a surprising amount of confusion.

True peak is sometimes treated as another mastering target: stay below a particular number and the job is done. At the other extreme, true-peak limiting is dismissed as unnecessary because the peaks it detects do not necessarily exist as individual samples in the original file.

I don't find either position particularly useful.

For me, true peak is something to account for. It is a delivery consideration — not a measure of whether a master sounds good, and certainly not a number worth damaging a record to satisfy.

The Peak Between the Samples

Digital PCM audio represents a continuous signal as a sequence of discrete sample values.

A conventional sample-peak meter examines those values and reports the highest one. If the highest stored sample is below 0 dBFS, the meter can truthfully tell us that no individual sample exceeds full scale.

But the samples are not the final analog waveform.

During reconstruction, filtering restores the continuous waveform represented by those samples. Its maximum amplitude can occur between the original sampling instants and can be higher than any individual stored sample.

These reconstructed excursions are commonly called inter-sample peaks.

They are not imaginary peaks invented by a meter.

But neither is a true-peak reading a literal prediction of what every converter, codec, playback device, and analog output stage will produce.

It is a standardized estimate of reconstructed peak level.

That distinction matters.

What a True-Peak Meter Is Actually Doing

A sample-peak meter asks:

How high are the samples?

A true-peak meter asks:

How high might the waveform represented by those samples actually reach?

To answer that second question, true-peak measurement reconstructs the signal at a higher temporal resolution and examines the resulting peaks.

The measurement is commonly expressed in dBTP.

The important point is not simply the oversampling factor used by a particular implementation.

It is that true-peak measurement attempts to expose a condition that ordinary sample-peak metering cannot see.

That condition becomes increasingly relevant as more of a master is pushed toward digital full scale.

Filtering, sample-rate conversion, encoding, decoding and D/A reconstruction can all create conditions where peak behavior differs from what a sample-peak meter showed in the original file.

That is why I don't consider inter-sample overs a purely academic problem.

I've encountered them in masters prepared for streaming.

Measurement Is Not Limiting

This is probably the most important distinction.

True-peak metering measures a condition.

True-peak limiting changes the signal in response to that condition.

Those two things are often discussed as though they are inseparable.

They aren't.

You can monitor true peak and decide that a small excursion does not justify additional processing.

You can leave additional headroom rather than force a limiter to contain every reconstructed peak.

You can also use true-peak limiting when the protection can be achieved transparently.

Turning off true-peak limiting does not make inter-sample peaks disappear.

But detecting one does not automatically mean that it must be eliminated at any cost.

The meter gives us information.

The mastering engineer still has to make the decision.

The Cost of Control

Every limiter changes the waveform when it acts.

That is not a criticism of limiting. It is what a limiter does.

The question is whether the change is useful, acceptable, or audible.

I've heard masters suffer from too much limiting.

Transients can lose definition. Punch can disappear. The upper edge of a kick or snare can become flatter than the music wants it to be.

I don't think that problem belongs uniquely to true-peak limiters.

Any limiting process can be asked to do too much.

And this is where I become cautious about absolute rules.

If eliminating a tiny true-peak over requires audibly damaging the transient that caused it, we have to ask whether we solved the right problem.

But the opposite argument matters too.

If a reconstructed peak can be controlled without audibly changing the master, why would I deliberately leave the risk unaddressed?

For me, the objective isn't simply:

No inter-sample peaks.

It is:

No unnecessary damage while controlling the final output.

Why I Usually Leave Some Room

Earlier in my mastering work, I was comfortable working considerably closer to full scale.

Depending on the project, I might use ceilings around -0.5 dB or even -0.1 dB.

As more of my mastering became focused on streaming delivery, I became more conservative.

For Apple Music delivery in particular, Apple's published guidance has influenced my practice, and I generally leave approximately 1 dB of final true-peak margin rather than pushing every last fraction of a decibel toward full scale.²

That is not because I believe -1 dBTP is a magic number.

It isn't.

It is margin.

The appropriate ceiling still depends on the material, the destination, the desired loudness, and what the processing is doing to the music.

A number should inform the decision, not become the decision.

Headroom Is Not Wasted Space

There is a tendency — particularly with loud masters — to think of anything below full scale as unused territory.

I don't think that is a very productive way to look at it.

Headroom can be protection.

It gives reconstruction, encoding, sample-rate conversion, and playback processes somewhere to go without immediately running into a hard boundary.

Giving up a fraction of a decibel at the ceiling is rarely the thing that determines whether a master feels powerful.

Transient shape, density, spectral balance, dynamics, and perceived loudness matter far more.

The last decimal place on the peak meter is not the record.

True Peak Does Not Tell You Whether a Master Is Good

A true-peak reading tells us something very specific.

It does not tell us whether the record is loud enough.

It does not tell us whether it has punch.

It does not tell us whether the tonal balance is right.

It does not tell us whether the dynamics are appropriate.

It does not tell us whether a limiter is being pushed too hard.

And it certainly does not tell us whether the music feels right.

That narrowness is a strength.

True peak is useful precisely because it answers a narrow technical question.

Problems start when we ask that measurement to become an aesthetic judgment.

Why I Built The Final Word This Way

This question eventually became part of the reason I built The Final Word.

I had delivered masters that produced inter-sample overs.

I wanted true-peak protection that I could trust at the end of a mastering chain without feeling that I had to continually second-guess what was happening above the sample peaks.

But I did not want the solution to simply be more aggressive limiting.

The main limiting stage should do the musical work.

The final protection should stay out of the way.

The Final Word therefore uses a dedicated true-peak ceiling stage after its main limiting path.

During normal processing, that stage analyzes an independent 8× oversampled reconstruction of the output and applies proportional gain reduction when the reconstructed peak would otherwise exceed the set ceiling.

It operates independently of the user-selected main Oversampling setting.

A separate final true-peak measurement then evaluates the signal that actually leaves the plugin.

The goal is not more limiting.

It is to make the last layer of protection as unobtrusive as possible.

That architecture reflects how I think about true peak generally:

• Acknowledge the problem.
• Measure it accurately.
• Control it when necessary.

And do as little damage as possible in the process.

Not a Rule. A Responsibility.

I am cautious about using the word always in mastering.

• Always use true-peak limiting.
• Always leave -1 dBTP.
• Always master to a particular LUFS value.
• Always use a clipper before a limiter.

Rules like these can be useful starting points.

They can also become substitutes for listening.

I value knowing what is happening to a signal beyond the samples themselves.

I've seen inter-sample overs occur in real delivery, so I am not comfortable pretending the issue does not exist.

But I am equally uninterested in sacrificing transient integrity simply to make a meter display a prettier number.

That leaves us with the same responsibility we have everywhere else in mastering:

Understand the measurement.

Understand the consequence.

Then make the decision that serves the record.

True peak is not something to chase.

It is something to account for.