Free plan: 1 conversion/hour, 1 file at a time
Go Unlimited →

Normalize Audio Loudness

Free Online Audio Loudness Normalizer

Indicate your files

*Files deleted after 24 hours

Convert up to 1 GB files free, Pro users can convert up to 100 GB files; Sign up now

Uploading

0%

How to Normalize the Loudness of Audio

1 Upload the audio files you want brought to a consistent level — a whole set at once is exactly the case this is for.
2 Pick a target: about -14 LUFS for streaming platforms, -16 LUFS for podcasts, -23 LUFS for broadcast.
3 Run the analysis; integrated loudness and true peak are measured before any gain is decided on.
4 Download the normalized Audio file, with the dynamics inside each track left untouched.

Normalize Audio Loudness FAQ

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.
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.
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.
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.
About -14 LUFS is what the major streaming platforms normalise to, -16 LUFS is the usual podcast target, and -23 LUFS is the broadcast standard. Going louder than the platform target gains you nothing — the platform simply turns it back down.
No. It is a single gain adjustment for the whole file, so the relationship between the quiet and loud parts is untouched. Compression and limiting are separate operations and are not applied here.
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.
Yes: free accounts process audio up to 200 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.
It depends on the source. Lossless input (WAV, FLAC, AIFF) is edited sample-exactly and loses nothing. Lossy input has already discarded detail once, so where the job can be done by copying the encoded stream rather than re-encoding it, that is the path taken.
Yes. The set queues in parallel with identical settings, which is how you process an album or a podcast back catalogue without repeating yourself.
Yes — ID3, Vorbis comments and MP4 atoms are carried across along with embedded artwork, so processed files still sort correctly in a music library.
No. Normalize Audio Loudness is free with no account, and nothing is added to the audio. Uploads are deleted from the workers shortly after the job completes.

Rate this editor

5.0/5 - 0 votes
ns6.com — Free WHOIS privacy, DNS and SSL on every domain.
Or plop your files here