|5.115Mins Read
How to Normalize Audio Loudness with LUFS: A Two-Pass Guide
- Authors
- Name
- Geeks Kai
- @KaiGeeks
The fastest repeatable workflow is to measure the entire file, choose the loudness target required by its destination, and run a second normalization pass using the measured integrated loudness, true peak, loudness range, and threshold. This is more predictable for finished files than adjusting only their highest peak.
If you already own or have permission to process the file, the Geekskai Audio Toolkit performs this two-pass workflow locally in your browser. A signed-in account receives 30 Free Credits per UTC day and processes one file at a time.
Peak normalization answers a narrow question: how close does the highest sample or true peak come to the ceiling? It can make two files share a similar maximum peak while they still sound noticeably different in average loudness.
LUFS-based normalization instead estimates perceived programme loudness over time. The European Broadcasting Union describes EBU R 128 as a move from using peak meters alone to measuring and normalizing loudness with loudness meters. The EBU also publishes separate guidance for broadcast, streaming, radio, short-form, and cinematic material, which is why one target should not be treated as universal. See the EBU loudness specification overview.
FFmpeg's official loudnorm filter supports both single-pass and double-pass operation. It can target integrated loudness, loudness range, and maximum true peak. See the loudnorm filter documentation.
A two-pass file workflow works like this:
This workflow is appropriate for completed files because the first pass can inspect the whole programme. A live stream cannot be measured from beginning to end before playback, so live workflows have different constraints.
The current Audio Toolkit accepts MP3, WAV, FLAC, and M4A input files up to 200 MB each. Processing uses FFmpeg in the browser; audio and filenames are not uploaded to Geekskai for processing.
The toolkit's normalization pipeline performs an analysis pass, then applies the measured values during the second pass with a true-peak ceiling. One Credit covers one minute of combined input audio, rounded up once per batch. Pay As You Go and Regular monthly Credits are available through secure PayPal checkout for batches of up to 50 local files and ZIP export. Paid Credits apply only to Audio Toolkit processing; public third-party downloader allowances remain separate free-product rules.
Start with the delivery specification, not a number copied from an unrelated platform guide.
Normalization is not a repair tool. It will not remove clipping already recorded into a file, eliminate background noise, correct a poor mix, or restore detail lost to aggressive compression.
Choose WAV when the file will be edited again, archived, mastered, or delivered in an uncompressed format. Choose MP3 when a smaller listening or review copy is appropriate and the recipient accepts lossy audio.
The toolkit currently offers:
| Output | Options | Good fit |
|---|---|---|
| WAV | 16-bit or 24-bit PCM | Editing, mastering handoff, archive, lossless delivery |
| MP3 | 320 kbps | Review copies and destinations that accept MP3 |
Converting a lossy MP3 to WAV does not restore information discarded during the original MP3 encoding. It only changes the output container and encoding.
Browser processing uses the local device. Long files and lossless formats can require more memory and time. Close memory-heavy tabs, keep the browser tab active, and test with a shorter file if the device is constrained.
Confirm that its extension is MP3, WAV, FLAC, or M4A and that the file is no larger than 200 MB. Renaming an unsupported file does not convert its actual media format.
Loudness normalization cannot undo clipping or distortion already present in the source. Return to the mix or an earlier master, lower problematic levels, and export a clean source before normalizing again.
Check that you entered the intended target and compare it with the destination's current specification. Perceived loudness also depends on dynamics, frequency balance, and listening conditions; matching a LUFS number does not make different mixes sound identical.
For a private, installation-free workflow, try one file in the Geekskai Audio Toolkit. For plan limits and current checkout availability, see Audio Toolkit pricing.