1Upload the AAC 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 AAC file, with the dynamics inside each track left untouched.
Normalize AAC Loudness FAQ
Does the source format affect normalisation?
+
It does. AAC is the MP4-family lossy codec, audibly better than MP3 at the same bitrate and the default for Apple devices. That determines whether the corrected audio can be written back exactly or has to be re-encoded.
Anything specific to AAC here?
+
Yes — AAC carries encoder delay in the container, so a naive cut can leave a few milliseconds of silence that a proper trim removes. 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 AAC Loudness on several AAC 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 AAC Loudness cost anything?
+
No. Normalize AAC 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.
Is there a file size limit on Normalize AAC 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 PNG site host Normalize AAC 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 AAC 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 AAC 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 AAC Loudness rather than before it means the conversion works from the file you finally settled on.
Is Normalize AAC 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.
