1Upload the MP3 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 MP3 file, with the dynamics inside each track left untouched.
Normalize MP3 Loudness FAQ
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.
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.
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.
Will Normalize MP3 Loudness lower the quality of my MP3 audio files?
+
A lossy file has already discarded detail once, and re-encoding discards more — that is generation loss and it does not undo. Wherever the job can be completed by copying the encoded stream rather than re-encoding it, that is what happens, and the audio comes back bit-identical.
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.
Do tags and cover art survive?
+
Yes. ID3, Vorbis comments and MP4 metadata atoms are carried across, cover art included, so a processed file still sorts correctly in a music library. ReplayGain values are recalculated rather than copied, because a stale one is worse than none.
Does Normalize MP3 Loudness cost anything?
+
No. Normalize MP3 Loudness is free without an account and adds no audio watermark or spoken tag to the output. Your upload is deleted from the workers shortly after the job completes.
Why does a WebM site host Normalize MP3 Loudness?
+
WEBM.to is built around the container the open web actually chose — VP9 or AV1 with Opus audio, decoded natively by every modern browser and needing no plugin, licence or player. Video is the case where extra round trips hurt most — the files are large and every upload costs real minutes. Running Normalize MP3 Loudness on the same pipeline as the conversions means one upload covers the whole job instead of one upload per tool.
What should I do with the result once Normalize MP3 Loudness is finished?
+
The converter on this site moves video between WebM, MP4, MKV, MOV and the rest, or pulls the soundtrack out entirely, without another upload. Sequencing it that way matters more for video than anywhere else: each re-encode is another generation, so the fewer of them stand between the source and the file you publish, the better it looks.
Is Normalize MP3 Loudness here the same tool the sibling sites run?
+
The engines are shared — the same ffmpeg build with x264, x265 and libvpx, the same workers, the same limits. What a WebM site adds is a view on containers and codecs: which combinations play everywhere, which need a re-encode and which can simply be copied across. It also starts from one fact about the format this site is named after: WebM is VP9 or AV1 with Opus audio, which browsers decode natively but which most desktop editors still transcode on import.
Do I need an account, and does anything get kept?
+
No account, and nothing is kept: uploaded video is deleted from the workers shortly after the job finishes, nothing is watched and nothing is indexed. Free accounts exist for history and batch size, not for access.
