Peak normalization gain calculator

Enter both levels in dBFS and receive a positive gain for amplification, a negative gain for attenuation, or zero when the audio already meets the target. Targets above 0 dBFS are rejected because they would exceed digital full scale. The calculation is deterministic and works without uploading, decoding, or changing an audio file.

Turn two peak readings into one usable gain setting

Peak normalization starts with a simple practical question: how far is the loudest measured sample from the level you want it to reach? Provide the current peak in dBFS and the intended target peak in dBFS. The calculator subtracts the current value from the target and reports the difference as gain in decibels. If a recording peaks at -8.4 dBFS and the target is -1 dBFS, the required adjustment is +7.4 dB. A positive result means amplification; a negative result means attenuation. A result of zero means no level change is needed. The response repeats both inputs, reports the resulting peak, and confirms that the requested target does not clip. This makes the output convenient for scripts, batch manifests, gain plug-ins, command-line audio tools, or a manual editing checklist. The calculation does not inspect audio samples, estimate loudness, or apply processing. It gives the exact gain setting from peak measurements you already trust, keeping measurement and adjustment as separate, auditable steps.

Choose a target that preserves the headroom you need

In dBFS, 0 dBFS represents digital full scale, so a target above zero would request a peak beyond the available digital ceiling. This calculator rejects such targets instead of returning a gain that promises clipping. A target of exactly 0 dBFS is mathematically valid, although many production workflows choose a lower value such as -1 dBFS to retain headroom for encoding, conversion, resampling, or later signal processing. Select that margin according to the delivery specification for your project rather than treating one target as universally correct. The tool accepts any finite current peak measurement, including a positive value from a meter that reports inter-sample or true-peak overs. In that situation, a safe non-positive target produces negative gain and therefore attenuation. Remember that sample peak and true peak are different measurements: the arithmetic is the same, but the two input values should come from the same measurement convention. Mixing a sample-peak reading with a true-peak delivery requirement can make a numerically correct result unsuitable for the intended quality-control standard.

Apply the result without confusing peak level and loudness

Use the returned gain as a uniform level change in an editor, digital audio workstation, encoder, or processing pipeline. After applying it, measure the output again with the same meter that produced the original peak. Rechecking catches changes introduced by effects, lossy encoding, sample-rate conversion, limiting, or rounding elsewhere in the chain. Peak normalization changes every sample by the same gain and therefore preserves the existing dynamics; it does not make quiet passages independently louder, reduce the crest factor, or match perceived loudness between different programs. For podcast, broadcast, music, or streaming delivery, you may also need an integrated loudness target in LUFS and a true-peak ceiling. Those are separate constraints and can require loudness normalization or limiting rather than this single subtraction. This capability is most useful when the current peak has already been measured and you need a transparent, reproducible gain instruction. Because it performs no upload or audio decoding, it is also suitable for lightweight automation that stores measurements in metadata and computes adjustments before a dedicated audio processor applies them. API requests cost $0.002 each.