LUFS for DJs: What Loudness Should Club Tracks Be?

Streaming taught every DJ a number — usually −14 LUFS — and the number is real, but it answers a question a club never asks. A streaming platform normalizes playback, so a target exists. A PA system does not: it plays your file at whatever level the file carries, through whatever the last DJ left on the mixer. For live DJ files, consistency across your crate matters far more than any absolute LUFS figure. Here is how the numbers actually fit together, and what to do with them.

LUFS in sixty seconds

LUFS (Loudness Units Full Scale) measures perceived loudness across a whole track using the BS.1770 method: frequency weighting that mimics human hearing, plus gating that ignores silence and quiet tails. “Integrated LUFS” is the single whole-track number everyone quotes. It is an excellent measurement — the deep comparison with the older ReplayGain system that MP3Gain uses is in ReplayGain vs LUFS. What matters here is the difference in purpose: LUFS targets were designed for broadcasters and platforms that adjust playback volume centrally. A club rig adjusts nothing.

Where −14 and −12 come from

−14 LUFS is the normalization target used by Spotify and roughly shared by YouTube and other streaming services: upload louder and the platform turns you down; the number exists so that consecutive songs on a playlist sit at one level. −12, −11, even −8 LUFS figures circulate in DJ and mastering forums as targets for club tracks — these describe how hot many commercial club masters actually measure, not a standard anyone enforces. A track mastered to −8 LUFS integrated is not “wrong” in a club; it is simply loud and heavily limited, and it will sit happily next to a −13 LUFS track only if someone or something evens out the difference at playback. On a streaming upload, the platform is that something. Live, the something is you — or your files, prepared in advance.

Can you “set” a DJ file to −14 LUFS with MP3Gain?

No — and any tool or tutorial claiming a clean conversion is rounding aggressively. MP3Gain does not measure LUFS at all; it applies ReplayGain toward its 89.0 dB reference. The two systems are cousins, not twins: different frequency weighting, and ReplayGain has no BS.1770-style gating. There is therefore no exact conversion between an MP3Gain target and a LUFS value. As a deliberately rough orientation only: material leveled to MP3Gain’s 89 dB default commonly measures somewhere in the mid-to-high teens below full scale when you check it with a LUFS meter — near the streaming neighbourhood, typically a little quieter, and varying by genre and master. Treat that as a sanity range, never as an equals sign. If a deliverable genuinely specifies a LUFS number — a recorded set going to a platform, a release, a promo — measure and set it with a BS.1770 tool; waveAlign is the DJ-focused example we compare against MP3Gain, precisely because LUFS is its native language.

What club DJs should actually optimize

Consistency across the crate. A library where every track sits within a decibel or two of its neighbours lets you mix with trims near centre and your ears on the music. This is the entire job of the pre-gig MP3Gain workflow, and it works regardless of what the shared level happens to be. Peak headroom. Whatever the loudness, files driven to the last fraction of a decibel leave the mixer and any downstream processing nothing to work with; MP3Gain’s 89 dB default plus its clipping guard keeps peaks honest, which is worth more on a big rig than two extra decibels of loudness. Knowing which destination normalizes. The same track may need no target at all for the club, −14 LUFS awareness for a streamed set, and nothing but consistency for a USB handed to the next DJ. Decide per destination instead of worshipping one number.

A practical loudness routine for working DJs

You do not need a metering lab; you need a reference and a habit. First, learn your own library’s landscape. Take ten tracks you trust — professionally mastered, recent, the ones that never surprise you — and measure their integrated LUFS with any BS.1770 meter (most DAWs and several DJ-adjacent tools include one). That range, whatever it turns out to be, is your scene’s real-world loudness: it tells you far more than a forum’s favourite number, because it describes the music you actually play. Second, level for the room, measure for the upload. Run the library through the shared-reference pass described in MP3Gain for DJs so live playback is consistent, and reserve actual LUFS targeting for artifacts that leave the booth: recorded sets, streams, promos. Two different deliverables, two different standards, no contradiction. Third, re-check after big intake. A hundred new promos can drag a leveled library’s balance sideways; a fresh analysis pass on the new folder, against the same target as the old one, restores the equilibrium in minutes.

And keep the limiter question straight: a club track that was mastered hot already had its peaks managed by the mastering engineer. Nothing in a leveling pass adds limiting, and your job is not to re-master the catalogue — it is to make the catalogue behave like one collection. Loudness wars are fought at mastering. Consistency is won at the library desk, which is where you are sitting.

The two questions DJs actually ask

“Should I normalize all my DJ tracks to −14 LUFS?” Only the copies destined for a normalizing platform. For the live library, leveling tracks to each other beats leveling them to a streaming figure — and if you do produce a −14 LUFS version of a recorded set, keep it as a separate export, never as a replacement for your working files. “My tracks measure all over the place — is that a problem?” For playback in one set, yes, and it is the fixable kind: mixed integrated readings mostly reflect different mastering eras, and a ReplayGain pass at a shared reference removes the practical problem (audible jumps) even though the files’ LUFS readings will still differ slightly afterwards, because the two systems weigh loudness differently. Close and consistent beats theoretically perfect and untouched.

One last confusion: loudness is not volume

It is worth separating two ideas the numbers blur together. Loudness, in every system on this page, is a property measured from the file — how intense the programme material is, weighted for human hearing. Volume is what the room does with it: the master fader, the limiter on the rack, the size of the PA. A DJ does not control the second and should not try to encode it into the first by mastering files ever hotter “for big systems” — big systems have amplification precisely so files do not have to. Keep files consistent and honest; let amplifiers be amplifiers.