If you’re asking what LUFS should you master to, the honest answer is that there is no single number to hit. For most streaming releases, mastering somewhere between -9 and -14 LUFS integrated, with a true peak ceiling of -1.0 dBTP, keeps your track competitive without flattening it.
The -14 LUFS figure you’ll see everywhere is a playback reference, not a mastering instruction. Spotify, Tidal, YouTube and Amazon Music simply turn the volume up or down so tracks sit near -14 LUFS on playback. They do not compress your master, and there is no penalty for delivering something louder.
What actually decides your target is genre, the dynamics of the track, and where it will be heard. A drum and bass master and a solo piano record need very different numbers, even though a lot of online advice skips that part.
Table of Contents
- LUFS vs. dBFS: What Are You Actually Mastering To?
- What LUFS Should You Master To for Streaming?
- Which LUFS Target Should You Choose?
- How Do You Measure LUFS in a DAW?
- A Practical LUFS Mastering Workflow
- Why Does Your LUFS Reading Change During Mastering?
- Common LUFS and Mastering Mistakes
- Frequently Asked Questions
- Conclusion
LUFS vs. dBFS: What Are You Actually Mastering To?
LUFS (Loudness Units Full Scale) measures how loud a piece of audio feels, weighted to match human hearing across different speakers and listening levels. Zero LUFS is digital full scale, and the number gets more negative as things get quieter.
dBFS, by contrast, measures the raw digital signal level with no perception weighting at all. A waveform peaking at -1 dBFS is simply the loudest possible sample value in your file. It says nothing about whether the track will sound loud next to another track.
That gap is the whole reason LUFS exists. It was standardized in ITU-R BS.1770 and popularized for broadcast under EBU R128, which sets a programme target of -23 LUFS. Loudness normalization then carried the same idea to streaming.
A useful third measurement sits alongside both: true peak, reported in dBTP. It accounts for inter-sample peaks that exist between your actual samples, which is what a lossy codec reconstructs and can cause to clip on playback.
| Measurement | What it reads | Window | Why it matters |
|---|---|---|---|
| LUFS-M (momentary) | Perceived loudness right now | 400 ms | Shows how loud the track feels in any instant |
| LUFS-S (short-term) | Perceived loudness of a passage | 3 seconds | Useful for checking that a chorus is not way out of line with the rest |
| LUFS-I (integrated) | Average perceived loudness of the whole track | Full duration, gated | This is the number platforms use and the one you set a target for |
| True peak (dBTP) | Highest level including inter-sample peaks | Instantaneous | Keeps your master clean through lossy transcoding |
| RMS | Average signal energy, no perceptual weighting | Full duration | The alternative framing some engineers still use, roughly -9 RMS landing near -11 LUFS |
When someone asks “is LUFS integrated or short-term,” the answer is that you set the target in integrated, and you watch short-term to keep the track internally consistent.
What LUFS Should You Master To for Streaming?
For a modern streaming release, aim for the top of the range that your genre supports. Roughly -9 to -12 LUFS integrated covers most pop, rock, hip-hop and electronic music, and anything louder than about -6 LUFS is difficult to keep clean without obvious pumping.
Deliver a 24-bit WAV at the sample rate you mixed in, and stay at one sample rate across the whole project. Some engineers hand in 32-bit float for extra headroom with lossy sources; either is fine, as long as it is a real file and not a session reference.
Streaming Targets at a Glance
| Platform | Normalization reference | Useful peak ceiling | Delivery format | Caveat |
|---|---|---|---|---|
| Spotify | -14 LUFS | -1.0 dBTP | 16/44.1 or 24-bit WAV | The web player does not normalize, so A/B comparisons there mislead you |
| Apple Music | -16 LUFS | -1.0 dBTP | 24-bit WAV | Apple has suggested 1 dB of true peak headroom on delivery |
| YouTube | Around -14 LUFS | -1.0 dBTP | WAV or high bitrate | Users can normalize manually in settings, so relative level still matters |
| Tidal | -14 LUFS | -1.0 dBTP | 16/44.1 or 24-bit WAV | HiFi tier adds SONY 360RA headroom playback, which rewards clean masters |
| Amazon Music | -14 LUFS | -1.0 dBTP | WAV accepted | Normalization setting defaults on for most listeners |
| Deezer | Around -15 LUFS | -1.0 dBTP | WAV accepted | Normalization is a user preference and defaults on |
| YouTube Music | No normalization | -1.0 dBTP | WAV accepted | Your level is heard exactly as delivered |
| Bandcamp and SoundCloud | No normalization | -1.0 dBTP | WAV or FLAC | The reason a -14 master can feel quiet on a direct link |
These are production references, not promises. Platforms change their normalization behaviour, and the best practice is to master for how the music sounds rather than for the number on a help page.
One fear comes up constantly: does delivering louder than -14 LUFS trigger a penalty? No. Normalization only attenuates playback volume. It never applies dynamic range reduction, and a louder master simply gets turned down a little more. The r/mixingmastering community documentation on this is blunt about it, and it matches how Spotify and Apple describe their own systems.
Which LUFS Target Should You Choose?
Choose a target from the genre the track lives in, then let the track’s own dynamics set the exact number inside that range. If two songs in the same genre measure differently, that is information, not a mistake.
What LUFS to Master To by Genre
| Genre or style | Typical integrated LUFS | True peak ceiling | Notes |
|---|---|---|---|
| Pop | -9 to -11 | -1.0 dBTP | Top end of the range keeps vocals forward without fighting the mix |
| Hip-hop | -8 to -10 | -1.0 dBTP | Beats carry a lot of low-end weight, which reads quieter on LUFS |
| EDM | -7 to -9 | -1.0 dBTP | Sidechain-pumped kick supplies micro-dynamics, so loud still feels energetic |
| Rock and metal | -8 to -11 | -1.0 dBTP | Djent and modern metal often sit near the loudest end by choice |
| Acoustic and folk | -13 to -16 | -1.0 dBTP | Room and instrument dynamics are the point |
| Jazz | -15 to -18 | -1.0 dBTP | Leave space; a compressed master sounds wrong here |
| Classical | -18 to -24 | -1.0 dBTP | Integrated loudness barely predicts perceived loudness for this repertoire |
| Ambient | -19 to -23 | -1.0 dBTP | Long quiet passages drag the average down, which is expected |
Classical and ambient figures show how far apart tracks can sit. A single -20 LUFS reading might be a very loud piece of chamber music or a genuinely quiet ambient record, and LUFS alone will not tell you which.
Non-music targets worth knowing
| Delivery | Target integrated LUFS | Peak ceiling | Notes |
|---|---|---|---|
| Podcast and voiceover | -16 LUFS | -1.0 dBTP | A common platform spec; consistency between episodes matters more than the exact number |
| Spoken-word audiobook | -18 to -23 | -1.0 dBTP | Listeners often raise the level, so extra headroom helps |
| TV broadcast | -23 LUFS | -1.0 dBTP | EBU R128, with variations per territory and broadcaster |
| Film trailer and cinema | -14 to -18 | -1.0 dBTP | Trailers deliberately sit hot, then get pulled back for the feature |
Genre expectation beats the platform number
Reference tracks still work, provided you level-match them. A cheap loudness meter on your monitor controller, or a plugin like MetricAB, REFERENCE or ListenHub, lets you switch between your master and a reference without your ears being fooled by level.
For trustworthy references, pull lossless versions from Qobuz, ProStudioMasters or HDTracks rather than comparing against a heavily compressed stream.
Micro dynamics and macro dynamics are the deciding factors. Micro dynamics are the small changes inside a sound: note velocity, breath, pick attack. Macro dynamics are the movement between quiet and loud across a track. A master can be loud and still full of both, as vi-control veteran Joël Dollié has argued at length; crushed masters destroy them first.
Dolby Atmos changes the decision
When an album is delivered in Atmos, an over-limited stereo master becomes a problem. Heavy stereo limiting fights the object-based mix, and the two versions end up sounding like different records. Several engineers on vi-control treat Atmos delivery as a reason to back the stereo master off by a decibel or two.
Matching across an album
Streaming preserves the level relationship between tracks on an album, so a quiet second track stays quiet beside a loud opener. Keep the loudness of an EP consistent track to track, even if each individual song has its own target.
How Do You Measure LUFS in a DAW?
You do not need a hardware meter. Every major DAW can show integrated, short-term and momentary loudness, and most of them can show true peak too.
Ableton Live 12
In Live 12, use the meter options in the View menu to add loudness readouts to the master track meters, where LUFS-M, LUFS-S and LUFS-I appear next to peak and RMS. Names moved slightly between point releases, so check the View menu rather than hunting through the device chain. For a true peak readout, add a utility or limiter device on the master and read its true peak indicator.
Logic Pro
Logic Pro’s audio meter handles LUFS directly. Use the meter options in the View menu to add LUFS-I, LUFS-S, LUFS-M, RMS and true peak in dBTP, then widen the meter window so the short-term history is visible. The Adaptive Limiter on the master bus gives you a ceiling control and a true peak readout in the same place.
FL Studio 2025
FL Studio 2025 exposes loudness readouts on the master mixer insert meters, including LUFS-I alongside peak and true peak. If your build does not show them, a free loudness meter plugin gives you the same numbers without changing your signal path.
Whichever DAW you use, play the track from start to finish once before you touch anything. The integrated value only settles after the whole file is read, and gating means silence at the start or end still counts toward the measurement.
A Practical LUFS Mastering Workflow
- Clean the mix first. Fix clicks, noise and build-up. Restrictive mixing makes the mastering chain work harder than it needs to.
- Pick a genre target. Choose a number from the table that fits the style, and treat it as a landing point rather than a law.
- Set your limiter ceiling. -1.0 dBTP is the streaming standard. If the material is going through heavy lossy transcoding or older gear, -2.0 dBTP buys safety.
- Bring it up gently. Use slow-ish attack on the limiter so transients survive. If you can hear the gain reduction moving with the kick, you are working too hard.
- Watch short-term loudness. Passages that sit 4 LU or more away from the rest of the track usually mean the mix, not the master, is unbalanced.
- Level-match a reference. Switch between the reference and your version at matched loudness. If your track sounds thin there, no amount of extra output will fix it.
- Check true peak on the final file. Re-open the exported bounce and meter it. Limiter readouts lie in their own meters more often than engineers like to admit.
- Export in a clean format. 24-bit WAV at your project sample rate, no dithering, no limiting on the way out twice.
On a mix bus rather than a master bus, a rough working level of -6 dBFS peak gives the mastering engineer room to work without you handing over a track that is already crushed.
Why Does Your LUFS Reading Change During Mastering?
Because LUFS is measured, not set. A meter is reporting what the audio is doing at that moment, and mastering changes the audio continuously.
Several effects stack up. Gating is the big one: the measurement ignores sections below a relative threshold, so adding a quiet intro or a long silence at the end will move the integrated value even if the loud parts never changed.
Short-term versus momentary is another source of confusion. Momentary reads a 400 ms window, short-term reads three seconds. A big snare hit spikes the momentary reading and barely registers on short-term, which is why watching only momentary makes masters look erratic.
Dynamic range changes matter too. Crushing transients raises short-term loudness across the board, which pushes the integrated value up without making anything sound better.
Finally, the LUFS algorithm sums channels with weights, so a mono fold-down of a wide stereo mix can read differently from the stereo file. Check the file you are actually delivering, not the mix bus before the renderer.
Measure across the full track rather than a single moment. A ten-second excerpt will not give you the integrated number you need, and the reading will drift as the track plays.
Common LUFS and Mastering Mistakes
Trying to match the raw loudness of references. Two tracks at the same LUFS can sound completely different. Level-match, then compare tone and balance, and always judge with normalization off so you are not comparing two different volume jumps.
Treating dBFS as a loudness target. Peak level is a ceiling, not an average. A track peaking at -3 dBFS could be quiet or loud depending on how much of it is at that level.
Clipping before limiting. If the signal is already flat-topped, a limiter has nothing left to control and the distortion is baked in.
Compressing to fix a balance problem. Heavy compression raises loudness and removes punch at the same time. Fix the mix instead, and use gain staging to get closer to the target before any dynamics processing.
Applying one genre’s number everywhere. Producers on r/trapproduction commonly work between -9 and -12 while showing tracks, and hold back further when they want the limiter to do real work later. That is a deliberate choice, not a contradiction.
Checking only the first thirty seconds. Chorus weight, breakdowns and outros all change the integrated reading. Judge the whole file.
Assuming quiet means wrong. A -14 master will sound quieter than a hot one on YouTube Music, SoundCloud or the Spotify web player, because those do not normalize. r/audioengineering posters put it plainly: LUFS is a broadcast standard, and consistency matters more than the number.
Over-correcting after the loudness war. The backlash against crushed masters, from Death Magnetic onward, has pushed some artists to masters that are far too quiet. You are allowed to be loud without being ruined.
Frequently Asked Questions
Should I master every genre to the same LUFS level?
No. A drum and bass track and a solo piano piece with the same integrated reading will not feel equally loud. Use the genre table as a starting range, let the track’s dynamics decide where inside that range you land, and keep the loudness consistent across the tracks on the same album.
Is -14 LUFS loud enough for streaming?
It is quiet rather than wrong. Since Spotify, Tidal, YouTube and Amazon Music normalize toward -14 LUFS, a master at that level gets turned up on playback, so it will never sound louder than its neighbours. On players that do not normalize, such as YouTube Music or SoundCloud, it will sound exactly as loud as you made it.
What LUFS target should I use for a hip-hop master?
Most hip-hop releases land between -8 and -10 LUFS integrated with a -1.0 dBTP ceiling. Kick and sub weight make a beat read quieter on the meter than it sounds, so do not panic if the integrated number is lower than a pop master. Keep your true peak in check and let the low end stay intact.
Does mastering to -14 LUFS remove the need for a limiter?
No. Integrated loudness and peak level are different measurements, and a track can average -14 LUFS while containing inter-sample peaks that clip once a lossy codec reconstructs them. Use a limiter to hold true peak at -1.0 dBTP, or -2.0 dBTP if the master will pass through heavy transcoding.
Should I deliver the same master to Spotify, Apple Music, and YouTube?
In most cases yes. One master at roughly -9 to -12 LUFS integrated with a -1.0 dBTP ceiling works across all three, because each platform adjusts playback volume to its own reference. Apple suggests about 1 dB of true peak headroom on delivery. If you need a version hotter for direct-to-listener platforms, make it as a separate alternate, not a replacement.
Conclusion
Start by picking a realistic integrated target for your genre, somewhere in the -9 to -14 LUFS range for most streaming music, and set your true peak ceiling at -1.0 dBTP. Keep the dynamics of the mix intact, compare level-matched against a reference you trust, and meter the exported file before you send it anywhere.
That is the practical answer to what LUFS should you master to in 2026: not a single number, but a genre-appropriate target, a clean peak, and a master that still sounds like music.
