1Upload the 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 Audio file, with the dynamics inside each track left untouched.
Normalize Audio 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.
Does the source format affect normalisation?
+
It does. this format is read and written by the same streaming pipeline as everything else we support. That determines whether the corrected audio can be written back exactly or has to be re-encoded.
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.
Will Normalize Audio Loudness lower the quality of my audio files?
+
It depends on the source. Lossless input (WAV, FLAC, AIFF) is edited sample-exactly and loses nothing. Lossy input has already discarded detail once, so where the job can be done by copying the encoded stream rather than re-encoding it, that is the path taken.
Do tags and cover art survive?
+
Yes — ID3, Vorbis comments and MP4 atoms are carried across along with embedded artwork, so processed files still sort correctly in a music library.
Does Normalize Audio Loudness cost anything?
+
No. Normalize Audio Loudness is free with no account, and nothing is added to the audio. Uploads are deleted from the workers shortly after the job completes.
Which audio formats does Normalize Audio Loudness accept?
+
MP3, WAV, AAC, M4A, FLAC, OGG, Opus, WMA and AIFF. Codecs are detected from the stream rather than the extension, so a mislabelled file still works and a mixed batch is handled per file.
Why does a PDF site host Normalize Audio Loudness?
+
PDF.to exists because PDF is where documents go to be shared and the worst place to keep them while they are still being worked on, so nearly every job here is about getting something into or out of that state deliberately. A document rarely arrives in the state it needs to leave in: it is too big, in the wrong order, locked, or a scan with no text in it. Normalize Audio Loudness sits on the same upload and the same account as the conversions because those jobs turn up together.
What should I do with the result once Normalize Audio Loudness is finished?
+
The converter on this site moves documents between PDF, Word, images, plain text and eBook formats in either direction, so whatever comes out of a tool here has somewhere to go next without a second upload. Running that after Normalize Audio Loudness rather than before keeps the document structure intact through the step that is most likely to flatten it.
Is Normalize Audio 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 PDF site adds is a view on when a file should stay a document and when it genuinely wants to become something else, which is the decision most tools quietly make for you. It also starts from one fact about the format this site is named after: a PDF is an object graph, not a page image, so text stays selectable and vectors stay sharp no matter what happens to the raster content inside it.
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, nothing is read and nothing is indexed. Free accounts exist for history and batch size, not for access.
