AubioMixVisit Website →
← Back to blog

−14 LUFS, −1 dBTP: How Producers Meter for Streaming with AubioMix

October 4, 2026
−14 LUFS, −1 dBTP: How Producers Meter for Streaming with AubioMix

For streaming, measure integrated LUFS and true peak, aim for a realistic target like −14 LUFS with a True Peak ceiling around −1 DTP, and resist the urge to squash your dynamics to hit a number. Check both readings again after you render your final file, because encoding can shift the numbers more than you'd expect.

TL;DR:

  • Streaming platforms normalize playback to around −14 LUFS, so mastering louder only causes distortion without increasing perceived volume.
  • True Peak headroom of −1 to −2 dBTP is essential to prevent inter-sample clipping after lossy encoding.
  • Consistently measure integrated LUFS, True Peak, and Loudness Range across the full track to ensure optimal loudness and dynamic range for your genre.
  • Use high-quality, oversampled True Peak metering and verify numbers after rendering, as encoding can shift loudness and peak levels.
  • Regularly check your master across different playback environments to confirm your loudness and dynamics translate well beyond studio monitors.
Aubiomix
aubiomix.com
Get Clearer Mixing Feedback
Upload your song to Aubiomix for detailed feedback and actionable steps on mixing and mastering decisions.
Get mixing feedback

Table of Contents

Standards and how modern loudness metering actually works

Every loudness meter worth trusting is built on the same foundation: ITU‑R BS.1770. This standard defines how we calculate integrated LUFS and estimate true peak, and once you understand what it's doing under the hood, meter readings stop feeling like a black box.

The algorithm applies K-weighting first, a filter that mimics how we perceive loudness across the frequency spectrum, giving less weight to very low frequencies the way your ears naturally do. It then calculates mean square energy per channel, applies channel weighting, and uses gating thresholds to ignore quiet passages that would otherwise skew the average. The result is integrated LUFS: a single number representing the overall perceived loudness of your track from start to finish.

True peak works differently. Rather than just reading the sample values, BS.1770 estimates inter-sample peaks using oversampling, catching the peaks that occur between digital samples when a file is converted to analogue or transcoded to a lossy format. Miss these and you risk clipping after your track leaves your DAW, even when your sample peaks look perfectly safe.

Broadcast engineers have long worked to the EBU Tech 3343 / R128 guidelines, which set a production target of −23.0 LUFS for broadcast and offer supplementary guidance for streaming contexts. The tolerances and true-peak recommendations in these documents shaped how most modern meters are built, even outside broadcast work.

A few things worth knowing before you trust a single readout:

  • Meters can disagree by roughly 0.2 to 0.3 dB depending on implementation, gating choices and oversampling rate, so don't chase a single decimal point.
  • Loudness measurement is an estimate of perceived loudness, not an absolute truth. It varies with listening conditions and individual hearing.
  • True-peak accuracy depends heavily on oversampling quality. A meter with weak oversampling can miss peaks that a properly specified one catches.

None of this means metering is unreliable. It means you should treat the numbers as a well-informed guide, not gospel, and always pair them with your own ears.

How streaming platforms actually treat your loudness

Streaming platforms don't permanently alter your master file. They apply playback normalisation, a volume adjustment that happens in real time when a listener presses play, turning your track up or down to match a target loudness for that platform's "normal" listening mode. Your file on the server stays untouched. What changes is what the listener hears.

Spotify measures every uploaded track and normalises playback to roughly −14 LUFS. If you master louder than that, Spotify simply turns your track down at playback, meaning all that extra limiting you applied just adds distortion without adding perceived volume. Spotify also recommends keeping True Peak below −1 dBTP, or −2 dBTP if you've mastered louder, specifically to avoid artefacts introduced during lossy encoding.

YouTube takes a looser approach. It recommends delivering the highest quality audio you can, ideally 24-bit FLAC or PCM, and it applies some automated volume adjustment to certain content, but it doesn't publish a strict LUFS target the way Spotify does. That gives you more creative latitude on YouTube, though the safety margin around true peak still applies.

A True Peak ceiling of −1 to −2 dBTP gives lossy encoders enough headroom to avoid inter-sample clipping according to Spotify's loudness guidance, which is the single most useful number in this whole discussion if you only remember one thing.

Before you upload anywhere, run through this short platform-aware check:

  • Confirm your integrated LUFS sits near your target platform's normalisation point, not necessarily at it.
  • Verify True Peak stays below your chosen ceiling across the entire track, not just the loudest chorus.
  • Export in the highest bit depth and sample rate the platform accepts, rather than pre-compressing to a lossy format yourself.

