Loud enough to sound finished, and no louder. Many streaming services play every track at about the same loudness, so a master pushed past their target is just turned down, and the extra limiting only costs you punch. Measure integrated loudness against the target where your track will play, and leave true-peak headroom, around −1 dBTP, for the encode.
What loudness normalization does
A service that normalizes measures each track's integrated loudness, in LUFS, and turns it up or down to its playback level. Loud masters get turned down by the difference. So a heavily limited master plays back at the same level as a dynamic one, minus its peaks.
Targets differ from service to service and change over time, so check the one you deliver to rather than memorizing a number.
Measure against your target
Gaugex is a loudness meter. Pick where the track will play in Platform Target, play the whole track, and read the Integrated number against the target.
MATCH then sets Gain Trim so the track hits that target. You hear your master at the level listeners will, next to other tracks at the same level. If it sounds flat or squashed there, back off the limiter.
Leave headroom for the encode
Streaming services play a lossy encode, not your WAV, and encoding can push peaks between samples above 0 dBFS even when the file doesn't clip. A true-peak ceiling leaves room for that.
In Clampit, turn on TRUE PEAK and set Ceiling to −1.0 dB for streaming. Gaugex's CEIL adds an optional true-peak ceiling at −1 dBTP if you only want a safety stop at the end of the chain.
Compare at matched loudness
Louder always sounds better at first, so judge the limiter at the same level. Clampit's LINK turns the output down by the amount you add with Input, and its BYPASS is loudness-matched. Push the limiter only as far as it still sounds better at the same loudness.
Frequently Asked Questions
What LUFS should I master to for streaming?
There's no single number. Each service has its own playback target, and a master louder than it is turned down. Check the target where you deliver, master for the sound, and make sure it holds up when played at that level.
Why does my track sound quieter after upload?
The service turned it down to its playback level. The loudness you pushed for disappears, and the lost dynamics stay. The Clampit manual FAQ shows how to hear that trade before you export.
Do I need a true-peak limiter for streaming?
It helps. Encoding can push peaks above 0 dBFS even when the WAV is clean. A true-peak ceiling around −1 dBTP leaves room for it.
Is a quieter master worse?
Not on a service that normalizes. A master below the target may be turned up or left as it is, depending on the service. What matters is how it sounds at the playback level.
Plugins in this post
- GaugexFree: measures integrated loudness against a playback target and previews your master at that level (MATCH)Manual: Platform Target · MATCH · CEIL
- ClampitFree: a true-peak limiter with a loudness-matched bypassManual: Ceiling · TRUE PEAK · Loudness normalization
This tip uses Gaugex 1.1.1 and Clampit 1.1.0. Some steps may differ, or not apply, if you're on a different version. Tried this workflow, or got stuck along the way? We'd love to hear from you: contact us.