Audio Normalizer
Normalize audio by its loudest peak: see the lift in decibels before you press, pick a headroom preset, and download a copy that lands on the target.
The recording
Track
Drop a quiet recording
MP3, WAV, M4A, OGG or FLAC · one at a time
—
—
The lift
Pick a track and the peak it already has decides how far it can rise.
Bringing the level up
- Drop the quiet file on the Track box. The waveform draws at the level the file really has, a dashed rule marks its loudest sample, and Loudest moment moves the player to just before it, which is worth a listen, because whatever is loudest in there decides how far everything else can rise.
- Type a target peak or press a headroom preset. The lift under the controls reads the gain in decibels, the peak before and after, and the number every sample gets multiplied by, and it changes as you edit.
- Pick M4A, WAV, Opus or FLAC, then press Normalize. A bar counts the encode with Cancel beside it; when it lands, switch between the Original and Normalized takes to hear the difference, then press Download.
About this tool
A recording that sounds fine on your headphones and vanishes on someone else's phone usually has one thing wrong with it: its loudest moment sits well below full scale. Peak normalizing is the fix. The tool finds the single biggest sample in the file, works out what it would take to lift that one sample to your target, then multiplies every sample by the same number. Nothing about the balance of the recording shifts. All of it moves together.
Target peak is a percentage box that steps in whole numbers between 1 and 100, with the headroom presets beside it doing the conversions for you: Full is 100, and −1, −2, −3 and −6 dB are 89, 79, 71 and 50. It starts on 89, about a decibel under full scale, because a file pinned at 0 dBFS has nowhere to go once the next encoder or edit adds gain. Type your own number and the preset lets go of it. The lift is worked out the moment the file lands, so the decibels and the multiplier are on the page before you press anything.
Output goes to M4A, Opus, FLAC or WAV, the choice is remembered for next time, and the copy keeps your file's name with -normalized added. The WAV writer works at 16-bit, keeping whatever sample rate the source had, and the other three get encoded from that same 16-bit copy, which makes this a good step for voice notes, lecture audio, podcast rough cuts and samples, and the wrong step for finishing a master. Matching several clips is a matter of running each one at the same target. Recorded in the Voice Recorder, trimmed in the Audio Cutter, normalized here: that is the order I use.
Good to know
- One loud moment decides the whole file. A cough, a door, a knuckle on the desk: whichever sample is biggest gets lifted to your target, and the speech underneath rises by that same modest amount. Cut the spike out in the Audio Cutter and run it again to see how much difference it makes.
- Peak is a different quantity from loudness. Two files normalized to 89 can still feel unequal, because ears average energy over time while a peak meter reports one instant. Streaming platforms measure LUFS, and this tool has nothing to say about landing on -14.
- Dynamics come out exactly as they went in. There is no compressor and no limiter here, so the gap between the quietest passage and the loudest one is the same gap it always was.
- Distortion already baked into a recording stays baked in. Lifting the level carries the damage up with everything else.
- Every export is written at 16-bit, FLAC included, and a lossy source picks up one more encode on the way out. That is fine for a voice memo. It is the wrong place to prepare audio for a mastering engineer.
Frequently asked questions
How much louder does this actually make a quiet recording?
As much as the headroom allows, and the sum is easy to do in advance. The gain is your target divided by the current peak. A take whose loudest sample sits at 0.2, which is roughly -14 dBFS, normalized to 89 gets multiplied by about 4.5, a lift of nearly 13 dB. Room hiss and breath noise come up by that same 13 dB, and that is the part people forget.
Should I use 100, or leave a bit of headroom?
100 is fine for something you are about to listen to once and delete. Anything with another step after it wants 89. A file sitting at exactly full scale has no room left for the next encoder, and lossy formats can reconstruct a sample slightly above where it started, which is where crackle on playback tends to come from.
Why is my file still quieter than a song on Spotify?
Commercial masters are compressed and limited before release, which drags their average level up close to the peak and holds it there. Peak normalizing moves the single loudest sample to your ceiling and leaves the average exactly where it was. Same peak, wildly different perceived loudness. Closing that gap takes a limiter, which this page deliberately does without.
I ran it and the result sounds identical. What happened?
Look at the lift before you press. A gain of a decibel or two is a real change but a small one, and at a comfortable listening level it can pass unnoticed. A file already within 0.05 dB of the target, or silent the whole way through, never gets that far: Normalize stays off and the page says why, since the copy would be the same file encoded again.
Missing something in Audio Normalizer? Suggest a feature →
Tell someone who needs this.