A practical metering workflow you can use in the studio

Getting this right isn't about memorising numbers. It's about building a repeatable process that catches problems before they reach a listener's ears. Here's the order I'd work through on every master.

  1. Calibrate your monitoring first. Set your reference listening level consistently, load a couple of commercially released tracks in your genre as reference points, and leave real headroom in your mix bus, ideally peaking well below 0 dBFS before any mix bus processing.
  2. Check the full track, not just the loud bits. Run your meter across integrated LUFS, short-term, momentary and True Peak for the entire song. A chorus that peaks fine in isolation can still push your integrated value higher than you intended once the whole arrangement plays through.
  3. Apply your mastering pass with intent. Use gentle limiting rather than brute force, and re-measure after every adjustment. If your genre leans loud and energetic, you might accept a higher integrated LUFS and tighter LRA. If it leans acoustic or ambient, protect the dynamic range instead.
  4. Export properly and check again. Render at 24-bit/48kHz where the platform allows it, then reload that exported file and measure it again. Rendering and dithering can shift your numbers slightly, and you want to catch that before upload, not after.
  5. Do a final upload verification where possible. Some platforms let you preview how your track sounds post-normalisation. Use that if available, rather than assuming your pre-upload numbers tell the whole story.

Pro Tip: Keep a simple checklist taped to your session template: target LUFS, True Peak ceiling, and LRA range for the genre you're mastering. Five seconds of checking saves a re-upload later.

If you want a deeper walkthrough of the full mastering chain, our complete producer's guide to mastering covers the process end to end.

Key metering metrics explained and how to read them

Four readings matter here, and conflating them is the most common mistake I see in producer forums.

Integrated LUFS is your track's overall loudness average from start to finish, gated to ignore silence and very quiet passages. It's the number streaming platforms use for normalisation, and it's the one you should treat as your primary target.

Short-term LUFS measures loudness over a rolling three-second window, giving you a sense of how loudness moves through sections of your track. Momentary LUFS is even faster, typically a 400 millisecond window, useful for spotting sudden spikes but too jumpy to use as your main reference.

Loudness Range (LRA) tells you how much your track's loudness varies between its quietest and loudest sustained sections. A narrow LRA suggests a heavily compressed, consistently loud track. A wide LRA suggests more dynamic movement, which suits genres like acoustic, orchestral or ambient work far better than it suits dance or pop.

True Peak catches inter-sample peaks that ordinary sample peak meters miss entirely, which is why oversampling matters so much here. Our true peak guide breaks down exactly why these peaks occur and how to guard against them.

Practical acceptance ranges worth working towards:

  • Integrated LUFS near your target platform's normalisation point, adjusted for genre expectations.
  • True Peak at or below −1 dBTP, dropping to −2 dBTP if you've mastered on the louder side.
  • LRA wide enough to preserve the emotional dynamics your arrangement relies on, rather than flattened for the sake of consistency.

For quick definitions while you work, our audio metrics glossary covers LUFS, True Peak, Crest Factor and LRA in one place, and our piece on LUFS explained goes deeper on how producers should interpret each reading.

Choosing and configuring a loudness meter that you'll actually trust

Not every meter plugin gives you the same confidence, and the difference usually comes down to a handful of features worth checking before you buy or commit to one.

Look for ITU-1770 compliance first, since that's the algorithm underpinning the LUFS and True Peak figures every platform references. Beyond that, these features separate a genuinely useful meter from a decorative one:

  • True-peak oversampling at 4x or higher, which catches inter-sample peaks that lower-quality implementations miss.
  • Simultaneous integrated, short-term and momentary displays, so you can watch all three without switching views mid-mix.
  • History and logging, letting you review how loudness evolved across the whole track after playback finishes.
  • Gating options that match the ITU standard, so your integrated reading isn't skewed by silence or very quiet sections.

Ergonomics matter more than people admit. A meter you can read at a glance, with a resizable window and presets for your target platforms, gets used properly. One buried in submenus gets ignored under deadline pressure.

For final verification, run an offline render-based LUFS check rather than relying solely on real-time monitoring during playback. Real-time meters are great for mixing decisions, but a render-based pass catches the true, final values of your exported file, including any shifts introduced by dithering or sample rate conversion.

Pro Tip: Test any new meter against a reference test tone at a known level. If it doesn't read back accurately, trust your ears over its numbers until you sort out why.

