What does lookahead do?

It delays the audio while the detector examines what is coming, so the gain reduction is already in place when the peak reaches the output. Without it a limiter has to react after the fact, which either overshoots the ceiling or introduces distortion. Longer lookahead is safer at the cost of additional delay on the file.

How much gain reduction is too much?

There is no fixed number, but the more the limiter pulls, the more obvious it becomes. A decibel or two on occasional peaks is inaudible on most material, while continuous reduction of several decibels changes the punch of a mix. If the report shows heavy reduction across the whole file, the level should come down before limiting rather than after.

Why does my bass sound different after limiting?

Because low frequency content interacts badly with fast gain changes. A short lookahead with a quick release can make the gain itself fluctuate within a cycle of a low note, which produces distortion. Slower release and a slightly longer lookahead usually clear it up.

Does limiting make the file louder?

Not by itself. It only reduces peaks, so the output is at or below the input level. What makes a file louder is combining the reduced peaks with a gain increase, which is how the normaliser and limiter are used together: control the peaks first, then raise the level into the space you created.

Is this the same as a brickwall limiter?

The engine is identical, a lookahead brick wall. The difference is the interface: this tool exposes the ceiling, lookahead and release directly so you choose every value, while the brickwall version leads with three delivery presets and a single lookahead control.

Peak Limiter

You Might Also Need

Brickwall Limiter

Ultra-transparent peak limiting

Audio Limiter

Apply peak limiting to prevent clipping

Clipping Distortion Remover

Repair clipped audio distortion

Loudness Normalizer

Normalize to LUFS loudness standards

Peak Limiter holds the loudest moments of a file under a ceiling you set, using lookahead so the gain is already reduced when the peak arrives. It is the general purpose limiter: you choose how far ahead it listens and how quickly it lets go.

What is Peak Limiter?

Drop a file, set the ceiling, decide how much lookahead to give the detector and how fast the gain should recover, then read the report. The footer gives the peak before and after, the ceiling in force and the total gain reduction applied.

The controls:

A ceiling from minus 12 to zero dBFS in half decibel steps, defaulting to minus 1.
A lookahead from 1 to 20 milliseconds in single millisecond steps, defaulting to 5.
A release from 10 to 500 milliseconds in steps of 10, defaulting to 60.
A report line quoting the peak before and after the pass, the ceiling and the gain reduction in decibels.
An output WAV named after the source with a limited suffix.

The engine is a lookahead brick wall limiter. The signal is delayed by the lookahead time while the detector looks at what is coming, and the gain that is computed when a peak is spotted is held in a ring buffer aligned to that exact delay, so a peak always receives the gain that was calculated for it rather than a gain computed a moment too late. That is what prevents overshoot: a limiter without lookahead has to react after the transient has already passed the ceiling, and the result is either an overshoot or a distortion known as clipping something that only happens in the moment. Release controls how quickly the gain returns to unity after each peak, and it is the control that shapes the character of the result: a fast release restores level quickly and can sound pumped on dense material, while a slow release holds the level down longer and sounds smoother but reduces more overall. The report's gain reduction figure is the difference between the peak before and after, which is the honest measure of how hard the limiter worked.

Where limiting is the wrong answer:

It does not raise the average level unless the peaks are what was holding it back, so a quiet file stays quiet after limiting.
Limiting is transparent only up to a point; several decibels of gain reduction on a dense mix becomes audible as a loss of punch.
A very short lookahead and a fast release can add audible distortion on low frequency content, because the gain itself is changing quickly.
It works on sample peaks, so true inter sample peaks are not modelled by the setting here.
The limiter has no makeup gain control, so the output is simply quieter rather than louder after a heavy pass.
Long lookahead values delay the audio, which matters when the file has to line up with something else.

Use it as the final stage before delivery, when the job is to guarantee that nothing exceeds a stated line. Set the ceiling for the destination, give the detector a few milliseconds of lookahead, and choose a release that suits the density of the material: shorter for sparse speech, longer for a dense mix that would otherwise pump. Read the before and after peak figures together, because a large drop with an unchanged character usually means the ceiling was set lower than the material actually needed.

How to use Peak Limiter

Drop an audio file onto the panel or click to choose one from disk.
Set the ceiling you need the output to stay under, starting from minus 1 dBFS.
Choose a lookahead in milliseconds, longer being safer but delaying the audio further.
Pick a release that suits the material, run the pass and read the gain reduction in the footer.

When to use Peak Limiter vs related tools

Peak Limiter is the everyday tool for keeping peaks under a line without squashing the whole file. Brickwall Limiter is the same engine with three delivery presets, which is the faster route when the ceiling is a platform standard. When the goal is a loudness figure rather than a peak figure, Loudness Normalizer measures and targets loudness directly, and when the problem is peaks that are already flattened rather than peaks that need holding, Clipping Distortion Remover rebuilds them.

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.