Match volume across songs

Normalize a set of tracks to the same perceived loudness (-14 LUFS, the common streaming target) so nothing jumps out. Local processing, no upload.

Loading tool…

Loudness matching measures the integrated loudness of each track in a batch and applies a single gain offset so every file lands on the same perceived-loudness target. It relies on LUFS (Loudness Units Full Scale), a K-weighted measurement that models how the ear actually hears level, rather than raw sample peaks or a flat RMS average. This matters for Suno output because every generation renders at its own internal loudness, so a folder of AI songs can easily swing several LUFS from one track to the next.

You reach for a volume matcher when you're assembling those songs into something meant to be played back to back — an EP, an album, a long mix, or a playlist — and you don't want listeners riding the volume knob between tracks. Matching to a shared target keeps the set cohesive and puts the relative balance in your hands. Streaming services apply their own playback normalization on top, so matching first sets the intended relationship between your songs instead of leaving each platform's algorithm to sort it out.

How it works

  1. 1

    Drop all the tracks you want leveled.

  2. 2

    Click normalize — each track is analyzed and adjusted to -14 LUFS.

  3. 3

    Download each leveled track individually.

When to use it

  • Prepping a multi-song EP or album of Suno tracks for distribution through DistroKid or CD Baby so the volume doesn't jump when someone plays it start to finish.
  • Leveling clips generated across different sessions before stitching them into a long-form YouTube compilation like a 'one hour of' mix.
  • Balancing a batch of tracks for a continuous SoundCloud playlist or a back-to-back preview reel so no single song blasts out over the others.

FAQ

Why -14 LUFS?

It's the reference level most streaming platforms normalize toward, so mastering to it keeps your tracks consistent with everything else in a playlist.

Is this the same as peak normalization?

No. Peak normalization only looks at the loudest sample; LUFS matches perceived loudness, which is what makes tracks feel equally loud to a listener.

Will it distort quiet tracks that get boosted?

The normalizer also enforces a -1 dB true-peak ceiling, so boosted tracks won't clip.

What's the difference between LUFS and RMS when measuring loudness?

RMS is a flat average of signal energy, while LUFS applies K-weighting — a frequency curve that approximates human hearing — and gates out silent gaps so they don't drag the reading down. Two tracks can share the same RMS yet sound clearly different in loudness, which is why LUFS became the standard streaming platforms measure against. Matching by LUFS lines up perceived loudness, not just raw energy.

Should I loudness-match before or after mastering my tracks?

After. Do any EQ, compression, or mastering on each song first, then run loudness matching as the final step on the finished files. Matching only sets the overall level, so if you master afterward you would change the loudness again and undo the alignment.

Is matching loudness the same as making everything louder with a limiter?

No. Matching applies a level offset per track toward a shared target, so quieter songs come up and louder ones actually come down. A limiter instead pushes loudness by clamping peaks and adding compression, which changes the sound of the track itself. Loudness matching leaves each song's character intact and only aligns how loud they sit relative to one another.

Related tools