Why does the footer report headroom?

Because after attenuating, the amount of space left below full scale is the figure that governs whatever comes next. A file with twelve decibels of headroom can be processed or boosted without much risk, while one with half a decibel is already sitting at the ceiling. It is a practical readout rather than a decorative one.

Can reducing the volume fix a distorted recording?

No. Clipping happens where the waveform was flattened, and turning the level down afterwards keeps the flattened shape at a lower level. The distortion is baked into the waveform geometry. Repairing it needs a declipping tool, and even then the harmonics that were destroyed cannot be recreated exactly.

Is reducing level the same as normalizing?

No. Normalizing measures the file and applies whatever gain is needed to hit a target, while this tool applies a fixed cut that you choose. Normalizing is the right approach when the finishing level matters, and a fixed reduction is right when you simply need the file to sit lower in relation to something else.

Does a large reduction hurt the audio quality?

Not in any way you would hear on a normal file. The samples are scaled by a constant, so the shape of the waveform is preserved exactly, and the WAV output is floating point before it is encoded. Very large cuts on an already quiet recording can bring the noise floor closer to audibility in relative terms, but that is a consequence of the content, not the process.

Can I reduce only part of a file?

Not here. One figure is applied across the whole file, so reducing a single section means splitting the audio first and running the tool on that part alone. For level that changes over time, the leveler is designed to ride the gain automatically instead.

Volume Reducer

You Might Also Need

Volume Booster

Boost audio volume up to safe levels

Balance Adjuster

Adjust left/right balance

Audio Normalizer

Normalize audio levels for consistency

Audio Fade In/Out

Add smooth fade in and fade out effects

Volume Reducer applies a precise decibel reduction to a file and reports exactly what level it left behind. Because turning something down cannot clip, the honest answer here is simply the resulting peak and the headroom that remains.

What is Volume Reducer?

Drop a file, set how many decibels to remove and read the footer. It reports the new peak level both as a linear figure and in dBFS, along with the amount of headroom still available below full scale, so the consequence of the setting is visible immediately.

The control and the readout:

A reduction slider from minus 24 decibels to zero in single decibel steps, defaulting to minus 6.
Four quick presets at minus 3, minus 6, minus 10 and minus 20 decibels.
A footer giving the peak level after the pass as a linear value to three decimals and as dBFS to one decimal.
A second figure stating how many decibels of headroom remain below full scale.
An output WAV named after the source with a reduced suffix.

The maths is a single multiplication per sample: the requested decibels are converted to a linear factor by raising ten to the power of the figure divided by twenty, and every sample is scaled by that one number. Nothing else is changed. There is no dynamics processing, no filtering and no time dependent behaviour, which is what makes the result predictable and exactly reversible in the sense that the same number of decibels added back would restore the original levels. Because attenuation moves the signal further from the ceiling, the whole operation is safe by construction: the output cannot clip regardless of how much is removed or how hot the input was. The footer's headroom figure is the useful part in practice, since it tells you how much room is left for whatever processing comes next.

What attenuation cannot do:

It does not change the dynamic range of the file, only its position, so a squashed mix stays squashed at a lower level.
It cannot fix uneven levels inside a recording, which needs a leveler or a compressor rather than a global gain.
Removing a large amount makes the noise floor and any quantisation at the bottom of the file more prominent in relative terms.
There is no metering beyond the peak figures, so loudness is not measured and perceived level is not reported.
The tool applies one figure to the whole file, with no automation and no way to reduce only part of it.
Reducing level does not restore the headroom that clipping already destroyed earlier in the chain.

Use it whenever a file needs to sit lower without anything else changing: to make room in a mix, to prepare a track for a limiter that benefits from a little space above it, or to lower a source that is drowning everything else. Pick a figure, check the remaining headroom in the footer, and remember that if the goal is a specific loudness rather than a specific cut, a normalizer is the tool that measures its way there. One figure for the whole file is the point here; when only part of a recording needs to sit lower, the leveler is the tool that rides gain over time instead, and when only one side is too loud, the balance adjuster is the right instrument.

How to use Volume Reducer

Drop an audio file onto the panel or click to choose one.
Set the reduction with the slider, or press one of the presets at minus 3, minus 6, minus 10 or minus 20 decibels.
Run the pass and read the footer, which gives the new peak in dBFS and the headroom that remains.
Download the reduced WAV, named after the original with a reduced suffix.

When to use Volume Reducer vs related tools

Volume Reducer is the precise attenuation tool, so it is the right answer when a file simply needs to be quieter by a known amount. Volume Booster does the opposite with an explicit peak strategy, and Balance Adjuster applies the same idea to one channel only when the problem is a leaning stereo image. When the level needs to be measured rather than guessed, Loudness Normalizer targets a loudness figure directly, and Audio Fade In/Out shapes level over time rather than applying one constant.

Privacy & Security

This tool runs entirely in your browser — no data ever leaves your device. There is no server round-trip, no upload, no logging, and no account required. Your input is processed locally using client-side JavaScript and is never stored, transmitted, or accessible to anyone else. When you close the tab, everything disappears.