NEW · FFmpeg.wasm · 100% Browser-Based

Audio Peak Limiter

Apply brickwall peak limiting to prevent clipping while maintaining loudness — the standard final step after normalization. Adjustable ceiling, release time, and lookahead. FFmpeg.wasm runs locally. No upload, no signup, no watermark.

🎵
Drop an audio file
MP3 · WAV · AAC · OGG · FLAC · M4A
Files stay on your device · Never uploaded

Related Tools on UDT

Audio Normalizer →
EBU R128 loudness normalization — apply before the limiter.
Audio Compressor →
Codec/bitrate compression — usually the final step after limiting.
Audio Fade In/Out →
Add fade-in/fade-out with curve control.
All Audio Tools →
Browse the full Audio Suite — 13 tools, all in-browser.

Why Do This in Your Browser?

After loudness normalization the average level is right, but individual peaks can still spike past 0dB and clip on playback. The fix is a brickwall limiter: a fast compressor with an extremely high ratio (effectively infinite) and a ceiling parameter that the audio cannot cross. The limiter catches the brief peaks and pulls them back to the ceiling, leaving everything below untouched. The result is loud but never distorted.

Limit-after-normalize is the standard mastering chain for streaming and broadcast delivery. Spotify normalizes to -14 LUFS with a -1dBTP true-peak ceiling; Apple Music sits at -16 LUFS with the same ceiling target. Apply the normalizer first to set the average level, then apply the limiter to catch the peaks. FFmpeg's `alimiter` filter handles this — and it runs in the wasm build with no additional dependencies.

How It Works

Drop an audio file. Set the ceiling — the maximum allowed peak in dB, typically -0.3 to -1.0 for streaming (leaves headroom for codec overshoot), -0.1 for already-encoded files, or -3.0 for conservative broadcast targets. Set the release time — how quickly the limiter recovers after a peak (5–50ms typical; faster releases preserve transients, slower releases sound smoother). Optionally enable lookahead for cleaner peak detection (adds a few ms of latency but catches peaks before they happen).

FFmpeg applies `alimiter=limit=L:release=R:level=disabled:asc=1` where L is the ceiling in dB and R is the release time in milliseconds. The `level=disabled` flag means the limiter doesn't apply makeup gain — that's the normalizer's job. `asc=1` enables auto-release scaling so the limiter adapts release time based on signal dynamics. The result is exported in the original format by default.

Tip: For the loudness normalization that should precede limiting, use the Audio Normalizer first. After limiting, the Audio Compressor finishes the chain with codec/bitrate conversion for distribution.

Common Use Cases

Streaming Delivery Polish
Final brickwall pass before uploading to Spotify, Apple Music, or YouTube. Catches inter-sample peaks the normalizer alone may miss.
Podcast Mastering
Apply at -1dB ceiling after normalization. Prevents clip distortion on listener devices with cheaper DACs.
Broadcast Compliance
EBU R128 broadcast standards require -1dBTP true-peak ceiling. The limiter guarantees compliance after normalization.
Live Recording Cleanup
Stage recordings often have transient spikes from coughs, mic bumps, or applause. The limiter catches the worst without destroying dynamics.
Sample Library Safety
Limit one-shot samples to a uniform ceiling so they integrate cleanly into productions without clipping the mix bus.
Voice-Over Distribution
Voice content often has plosive spikes from 'P' and 'B' sounds. A gentle limiter at -1dB catches them without sounding processed.

How We Compare

Honest read on free, paid, and self-hosted options for this kind of job:

UDT Audio Peak Limiter (this tool): Free, browser-based, FFmpeg.wasm alimiter filter. Adjustable ceiling, release time, and lookahead. Pairs cleanly with the Audio Normalizer. No upload, no watermark, no signup.
FabFilter Pro-L 2: Industry-standard limiter plugin, $199. Cleaner transient preservation than free options for high-end mastering work.
Audacity (desktop): Free, full audio editor with a built-in Limiter effect. This browser tool is the focused alternative — no install, no project.
Adobe Audition: Creative Cloud $20+/mo. Hard Limiter effect with similar parameters.
FFmpeg CLI: Free, command-line; same engine as this tool. alimiter=limit=-1dB:release=50. This is FFmpeg with a UI.
LANDR / cloud mastering: Automated mastering services. Limit is one stage of many. For just the limiter step, this tool is the focused free path.

Frequently Asked Questions

Is this audio peak limiter really free?+
Yes — completely free, no watermark, no time limits, no signup. The site is supported by ads elsewhere; the tool is unrestricted.
What's the difference between a limiter and a compressor?+
A limiter is a compressor with an extremely high ratio (often infinite) and a fixed ceiling. It only affects audio that crosses the threshold — everything below passes through unchanged. A compressor reduces the dynamic range of the whole signal. Limiters are for catching peaks; compressors are for shaping overall loudness.
What ceiling value should I use?+
For streaming (Spotify, Apple Music, YouTube), -1.0dB is the standard true-peak ceiling and leaves headroom for codec overshoot. For broadcast (EBU R128), -1.0dBTP is required. For already-encoded files where the codec damage is done, -0.1dB to -0.3dB is safe. -3.0dB is overly conservative but used by some mastering houses as a margin.
Should I run the normalizer before or after the limiter?+
Normalizer first, then limiter. The normalizer raises the average loudness to the target; the limiter then catches any peaks that the loudness boost pushed past the ceiling. Reverse order doesn't work — the normalizer would push peaks back over the limit.
What does 'lookahead' do?+
Lookahead introduces a small delay (typically 5–10ms) so the limiter can see peaks before they happen. This lets it apply gain reduction more smoothly than a reactive limiter. The output is identical except for that small latency offset, which doesn't matter for a rendered file.
Are my audio files uploaded anywhere?+
No. FFmpeg.wasm runs entirely in your browser. The 32MB engine downloads once and caches; after that, the tool works fully offline.
What's the maximum file size?+
Limited by browser memory. Most laptops handle 1–2GB audio files comfortably; phones cap around 500MB.
What's the underlying engine and license?+
FFmpeg.wasm v0.12.x with @ffmpeg/core v0.12.6 (alimiter filter built in). FFmpeg itself is LGPL-licensed; the wasm wrapper is MIT.