1Upload the WAV 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 WAV file.
Normalize WAV Loudness FAQ
How does Normalize WAV Loudness decide the right level?
+
Concretely, R128 loudness analysis drives an exact gain applied to the PCM, so a whole album can be brought to one target level with the relative dynamics inside each track untouched. The file is measured first and the correction follows from the measurement, rather than a fixed gain being applied and hoped for.
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 can I upload to Normalize WAV Loudness?
+
WAV, FLAC and AIFF, at any bit depth and sample rate up to and including 24-bit/192 kHz. Lossy files work in the same batch if you are mixing sources.
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.
Will Normalize WAV Loudness lower the quality of my WAV audio files?
+
No. Lossless audio is edited sample-exactly, so what comes back decodes bit-identically to what you would get doing the same edit in a desktop editor. You can repeat the cycle as many times as you like without accumulating any loss at all.
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.
Why does a EPUB site host Normalize WAV Loudness?
+
EPUB.to is built around the open eBook format — XHTML in a zip, reflowable by design, and readable on hardware nobody has thought about the layout for. A book is a zip full of markup, images and fonts, so almost every job people bring to an eBook site is really a job on one of those things. Normalize WAV Loudness runs on the same upload and the same account as the conversions because that is where it is needed.
What should I do with the result once Normalize WAV Loudness is finished?
+
The converter on this site moves books between EPUB, MOBI, AZW3, PDF and DOCX, so a title ends up on whatever hardware is actually going to read it. Doing that after Normalize WAV Loudness means the conversion is made from the version you settled on, not from the one you were still fixing.
Is Normalize WAV Loudness here the same tool the sibling sites run?
+
The engines are shared — the same toolchain, the same workers, the same limits. What a EPUB site adds is a view on reflow: which of these operations a reflowable book genuinely supports, and which ones only make sense on the fixed-layout media inside it. It also starts from one fact about the format this site is named after: the book is a zip of XHTML with a manifest, so the text costs almost nothing and every decision that matters is about the embedded images and font subsets.
Do I need an account, and does anything get kept?
+
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.
