1Upload the MP3 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 MP3 file.
Normalize MP3 Loudness FAQ
Does the source format affect normalisation?
+
It does. MP3 is the universal lossy codec — nothing refuses to play it, at the cost of poorer quality per bit than AAC or Opus. That determines whether the corrected audio can be written back exactly or has to be re-encoded.
Anything specific to MP3 here?
+
Yes — MP3 frames are fixed-size blocks, so a cut lands on a frame boundary and gapless playback markers do not survive a re-encode. Worth knowing when the goal is a consistent set rather than one file.
How does Normalize MP3 Loudness decide the right level?
+
Concretely, loudness is measured against the EBU R128 standard and a single gain adjustment brings the whole file to the target LUFS — which is what streaming platforms actually measure, and is not the same thing as peak normalisation. The file is measured first and the correction follows from the measurement, rather than a fixed gain being applied and hoped for.
Can I run Normalize MP3 Loudness on several MP3 audio files at once?
+
Yes. Upload the set and they process in parallel with the same settings, which is the practical way to handle a podcast series or an album rather than repeating the job by hand.
Is there a file size limit on Normalize MP3 Loudness?
+
Yes: free accounts process audio up to 15 MB per file, which at typical bitrates is several hours of material; ffmpeg does the decoding and encoding, exactly as it would on a desktop. That is the most generous cap on the site after video, and audio work rarely runs into it.
Why does a Word site host Normalize MP3 Loudness?
+
WORD.to is built around the editable end of a document's life — the DOCX that is still being written, still being styled and still being argued over, before anyone flattens it for sending. Office files are containers full of other people's media — images, embedded audio, fonts — so the work people need on them is usually the work they would need on those contents anyway. Normalize MP3 Loudness shares the upload, the caps and the account with the conversions for that reason.
What should I do with the result once Normalize MP3 Loudness is finished?
+
The converter on this site takes documents out to PDF for sending, to images for embedding and to plain text for anything that has to read them programmatically, and back the other way. Doing that afterwards keeps the editable original around, which is the part you cannot get back once it has been flattened.
Is Normalize MP3 Loudness here the same tool the sibling sites run?
+
The engines are shared — the same document toolchain, the same workers, the same limits. What a Word site adds is a view on what survives leaving the Office format and what does not, which is the question every one of these jobs actually turns on. It also starts from one fact about the format this site is named after: the document is a zip of XML, so text edits are cheap and the weight is almost always the embedded images.
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.
