Why is minus 1 dBFS the transparent setting?

Because it leaves a decibel of space above the loudest sample, which matters when the file will be encoded to a lossy format. Encoders can produce inter sample overshoot slightly above the level the file itself contained, so having a little headroom means the encoded version is still safe. It is also gentle enough to be inaudible on most material.

What makes this a brick wall rather than an ordinary limiter?

The lookahead. The signal is delayed while the detector examines what is coming, and the gain computed for a peak is held in a buffer aligned to that exact delay, so it is already applied when the peak arrives. That removes overshoot entirely, which is what the term describes.

Which preset should I use for a streaming release?

The loud streaming preset, at minus 0.3 dBFS with a 40 millisecond release. That ceiling is what most services expect for delivery, and the faster release keeps the level up between peaks. Pair it with a loudness normaliser beforehand if the file also has to hit a target in LUFS.

Does the limiter add loudness?

No. It only reduces peaks, so the output is at or below the input level. Loudness comes from raising the level into the space that limiting creates, which is why the two steps are normally done in order: normalise to the target, then limit to keep the peaks in place.

Why does my bass sound different at zero dBFS?

Because a low ceiling with a fast release means the gain is changing quickly, and low frequency content is where fast gain changes become audible as distortion. The transparent preset with its slower release avoids most of it. If the deliverable allows minus 1 dBFS, that is the safer choice for bass heavy material.

Brickwall Limiter

You Might Also Need

Peak Limiter

Prevent audio peaks and clipping

Audio Limiter

Apply peak limiting to prevent clipping

Clipping Distortion Remover

Repair clipped audio distortion

Loudness Normalizer

Normalize to LUFS loudness standards

Brickwall Limiter is the final-safety version of a limiter, built around three delivery presets instead of a wall of parameters. The output never crosses the ceiling, whatever happens upstream.

What is Brickwall Limiter?

Drop a file, choose the preset that matches your delivery, and adjust the lookahead if you want more safety margin. The report gives the peak before and after, the ceiling that was enforced and a plain description of what the preset is for.

The three presets:

Transparent, with a ceiling of minus 1 dBFS and an 80 millisecond release, leaving a decibel of headroom and staying inaudible on most material.
Loud for streaming, at minus 0.3 dBFS with a 40 millisecond release, which is the ceiling most services expect for delivery.
Hard digital, at zero dBFS with a 20 millisecond release, where nothing at all passes above the line and recovery is fastest.
A lookahead control from 1 to 20 milliseconds, defaulting to 5, shared by all three presets.
A report line giving the peak before and after the pass, the ceiling in force and the preset's description.

The engine is the same lookahead brick wall used by the peak limiter, with the signal delayed while the detector looks ahead and the computed gain held in a ring buffer aligned to that delay. That alignment is what makes the brick wall claim literal: because the gain for a peak is already in place when the peak reaches the output, overshoot is not possible, and the ceiling is a property of the output rather than an aspiration. The presets differ in ceiling and release, which is where the character comes from. A minus 1 dBFS ceiling with a slow release is the conservative choice for material that has to survive a lossy encode, since encoders can overshoot what the file itself did. The minus 0.3 preset matches the common streaming delivery recommendation. Zero dBFS is the mathematically tightest line, and with the fastest release it is also the most likely to sound worked on. Because the tool is a limiter, it only reduces peaks; it does not raise the level of the file.

What a brick wall does not give you:

It cannot make a file louder, only quieter at the peaks, so a quiet master stays quiet after the pass.
A really low ceiling with a fast release will audibly change dense material, particularly bass.
The ceiling applies to sample peaks, so inter sample overshoot is not specifically modelled.
Only three presets exist, with no separate control of release outside them.
It is not a loudness tool, so it says nothing about where the file lands against a platform target.
It cannot undo peaks that were already clipped before the file reached it.

Use it as the last stage of any chain, when the requirement is simply that nothing exceeds a stated line. The transparent preset is the safe default for anything that will be encoded to a lossy format afterwards, and for mastering deliveries where the level was set earlier in the chain, the streaming preset matches what most services expect, and the hard digital preset is for situations where the deliverable spec literally says zero. If the file also needs to reach a loudness figure, normalise first and limit afterwards.

How to use Brickwall Limiter

Drop an audio file onto the panel or click to choose one from disk.
Choose the preset that matches the delivery: transparent, loud for streaming, or hard digital.
Adjust the lookahead if you want a wider safety margin before each peak.
Run the pass, check the peak figures in the report, and download the brickwalled WAV.

When to use Brickwall Limiter vs related tools

Brickwall Limiter is the delivery-ceiling tool, so it belongs at the end of a chain rather than in the middle of one. Peak Limiter is the same engine with direct control of the ceiling, lookahead and release, which suits material that needs tuning rather than a preset. When the deliverable is defined by loudness rather than by peak, Loudness Normalizer is the tool that measures its way to the target, and Clipping Distortion Remover handles the case where the damage happened earlier than the limiter.

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.