1Upload the WAV audio files you want brought to a consistent level — a whole set at once is exactly the case this is for.
2Pick a target: about -14 LUFS for streaming platforms, -16 LUFS for podcasts, -23 LUFS for broadcast.
3Run the analysis; integrated loudness and true peak are measured before any gain is decided on.
4Download the normalized WAV file, with the dynamics inside each track left untouched.
Normalize WAV Loudness FAQ
Does the source format affect normalisation?
+
It does. WAV is uncompressed PCM: bit-exact and editable, at roughly 10 MB per stereo minute. That determines whether the corrected audio can be written back exactly or has to be re-encoded.
Anything specific to WAV here?
+
Yes — WAV is raw PCM, so edits are sample-exact and instant, but the file is about 10 MB per stereo minute and uploads dominate the time. Worth knowing when the goal is a consistent set rather than one file.
What loudness target should I aim for?
+
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.
Does normalisation compress the dynamics?
+
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.
Can I run Normalize WAV Loudness on several WAV audio files at once?
+
Yes, though lossless files are large, so the batch is bound by upload bandwidth rather than by processing. Settings apply uniformly across the set.
Are bit depth and sample rate preserved?
+
Yes, unless you change them deliberately. A 24-bit/96 kHz source stays 24-bit/96 kHz — nothing is silently downsampled to 16/44.1, which is the failure mode that makes a master unusable.
Does Normalize WAV Loudness cost anything?
+
No. Normalize WAV Loudness is free with no account required, and nothing is added to the audio. Uploads are deleted from the workers shortly after the job finishes.
Is there a file size limit on Normalize WAV Loudness?
+
Yes: free accounts process audio up to 15 MB per file — for uncompressed PCM that is roughly twenty minutes of CD-quality stereo, so it is a real limit here in a way it is not for MP3. If you are over it, converting WAV to FLAC first is the free fix — it is lossless and roughly halves the size.
Why does a PNG site host Normalize WAV Loudness?
+
PNG.to is built around the format you use when you cannot afford to lose a pixel: lossless, alpha-capable, and the correct answer for screenshots, logos, line art and anything with hard edges. Image work is rarely one step: people arrive to change a format and leave needing the picture a different size, a different weight or a different shape. Running Normalize WAV Loudness on the same upload pipeline, the same size caps and the same account is the whole reason it is here rather than on a fourth tab.
What should I do with the result once Normalize WAV Loudness is finished?
+
The converter on this site moves images to and from PNG, JPG, WebP, GIF and SVG — which is the step where the decision about transparency actually gets made. That is the step most people actually came for, and doing it after Normalize WAV Loudness rather than before it means the conversion works from the file you finally settled on.
Is Normalize WAV Loudness here the same tool the sibling sites run?
+
The engines are shared — the same libraries, the same workers, the same limits. What differs is the advice, and the advice here starts from one fact about the format this site is named after: there is no quality slider to get wrong — a PNG round-trips bit-exactly, so the only thing edits cost you is file size. A PNG site is opinionated about where PNG is the right destination and where it is not, and that judgement is worth more than the button.
Do I need an account, and does anything get kept?
+
No account, and nothing is kept: uploads are deleted from the workers shortly after the job finishes, and nothing you process is indexed, listed or used for anything else. Free accounts exist for history and batch size, not for access.
