Volume Normalizer

Measure a file's real loudness and normalize it to a broadcast or streaming target - with true-peak protection instead of silent clipping. Local processing, nothing uploads.

Drop an audio file here, or click to choose

MP3, WAV, AAC/M4A, OGG - decoded locally, never uploaded

Normalization done honestly

Most "make it louder" sites quietly clip or slap a limiter on your audio. This tool only ever applies clean gain: it measures integrated loudness the way platforms do (ITU-R BS.1770 with gating), computes the exact dB difference to your target, and refuses to push true peaks past −1 dBTP. When peaks are the bottleneck it says so and applies what fits. To inspect a file without changing it, use the audio analyzer; for the theory and platform table, the streaming loudness guide.

Normalizing a podcast episode? fix.fm, our sister site, can check your podcast loudness against Apple Podcasts and other targets before you publish, in your browser with nothing uploaded.

Volume Normalizer FAQ

How do I make my audio louder online?

Drop the file here, pick a loudness target, and download. The tool measures the file's integrated LUFS per ITU-R BS.1770, applies exactly the gain needed to hit your target, and exports a WAV. If full gain would push true peaks past -1 dBTP it applies the maximum clean gain instead and tells you - honest normalization, not a clipper.

What loudness should I normalize to?

-14 LUFS matches Spotify and YouTube playback level, -16 matches Apple Music, -18 is a common podcast level, -23 is the EBU broadcast standard. For music going to streaming platforms, normalizing is usually unnecessary (the platforms do it themselves) - this tool shines for podcasts, voiceovers, lecture recordings, and matching levels across a batch of files.

Why did it apply less gain than needed?

Gain moves peaks and loudness together. If your file needs +8 dB to reach the target but its true peak is already -5 dBTP, +8 dB would clip; the tool applies +4 dB (peak to -1 dBTP) and reports the shortfall. Getting the rest requires limiting/compression, which changes the sound - do that deliberately in an editor, not silently in a normalizer.

Is this the same as what Spotify does?

Same measurement, same idea: Spotify turns tracks down (and sometimes up) to about -14 LUFS at playback. The difference: this tool bakes the change into the file itself, which is what you want for podcasts, DJ sets, and anywhere no normalizer runs.

Is my file uploaded?

No - measurement and rendering happen in your browser with the Web Audio API. Nothing leaves your device, and the page works offline once loaded.