Guide
What Is LUFS? Loudness Standards Explained
Marc Aaron Jacobs
Founder, DropCue · Composer
LUFS is the standard that decides how loud your music actually sounds after streaming platforms normalize it. Here is what the measurement means, where it comes from, and why composers and producers chasing sync placements and clean streaming masters should care.
Who this is for
If you have ever bounced a track that sounded huge in your DAW, uploaded it to Spotify, and wondered why it came back quieter than the song before it, you have run into LUFS. This page is for composers, producers, beatmakers, and anyone delivering music to streaming platforms or sync libraries who keeps hearing the term "LUFS" thrown around in mastering threads and delivery specs without a straight definition.
It is also for the working composer staring at a sync brief that says "deliver at -14 LUFS integrated, true peak under -1 dBTP" and quietly Googling what that actually means before replying to the music supervisor. You are not alone, and you are not behind. Loudness metering went from a niche broadcast concern to a daily reality for everyone uploading audio, and most of us learned it on the job.
Quick definition up top, because that is probably why you are here: LUFS stands for Loudness Units relative to Full Scale. It is a measurement of perceived loudness, how loud audio actually sounds to human ears, standardized so that a number on your meter means the same thing across every platform, country, and engineer. Higher (closer to zero) means louder. So -9 LUFS is louder than -14 LUFS.
The audience-specific reality
What makes LUFS different from the old way of measuring level is that it models human hearing instead of just raw signal. For decades engineers chased peak meters and RMS, but neither one tells you how loud a track feels. A heavily compressed track and a dynamic one can hit the exact same peak and sound wildly different in volume. LUFS fixes that by applying a frequency weighting (the "K-weighting" curve) that approximates how our ears actually respond, then integrating loudness over time.
There are three flavors you will see on a meter, and the difference matters. Momentary LUFS measures a 400 millisecond window, useful for catching the loudest instant. Short-term LUFS measures a 3 second window, good for tracking how loud a section feels. Integrated LUFS measures the entire track from start to finish as one number, and this is the value streaming platforms and sync libraries care about most. When a spec says "-14 LUFS," it almost always means integrated.
Then there is true peak, measured in dBTP (decibels true peak). Regular sample peak meters miss the inter-sample peaks that appear when a digital signal is reconstructed into analog on playback. A track can read -0.1 dBFS on a normal peak meter but actually overshoot 0 dBTP after conversion, causing clipping on the listener's device. That is why delivery specs pair a loudness target with a true peak ceiling, typically -1 dBTP, to leave headroom.
The standards behind all of this are real and worth knowing. ITU-R BS.1770 is the International Telecommunication Union recommendation that defines exactly how to measure loudness and true peak. EBU R128 is the European Broadcasting Union standard built on top of it, originally for broadcast, that popularized the integrated LUFS target. Streaming platforms then adopted their own normalization targets: Spotify and YouTube normalize around -14 LUFS, Apple Music around -16 LUFS. Upload louder than the target and the platform turns you down. Upload quieter and some platforms turn you up (or leave you sounding small next to everyone else).
Why DropCue fits this workflow
Here is the practical problem LUFS creates for working composers. To actually know your track's integrated LUFS, true peak, and whether it will get penalized by streaming normalization, you traditionally need a loudness meter plugin running on a master bus, a separate spectrum analyzer, and a mastering chain or service to fix whatever the meter tells you is wrong. That is three or four tools, none of which live where your catalog lives, all of which you bounce between for every single track. A dedicated loudness checker can give you the number, but it still does not fix anything.
DropCue collapses that. Your catalog already lives in DropCue, so the loudness measurement and the fix both happen on the same files you are already pitching and sharing. AI Mix Analysis, powered by ROEX, gives you a diagnostic read on any track in your library: integrated LUFS measured to ITU-R BS.1770, true peak, clipping detection, stereo width, mono compatibility, phase, and tonal balance, plus plain-language AI recommendations on what to fix and how. You do not have to interpret a raw meter; it tells you in words.
Then AI Mastering, powered by Chosen Masters, lets you actually hit a target. Pick a style (Modern, Open, or Powerful), master in seconds, and A/B the before and after loudness-matched, with a moving waveform and the same studio analytics (integrated LUFS to ITU-R BS.1770, true peak and inter-sample peaks, dynamics, L/R correlation, EQ). Loudness-matched A/B is the honest way to compare, because without it everything louder just sounds "better" to your ear. So you measure with Mix Analysis, you target with Mastering, and you never leave the platform your music is already on.
One honest caveat we build into the read: for lossy or compressed source files (MP3, AAC), loudness and peak readings can be slightly skewed compared to the original WAV or FLAC, so those are flagged as approximate. Real meters do not pretend a 128 kbps MP3 measures identically to a master WAV, and neither do we.
The features that matter most
✓ AI Mix Analysis (ROEX)
Reads integrated LUFS to the ITU-R BS.1770 standard, plus true peak, clipping, stereo width, mono compatibility, phase, and tonal balance on any catalog track. This is the tool that answers 'what is my track's LUFS' without a separate meter plugin, and explains the number in plain language.
✓ AI Mastering (Chosen Masters)
Once Mix Analysis tells you a track is too quiet, too loud, or clipping, Mastering lets you target a clean loudness with a Modern, Open, or Powerful style in seconds. Use it to get masters that sit right against streaming normalization instead of getting turned down.
✓ Loudness-matched A/B comparison
Before and after are level-matched with a moving waveform, so you judge the master on tone and dynamics, not just whichever version is louder. This is the only fair way to A/B loudness changes, and it is built in.
✓ Studio analytics readout
Integrated LUFS, true peak and inter-sample peaks, dynamics, L/R correlation, and EQ all surface on the same screen. You see exactly the metrics a music supervisor or delivery spec asks for, in one place.
✓ Tools built into your catalog
No bouncing between a DAW, a loudness meter, a spectrum analyzer, and a separate mastering service. The files you measure and master are the same files you pitch and share, so the loudness workflow lives where your music already does.
Names you may know in this space
ITU-R BS.1770
The International Telecommunication Union recommendation that defines how LUFS loudness and true peak are measured. This is the actual standard the LUFS number comes from.
EBU R128
The European Broadcasting Union standard built on ITU-R BS.1770 that popularized integrated LUFS as a delivery target, originally for broadcast.
Spotify and YouTube
Both normalize playback around -14 LUFS integrated, which is why uploading a hot master just gets turned back down.
Apple Music
Normalizes around -16 LUFS via Sound Check, a slightly quieter target than Spotify, illustrating why there is no single universal loudness number.
Pricing for this audience
Both tools live inside DropCue at transparent, flat pricing with no per-track fees and no revenue share on placements. Starter starts at $5/mo (annual, 500 tracks) and can buy analysis and mastering packs. Pro starts at $15/mo (annual, 1,000 tracks, scaling by catalog size) and includes 10 free mastering credits and 10 free mix analyses. After that, Mix Analysis packs run 20 for $4.99 or 50 for $9.99, and Mastering packs run 10 for $9.99, 25 for $21.99, or 50 for $39.99 (or 15 per month for $12). Packs never expire, and Pro and Studio include every feature with no add-ons.
Frequently asked questions
What does LUFS stand for?
LUFS stands for Loudness Units relative to Full Scale. It is a standardized measurement of perceived loudness, how loud audio actually sounds to human ears, defined by the ITU-R BS.1770 recommendation. Values are negative and approach zero, so -9 LUFS is louder than -14 LUFS.
What is the difference between integrated, short-term, and momentary LUFS?
They differ by measurement window. Momentary LUFS uses a 400 millisecond window for catching the loudest instant. Short-term LUFS uses a 3 second window for how loud a section feels. Integrated LUFS measures the entire track as one number, and that is the value streaming platforms and sync delivery specs care about most.
What LUFS should I master to for streaming?
There is no single answer because platforms normalize to different targets. Spotify and YouTube sit around -14 LUFS integrated and Apple Music around -16 LUFS. Mastering near -14 LUFS integrated with true peak under -1 dBTP is a common safe target. The point is not to go as loud as possible; anything hotter than the platform target just gets turned back down.
What is true peak and why is it different from regular peak?
True peak (measured in dBTP) accounts for inter-sample peaks, the overshoots that appear when a digital signal is reconstructed into analog on playback. A normal sample peak meter can read under 0 dBFS while the true peak actually clips after conversion. That is why delivery specs pair a LUFS target with a true peak ceiling, usually -1 dBTP, for safe headroom.
How do I measure the LUFS of my own tracks?
DropCue's AI Mix Analysis, powered by ROEX, reads integrated LUFS to the ITU-R BS.1770 standard on any track in your library, alongside true peak, clipping, stereo width, mono compatibility, phase, and tonal balance, with plain-language recommendations. Note that for lossy sources like MP3, loudness and peak readings are approximate compared to the original WAV or FLAC, and we flag that.
Why does my loud master sound quiet on Spotify?
Because of loudness normalization. Streaming platforms turn every track toward their target (around -14 LUFS for Spotify), so a master pushed to -8 LUFS gets turned down to match, often losing dynamics in the process for no extra perceived loudness. Mastering to the target instead, then verifying with a loudness-matched A/B, gets you a cleaner result.
