Adjust audio volume in decibels

Enter the current peak in dBFS and the gain in dB, and it returns the resulting peak, remaining headroom, and a clear clipping flag. It is useful for checking a proposed level change before processing a file, setting a mixer, or building an automated audio workflow. The calculation is deterministic and does not upload, decode, or modify audio.

Read peak level and gain as two different measurements

A digital peak is commonly expressed in dBFS, where 0 dBFS is the maximum representable level and ordinary unclipped peaks appear as negative values. Gain, by contrast, is a relative change expressed in dB. A gain of 3 dB raises the peak by 3 dB, while a gain of -3 dB attenuates it by the same amount. This calculator keeps those roles explicit: current_peak_dbfs describes where the signal starts, and gain_db describes the change you intend to apply. The resulting peak is their arithmetic sum. For example, a peak at -8 dBFS with 5 dB of gain becomes -3 dBFS. No waveform analysis is performed, so the current peak should come from a trusted meter, editor, loudness report, or earlier processing step. The result predicts peak position after ideal gain only. It does not estimate loudness, dynamics, inter-sample peaks, codec overshoot, or changes caused by compression, limiting, equalization, mixing, or sample conversion.

Interpret clipping and headroom at the 0 dBFS boundary

The clipping flag becomes true only when the calculated peak is greater than 0 dBFS. A result exactly equal to 0 dBFS reaches full scale but does not exceed it, so this calculator reports clipping as false and headroom as zero. That distinction makes boundary checks predictable in automation. A positive result, such as 1.5 dBFS, means the proposed gain would push the known peak 1.5 dB beyond full scale; the returned headroom is therefore -1.5 dB. A negative result leaves positive headroom. This is a mathematical warning, not a simulation of a particular audio system. Floating-point formats and some internal processing chains can temporarily represent values above full scale, while integer exports, digital-to-analog paths, codecs, plug-ins, and mastering requirements may behave differently. Engineers often reserve additional safety margin for true peaks or downstream processing. Use the flag to catch an obvious overage, then apply the headroom result and the requirements of the destination format when choosing a safe final gain.

Use the calculation in repeatable audio workflows

The calculator is designed for small, auditable decisions that need the same answer every time. In a batch pipeline, a peak scanner can provide the current dBFS value, after which this capability can evaluate a requested gain before any rendering begins. A user interface can show the predicted peak and disable an unsafe export, or a quality-control job can record the clipping boolean alongside its source measurement. Negative gain works naturally, making the same endpoint useful for attenuation and headroom targets. Both inputs must be finite JSON numbers; numeric-looking strings are rejected so an integration cannot silently concatenate text or accept an ambiguous value. The returned object repeats the two validated inputs, gives the calculated peak, reports clipping, and expresses remaining headroom as the negative of the resulting peak. Because the function uses no network, randomness, clock, audio decoder, or hidden state, identical inputs produce identical JSON results. Remember that it evaluates one supplied peak and one uniform gain adjustment, rather than inspecting an audio file or accounting for later signal processing.