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
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.
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.
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.
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.
What can I upload to Normalize MP3 Loudness?
+
MP3, AAC, M4A, OGG, Opus and WMA are the lossy codecs handled directly, and lossless sources (WAV, FLAC, AIFF) can go in the same batch. The codec is probed from the stream, so an incorrectly named file still works.
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.
Does Normalize MP3 Loudness belong on a site about a photo format?
+
JPEG.to is built around the format that carries nearly every photograph in existence — thirty years old, opened by literally everything, and still the right default for a photographic image. The jobs people bring here are the ones a photograph collects over its life — too big to email, wrong dimensions for a form, wrong way up out of a phone. Normalize MP3 Loudness runs on the same upload and the same account as the conversions because that is where those jobs land.
What is the sensible next step after Normalize MP3 Loudness?
+
The converter on this site moves images to and from JPEG, PNG, WebP and HEIC, which is where the trade between file size and one more generation of loss gets settled. Deciding the format last rather than first is the whole point: every extra save of a photographic image is another generation, and the fewer of them you spend, the more of the picture survives.
Is this the same engine as the other converter sites?
+
Yes — the same libraries, the same workers, the same caps. The difference is which advice is on the page, and here that advice is built on one property of the format the site is named after: the .jpeg and .jpg extensions are the same bitstream, so nothing here behaves differently from a .jpg — only the filename changes.
Is anything kept, and do I need to sign in?
+
Nothing is kept and no account is needed. Uploads are removed from the workers shortly after the job finishes; nothing is looked at, listed or indexed. An account buys history and larger batches, not access.
