Normalize Audio
Processed locally in your browser — nothing is uploaded.
Quick answer
Normalizing audio evens out loudness so a file sits at a consistent target level instead of jumping between quiet and loud. Modern normalization uses the EBU R128 loudness standard, measured in LUFS, matching how ears actually perceive loudness — streaming platforms target about −16 LUFS. This tool analyses your file and applies the right gain in your browser, with nothing uploaded. First use downloads the ~32 MB engine once, then caches it.
How to normalize audio
Add your audio
Drop in the file. The tool measures its integrated loudness in LUFS across the whole thing.
Pick a target loudness
Choose a target such as −16 LUFS for streaming or −23 LUFS for broadcast. The tool calculates the exact gain needed to reach it.
Normalize and download
Apply the correction and download a file that sits at your chosen loudness.
What is LUFS, and why not just use peaks?
LUFS — Loudness Units relative to Full Scale — measures perceived loudness over time, weighting frequencies the way human hearing does. That is why it beats peak-based methods: two files can have identical peaks yet feel wildly different in loudness because one is dense and one is sparse. Peak normalization only guarantees the single loudest sample hits a ceiling; LUFS normalization (EBU R128) matches the average loudness you actually experience, which is what makes tracks stop lurching between quiet and loud.
There are three LUFS readings worth distinguishing. Integrated loudness is the single number for the whole file — the one you normalize to a target. Short-term and momentary loudness describe how loud the file is over the last few seconds and the last fraction of a second, useful for spotting passages that spike. Alongside them sits true peak, the highest instantaneous sample level, which a good normalizer keeps under the ceiling so that hitting a loudness target never sneaks clipping back in.
| Target | LUFS | Where it applies |
|---|---|---|
| Streaming music/podcasts | −16 LUFS | Spotify, Apple, most podcast apps |
| YouTube | −14 LUFS | Platform playback normalization |
| EBU R128 broadcast | −23 LUFS | European TV and radio |
| US broadcast (ATSC A/85) | −24 LKFS | US television |
Normalize vs. compress vs. amplify — what is the difference?
These three get muddled constantly, so it is worth pinning down:
- Normalize measures the whole file’s loudness and applies one gain so the average hits a target. It changes level, not dynamics.
- Amplify (adjust volume) applies a gain you type by hand — no measurement, no target. Blunt and manual.
- Compress (dynamic-range compression) reduces the gap between loud and quiet *within* the file, evening out moment-to-moment swings. Note: "compress" here means dynamics, not file size — that other meaning of compress lives on the compress audio page.
In practice the three often work together. You might compress a voice recording to tame the gap between loud and quiet phrases, then normalize the compressed result to −16 LUFS so it sits at the same level as everything else in the feed. Amplify is what you reach for only when you already know the exact decibels you want and have no need for a measured target at all.
Does normalizing upload my audio?
No. Both the loudness measurement and the gain correction run in ffmpeg.wasm inside your browser. Your file is analysed and rewritten locally and never sent anywhere — confirm it in DevTools → Network, where normalizing produces no upload. Unreleased mixes and confidential recordings stay on your machine.
Related audio and video tools
Need a manual, exact dB change instead of a target? Use adjust audio volume. Smoothing the ends is the job of fade in and out. Once loudness is even, compress the file for delivery. And if the audio is currently inside a clip, extract the audio from the video first, then normalize it here.
Your files never leave your device
Processed locally in your browser — nothing is uploaded. You can verify it yourself: open your browser’s developer tools, watch the Network tab, and use the tool — no upload request is ever made.
Frequently asked questions
What LUFS should I normalize a podcast to?
About −16 LUFS is the common target for podcasts and streaming music. Broadcast uses −23 LUFS (EBU R128) or −24 LKFS (US).
What is the difference between normalize and amplify?
Amplify applies a gain you type by hand. Normalize measures the file’s loudness first and computes the gain needed to reach a target, so results are consistent across files.
Is normalizing the same as compression?
No. Normalizing changes overall level to a target. Dynamic-range compression narrows the gap between loud and quiet within the file. They solve different problems.
Why is LUFS better than peak normalization?
LUFS reflects perceived loudness, weighting frequencies like human hearing. Peak normalization only aligns the single loudest sample, which does not match how loud a file feels.
Will normalizing cause clipping?
Loudness normalization targets an average, and a true-peak safeguard keeps peaks under the ceiling, so it avoids the clipping that a blind boost can cause.
Can I normalize several files to match?
Yes — that is the main use. Normalize each file to the same LUFS target and they will sound equally loud when played back to back.
Is my file uploaded?
No. Measurement and correction both run locally via WebAssembly. You can verify there is no upload in the Network tab.