Common mastering mistakes and how to actually fix them

The most common mistake I see is producers chasing a specific LUFS number without first deciding what the track is supposed to feel like. Decide your artistic target first: is this a track meant to hit hard and loud, or one that needs to breathe? Then use metering to confirm you've hit that target safely, not to dictate it from the outset.

The second mistake is watching only a peak meter and assuming that's enough. Sample peaks tell you almost nothing about perceived loudness or inter-sample clipping risk. Pair integrated LUFS with properly oversampled True Peak readings, always.

Practical fixes worth trying:

  • Use mild clipping before your limiter rather than relying on the limiter alone, which often preserves more punch with less audible artefact.
  • Reach for multiband dynamics on problem frequencies instead of squashing the whole mix with broadband compression.
  • Automate level through a section rather than defaulting to blanket compression across the entire track.

Genres built around sustained energy, such as dance, hip-hop and pop, generally tolerate louder, tighter masters without sounding wrong. Acoustic, jazz, orchestral and ambient material usually benefits from more headroom and a wider LRA, since the emotional impact often comes from the quiet-to-loud contrast rather than consistent intensity.

Measured benchmarks and checks worth running before delivery

Genre expectations vary enough that a single universal LUFS target rarely serves every track well, which is part of why AubioMix tracks measured benchmark ranges by genre rather than pushing one number for everyone. Our pop mastering benchmarks illustrate this well: pop masters tend to cluster in a tighter loudness range than something like acoustic material, which benefits from more preserved dynamics.

Before you call a master finished, confirm these items:

  • Integrated LUFS sits within the range appropriate for your genre and target platform.
  • True Peak stays below your chosen ceiling across the full track, verified with oversampling.
  • LRA matches the dynamic character the arrangement calls for, not an arbitrarily narrow figure.
  • No phase or frequency masking flags remain unresolved between competing elements.

Running your mix through an automated report before sending it to a mastering engineer cuts down the back-and-forth considerably. Instead of a vague "it feels thin" note, you arrive with specific, prioritised issues to address, which tends to make every subsequent revision faster.

Loudness normalisation beyond Spotify and YouTube

Spotify and YouTube get most of the attention, but other platforms run their own normalisation schemes, and the differences matter if you distribute widely. Apple Music normalises playback by default through its Sound Check feature, generally targeting a level in a similar region to Spotify's approach, though Apple doesn't publish the same granular guidance Spotify does for artists preparing masters.

Tidal and Amazon Music also apply their own playback normalisation, and because neither publishes detailed loudness targets with the same clarity as Spotify, the safest approach is to master to a sensible, genre-appropriate loudness and keep your True Peak ceiling conservative, rather than trying to hit a platform-specific number you can't verify.

The practical takeaway is that chasing an exact figure for every platform individually is a losing game. Master your track so it sounds right at a reasonable, controlled loudness with safe True Peak headroom, and let each platform's normalisation handle the rest. Consistency in your mastering approach serves you better across a dozen platforms than an obsessive chase for one platform's exact number.

How codecs and bitrates change what listeners actually hear

Lossy codecs like AAC and Ogg Vorbis, which most streaming platforms use for delivery, can introduce small level and transient changes during encoding. This is precisely why True Peak headroom matters so much: a file that measures safely in your DAW can develop inter-sample peaks after it's been through a lossy encoder, especially if you've mastered right up against 0 dBFS.

Lower bitrates compress the audio more aggressively, which can shift perceived loudness slightly and soften transients. Higher bitrates and lossless formats preserve more of your original master's character, which is part of why YouTube recommends delivering the highest quality file you can rather than pre-compressing yourself.

The practical implication for your metering workflow is simple: always build in True Peak headroom before you export, because you're not just protecting against clipping in your own file. You're protecting against artefacts introduced by a codec you don't control once the platform processes your upload.

Why playback devices change how your metering decisions land

A LUFS reading is consistent on paper, but what a listener actually experiences depends heavily on their playback environment. Phone speakers, earbuds, car audio systems and studio monitors all reproduce frequency and dynamics differently, and a track mastered with a wide LRA for a quiet listening room can lose its intended impact on a noisy commute.

This doesn't mean you should flatten every track for phone speakers. It means you should check your master across a few realistic environments, not just your studio monitors, before finalising. A track that sounds powerful on monitors but disappears on earbuds likely needs some adjustment to its frequency balance or dynamic handling, not necessarily its overall loudness.

