BLOG

Trap mastering loudness: what 817 tracks show

How loud trap uploads are before mastering and where they land after, with median LUFS and true peak from 817 tracks, and what that means for a trap master on streaming.

Trap is close to hip-hop in level, but the way it is built makes the loudness work different. Long sub-bass notes, sparse drums and hard-hitting 808s take up most of the headroom, and the quiet intros and breakdowns sit far below the drops. If you are searching for trap mastering loudness, this article gives the numbers first and then a method for checking your own track. The figures are numbers from 817 tracks processed by the mastering engine behind Echoteka in the last six months (aggregate, no personal data).

What the numbers show

Reading Trap, 817 tracks
Median loudness before mastering −13.2 LUFS
Middle 80% of uploads (10th to 90th percentile) −17.7 to −8.7 LUFS
Uploads louder than −10 LUFS before mastering 18%
Median loudness after mastering −14.0 LUFS
Median true peak after mastering −1.0 dBTP

Two things stand out. The median upload is a little louder than the −14 LUFS reference, and the spread is wider at the quiet end than in hip-hop. One trap upload in ten was quieter than −17.7 LUFS. The numbers do not say why, but a long, sparse intro or an unbalanced demo would produce a quiet reading like that. The engine brings the median to −14.0 LUFS and the median true peak to −1.0 dBTP.

These are medians of two separate sets of measurements, before and after. They show the starting point and the end point for this genre. They do not show how much any one track changed.

To place your own trap track against these figures, measure it with the same meter. If it reads between −17 and −12 LUFS, it is in the middle of the range, and a master to −14 LUFS is a moderate move. If it reads louder than −10 LUFS, it belongs to the group that made up 18% of the sample. The master will bring it down, and the 808 is the first thing to check, because it usually sets the true peak. If it reads quieter than −17.7 LUFS, it is in the bottom tenth. Look at the loudest sections first: if the drops are at a normal level and only the intro is quiet, the track is fine as it is. If the whole file is quiet, the gain was set too low before mastering. The true peak is the second number to read, and it should be checked again after the final file is exported.

What the targets mean for a trap master

Spotify publishes a target of −14 LUFS for integrated loudness, and many streaming services use a similar reference. A trap master near that figure keeps the most of its dynamics after the platform's volume adjustment. If the master is much louder, the platform turns it down, and the 808 and the kick, which are the first things to suffer from heavy limiting, lose their punch.

The true peak target is at or below −1 dBTP. Trap masters are prone to overshoot after encoding, because the sub-bass is dense and the peaks are high. A median true peak of −1.0 dBTP in our data means the engine stays at the limit. Your own master should leave the same margin, and the margin should be checked after the file is exported, not only inside the DAW.

For Apple Music, third-party measurements put playback near −16 LUFS. Apple does not publish that figure as a target, so treat it as a reference, not a rule.

Checks before you master a trap track

  1. Measure the true peak of the bass alone. Solo the 808 and the sub, and read the true peak. If it reaches −1 dBTP or higher on its own, the rest of the mix will be pushed down to make room, and the track will sound flat.
  2. Measure the quiet sections. Read the loudness of the intro and the breakdown separately. A trap track with a very quiet intro and a loud drop is normal, but the drop should not be so loud that the intro becomes unusable when the file is turned down on playback.
  3. Check the hi-hats and snares at the new level. A limiter can smear fast hats and rolls. Listen to a section with fast hi-hat patterns after mastering and compare it with the bounce.
  4. Use the same meter for every version. Keep a note of integrated loudness and true peak for each bounce, so you can see which change moved the number.
  5. Check the mono sum. A heavy sub-bass that is wide in stereo can lose level when it is summed to mono, and that is the kind of change that shows up on a phone speaker.

Common mistakes in trap mastering

Where to start

Measure the bounce with the free LUFS checker. It shows integrated loudness and true peak, which are the two numbers this article is about. If the track is far from the reference, a free AI mastering pass can bring the level to a streaming target, and you can measure the result to confirm the change.

If you want to understand why very loud trap masters lose on streaming, read what the loudness penalty on streaming is.

FAQ

What LUFS should a trap master be?

For streaming, aim for about −14 LUFS integrated and a true peak at or below −1 dBTP. In our measurements, the trap median after mastering was −14.0 LUFS and −1.0 dBTP.

Why is my trap track so quiet in the intro?

The intro is often sparse, so its integrated loudness is much lower than the drop. A short section of low level does not hurt the overall loudness, but if the whole track is quiet, the level is set too low. Measure the full file, not only the intro, before you decide.

Can I use a loud 808 and still hit −14 LUFS?

Yes, if the sub-bass is tamed before the limiter. Check the true peak of the bass alone. If the 808 is the only thing that reaches the ceiling, shape its peaks first, then master the full mix.

Measure your trap beat before you release it

The LUFS checker is free and needs no account. Measure the bounce first, then decide whether it needs a master.

Master a track free