1Upload the audio files you want brought to a consistent loudness.
2There is nothing to set: the loudness is brought to -16 LUFS (EBU R128), with true peaks kept below -1.5 dBTP.
3Run the analysis; integrated loudness and true peak are measured before any gain is decided on.
4Download the normalized Audio file.
Normalize Audio Loudness FAQ
Does the source format affect normalisation?
+
It does. this format is read and written by the same streaming pipeline as everything else we support. That determines whether the corrected audio can be written back exactly or has to be re-encoded.
Anything specific to Audio here?
+
Yes — the codec is detected from the stream, so a mislabelled extension does not derail the job. Worth knowing when the goal is a consistent set rather than one file.
How does Normalize Audio Loudness decide the right level?
+
Concretely, the file is analysed for integrated loudness and true peak, then a single gain is applied to reach the target — no compression, no limiting, just the level. The file is measured first and the correction follows from the measurement, rather than a fixed gain being applied and hoped for.
What is the difference between this and just turning it up?
+
A volume change applies a number you chose. Normalisation measures how loud the file actually is and computes the gain needed to hit a target, so ten files recorded at ten different levels all arrive at the same one.
Which audio formats does Normalize Audio Loudness accept?
+
MP3, WAV, AAC, M4A, FLAC, OGG, Opus, WMA and AIFF. Codecs are detected from the stream rather than the extension, so a mislabelled file still works and a mixed batch is handled per file.
Is there a file size limit on Normalize Audio Loudness?
+
Yes: free accounts process audio up to 15 MB per file whichever codec you brought; ffmpeg handles the decode and encode. In practice that limit only bites on uncompressed WAV; a compressed file of the same length is nowhere near it.
Why would a modern-format site run Normalize Audio Loudness?
+
WEBP.to is built around the modern replacement for both of the old defaults: one format that does lossy, lossless, alpha and animation, and reliably lands smaller than the JPEG or PNG it came from. People arrive here having decided the old defaults are costing them bandwidth, and that decision immediately raises the rest: what size, what quality, what happens to the transparency. Normalize Audio Loudness is on the same upload and the same account so those questions get answered in one place.
Once Normalize Audio Loudness has run, what is worth doing next?
+
The converter on this site moves images to and from WebP, PNG, JPG and AVIF, which is where you decide whether a smaller file is worth losing the older browsers. Doing it in that order matters: pick the pixels first and the container afterwards, because the container is the cheap decision and the pixels are the expensive one.
Do the sibling sites run something different?
+
The engines are identical — same libraries, same workers, same caps. What is different is the opinion attached, and the opinion here rests on a property of the format this site is named after: the same .webp extension can hold a lossy VP8 frame, a lossless one, or an animation, so the sensible processing path is decided per file rather than per extension.
What happens to my file, and is an account required?
+
No account is needed. Uploads and results are kept for about 24 hours, which leaves time to download the result, and are then deleted automatically; nobody reads, lists or indexes them. Several files in one job need a paid plan.
