Edit audio · Local tool

Audio Normalizer

Normalize to Spotify, YouTube, podcast or broadcast loudness — or peak-normalize to a target dBFS. Runs entirely in your browser.

Drop a file here or browse

MP3, WAV, FLAC, M4A, OGG — processed locally, never uploaded

About this tool

What it does

Recordings from phones, social apps, and old rips often sit at uneven levels. Audio Normalizer adjusts gain so the signal reaches a target loudness using either peak or RMS measurement. Peak mode scales to a maximum sample level — useful when you want to avoid digital clipping while using full headroom. RMS mode aims at average energy, which can feel more natural for music with varying dynamics. Like the other edit tools here, normalization is pure client-side DSP: your audio is not sent to a remote API.

Peak vs. RMS audio normalization

Audio normalization adjusts gain to bring a recording toward a chosen level. Peak normalization measures the largest sample value and is useful for setting a ceiling. RMS normalization measures average signal energy and can make material with different average levels feel more consistent, although it is not the same as perceptual loudness or LUFS mastering.

Normalization applies gain; it does not repair distortion or dynamically compress loud sections. If the requested RMS target requires excessive gain, peaks may reach the digital ceiling and be clipped. Use a conservative target and listen to the exported WAV before replacing or sharing your original.

Set a useful level without changing the performance

Normalization applies a gain adjustment to the entire clip. It can make a quiet recording easier to hear or help bring several files closer to a common level, but it does not automatically even out every loud and quiet moment the way compression or automation would. The original dynamics remain largely intact unless clipping occurs.

Choose a target with enough headroom for the next stage of your workflow. Peak normalization is a straightforward ceiling-based option, while RMS gives an average-energy measurement. Because perceived loudness also depends on frequency balance and dynamics, always audition the processed version instead of relying on a number alone.

Workflow

How to use it

01

Load the clip

Choose the file whose level feels too quiet, too hot, or inconsistent with other material.

02

Pick Peak or RMS

Peak is safer against clipping; RMS is closer to perceived loudness for sustained music.

03

Set the target level

0 dB is maximum for peak-style targets. Slightly lower targets leave a margin if you will process further.

04

Apply and compare

Render the normalized buffer, play it back, and download when the level feels right.

Tip: Leave a little headroom if you plan to apply EQ or other processing afterward, and keep the original file as a reference.

FAQ

Questions about Audio Normalizer

01Is this the same as loudness normalization (LUFS)?+

Yes — this tool measures integrated loudness with a K-weighted, gated method in the spirit of ITU-R BS.1770 / EBU R128, then applies the gain needed to hit your target (for example −14 LUFS for Spotify or YouTube). You can also switch to peak mode when you only need to bring the loudest sample to a dBFS target.

02Can normalization fix distortion?+

No. If the recording was already clipped when it was captured, raising or lowering level will not restore missing peaks. Normalization only changes gain; it does not repair distortion, noise, or limiting that is already baked into the file.

03Should I normalize before recognition?+

It can help when a file is extremely quiet and hard to hear, but clean signal and a focused 10–20 second section usually matter more than absolute loudness. If the platform already applies its own loudness normalization, matching −14 LUFS is mainly useful for consistent playback and sharing.

04Why does the level still sound uneven?+

Integrated LUFS is an average over the whole file. Tracks with huge dynamic swings — quiet verses and very loud choruses — can still feel uneven after a single gain change. For those cases, use compression or manual automation in addition to normalization.

05What LUFS target should I use?+

Spotify, YouTube, Tidal, Amazon Music, and most short-form video apps aim around −14 LUFS. Apple Music and many podcasts sit near −16 LUFS. European broadcast (EBU R128) uses −23 LUFS. Pick a platform preset or set a custom target with the slider.

06What does Prevent clipping do?+

When the calculated gain would push sample peaks above −1 dBFS, Prevent clipping caps the gain so the output stays safe. You may then land slightly quieter than the LUFS target — the summary panel shows the actual gain applied so you always know what changed.