detect and fix audio clipping
Digital clipping occurs when the signal amplitude exceeds 0 dBFS, the maximum representable in binary. Samples exceeding this limit are "clipped" to the maximum value, creating a square wave at the peaks. The auditory result is a characteristic distortion, especially noticeable in vocals and acoustic instruments.
The tool shows the exact clipped-sample count so you can judge if it is audible.
The waveform information that was clipped is permanently lost.
Without a limiter, that same +8 dB would blow past the ceiling and clip the result.
Peak normalization increases or reduces the overall gain of an audio file so that the maximum peak amplitude reaches a defined target level, usually -1 dBFS to avoid clipping on playback systems. It is the simplest and most direct normalization method.
No. Reducing the gain only makes the clipped samples fall below 0 dBFS, but the distortion of the original waveform is still present. The only way to "fix" clipping that already happened is through waveform reconstruction (algorithmic declipping) in specialized tools, or re-recording the audio without clipping.
Yes. It counts every full-scale sample (magnitude at or above 1) in the loaded file, even if there are only a few and they are inaudible. It is an exact count, not a visual estimate from the waveform.
No, that is exactly what it exists to prevent. The limiter anticipates peaks with a 5 ms lookahead, releases the reduction over 80 ms, and the result is double-checked with 4x oversampling before the file closes, guaranteeing the -1 dBTP ceiling instead of letting the gain overshoot the true peak.
Your file is processed locally in the browser. No data is sent to any server.