Metering gives you the numbers, but listening across devices tells you whether those numbers translate into the experience you actually intended for your audience.

Using metering tools across different DAWs and mastering software

Most modern DAWs, including Pro Tools, Logic Pro, Ableton Live and Cubase, support third-party loudness meter plugins that implement the BS.1770 standard, and several also include basic built-in loudness meters now. The key is checking that whichever meter you use, built-in or third-party, offers proper oversampled True Peak detection and a clear integrated LUFS readout, rather than assuming every bundled meter meets the same standard.

Dedicated mastering software often includes more detailed history and logging features than a DAW's native meter, which helps when you need to review how loudness evolved across an entire album rather than a single track. If you're mastering a full release, this kind of session-level logging saves considerable time compared with manually renaming screenshots of meter readings for every track.

Whichever software you choose, the workflow stays the same: real-time monitoring during your mix and master, followed by an offline render-based check on your final exported file, to confirm the numbers that reach the platform match what you intended in your session.

What before and after metering actually reveals

The clearest way to understand why metering matters is to compare an unmastered mix against the same track after a proper mastering pass. An unmastered mix often shows a wide, inconsistent LRA with integrated LUFS sitting well below typical streaming targets, meaning it will sound noticeably quieter than comparable tracks when a listener skips between songs on a playlist.

Before and after mastering waveform comparison

After a considered mastering pass, the same track typically shows a tighter, more intentional LRA, an integrated LUFS closer to the target platform's normalisation point, and a True Peak safely under the chosen ceiling. The difference isn't just a number moving. It's the track now competing fairly in a playlist without losing the dynamic character that made the arrangement work in the first place.

This is the practical value of metering throughout the process rather than only at the final export: you can see exactly where a track started, track the impact of each mastering decision, and confirm the finished file actually delivers what you intended before a listener ever presses play.

Measure first, then let the music decide

Metering tells you where you stand, not what to do next. I always measure before making a single mastering decision, because a number without context is just noise, and a master without numbers is a guess.

Test everything across more than one playback environment. Your monitors will lie to you occasionally, and a quick check on earbuds or a phone speaker catches problems a meter alone won't flag. Use an objective report as your final gut check, not your starting point, and let the genre and the arrangement guide the target you're actually chasing.

— AubioMix

How AubioMix helps you get your master streaming-ready

Upload your mix to AubioMix and get a measured report back with the specific numbers and fixes you need, not vague feedback you have to interpret yourself. The platform checks your track against genre benchmarks and flags exactly where your loudness, dynamics or peak levels need attention before you send a file anywhere near a streaming platform.

Aubiomix

What you get from a single review:

  • Integrated LUFS and True Peak readings checked against your target platform's behaviour.
  • Genre-specific benchmark comparisons, so your target reflects your style rather than a generic figure.
  • A downloadable PDF report you can share directly with a mastering engineer or keep for your own records.

A single Mix Review runs £4.99, or you can subscribe to the Professional or Professional + plans for ongoing feedback across multiple tracks.

FAQ

What is the best metering plugin?

There's no single best plugin, since the right choice depends on your workflow, but any meter you choose should offer proper ITU-1770 compliant integrated LUFS and oversampled True Peak detection. Look for one with clear simultaneous displays for short-term and momentary readings alongside history logging.

Should I meter for shadows or highlights?

This question usually comes from confusing photography terminology with audio, since loudness metering doesn't involve shadows or highlights at all. For audio, you're metering integrated LUFS, short-term and momentary loudness, Loudness Range and True Peak, each serving a distinct purpose in your mastering decisions.

YouTube doesn't publish a strict LUFS mastering target the way Spotify does, recommending instead that you deliver the highest quality audio possible, ideally 24-bit FLAC or PCM. Keeping your True Peak below a safe ceiling, such as −1 dBTP, remains good practice regardless of platform.

Does Spotify have integrated LUFS normalisation?

Yes, Spotify measures uploaded tracks and applies playback normalisation targeting roughly −14 LUFS for its standard listening mode. If your master is louder than that, Spotify turns playback down rather than up, so mastering far above that level adds distortion risk without adding perceived volume.

Can an automated tool replace checking my own mix numbers?

An automated report like AubioMix's can confirm your integrated LUFS, True Peak and LRA quickly and flag genre-specific benchmark comparisons, which speeds up your workflow considerably. It works best alongside your own listening checks across different playback devices, rather than as a complete replacement for critical listening.

Sources