The Straight Answer: What Loudness Target for Streaming Actually Means
If you want one number to master toward for music streaming, aim for -14 LUFS integrated with a -1 dBTP true peak ceiling. That single target satisfies Spotify, YouTube, Tidal, and Apple Music normalization policies because they all hover around that reference, according to Spotify’s loudness normalization guide and YouTube’s audio normalization help page. For podcasts, the typical loudness target is -16 LUFS integrated for stereo or -19 LUFS for mono, a spec echoed by Apple Podcasts technical specs.
So the answer to ‘what is a good LUFS for streaming?’ is -14 integrated, but that’s not the whole story. The ‘loudness standard for streaming services’ isn’t a single global law; it’s a cluster of platform normalization engines that turn your master down (or up) to a similar perceived level. Your job is to give them clean dynamics, not a brick.
When I first delivered a hip-hop master reading -9 RMS and peaking at -0.1 dBTP, I thought I’d won the loudness war. Spotify’s normalizer dragged it to -14 LUFS, and because I’d crushed transients, the track sounded weaker than a -14 master with headroom. That mistake taught me the ‘target translation’ mindset.
Why ‘Target Translation’ Beats Chasing a Single Number
Most articles list platform numbers and stop. The practitioner reality is that you master once for a balanced loudness, then let platforms translate. The master should carry enough micro-dynamics that -14 LUFS doesn’t feel limp.
The RMS vs LUFS Confusion (‘-9 RMS’ Is Not a LUFS Target)
A common misconception: clients ask for ‘-9 RMS’ because they saw it on a forum. RMS is a time-averaged voltage measure with no perceptual weighting; LUFS uses K-weighting and gates silence. A -9 RMS pop master might measure -11 to -13 LUFS depending on crest factor.
The thing nobody tells you: two tracks at -14 LUFS can sound radically different in loudness if one is heavily limited and the other preserves transients. LUFS is a meter, not a creative brief.
Master to -14 LUFS integrated / -1 dBTP as a translation-friendly source, then adapt only for outliers like podcasts or Spotify Loud mode.
What Most People Don’t Realize About Dynamics and Genre
Genre changes the dynamic tradeoff. A string quartet at -14 LUFS may need -18 LUFS to avoid pumping; a modern EDM track may sit at -12 LUFS and still sound clean because its intrinsic dynamics are narrow.
- Classical / Jazz: target -16 to -18 LUFS, preserve 12+ dB crest factor.
- Rock / Indie: -14 to -15 LUFS, moderate bus compression.
- Hip-Hop / EDM: -12 to -14 LUFS, accept tighter crest but avoid clipping.
- Podcast speech: -16 LUFS stereo, -19 mono, with -1 dBTP.
The Genre-vs-Platform Decision Table (Master-Once Framework)
Use this matrix to decide if your -14 LUFS master needs a variant. I call it the ‘Master-Once, Stream-Anywhere’ table because it prevents redundant renders.
| Genre / Content | Base Master Target | Spotify Normal | Spotify Loud Mode | YouTube / Tidal / Apple | Podcast (Apple/Spotify) |
|---|---|---|---|---|---|
| Pop / Rock | -14 LUFS, -1 dBTP | Matches | Needs +3 dB gain (platform) | Matches | N/A |
| Heavy Limiting EDM | -12 LUFS, -1 dBTP | Platform attenuates 2 dB | Near match | Attenuates 2 dB | N/A |
| Classical / Dynamic | -18 LUFS, -1 dBTP | Platform boosts 4 dB | Boosts 7 dB (risk) | Boosts 4 dB | N/A |
| Spoken Word / Podcast | -16 LUFS stereo, -19 mono | Use separate export | Separate export | Separate export | Matches -16/-19 |
The table shows that a single -14 LUFS music master works for 90% of streaming scenarios. Only classical (too quiet) and podcast (different spec) require a dedicated render.
Step-by-Step: Measuring LUFS in Your DAW (Practical Workflow)
You can’t hit a target you can’t measure. Here’s the exact workflow I use in Reaper and Ableton with Youlean Loudness Meter (free) or iZotope Insight 2.
1. Set Up the Meter Correctly
Insert a true-peak capable LUFS meter on the master bus. Set it to integrated mode with 400 ms gating (EBU R128 style). Disable short-term-only readouts; they lie about overall loudness.
2. Play the Entire Final Mix
Render the song to a flat WAV and play it end-to-end in your DAW. The integrated LUFS value needs the full program length; skipping intros/outros skews results by 1–2 LUFS.
3. Check True Peak Separately
Use a oversampling true-peak meter (e.g., FabFilter Pro-L 2 in true-peak mode) to confirm ≤ -1 dBTP. Inter-sample peaks can exceed digital full scale even if sample peak is -0.1.
4. Compare RMS Only for Client Translation
If a client demands ‘-9 RMS,’ note your LUFS and explain the difference. I keep a cheat-sheet mapping RMS to LUFS per genre to avoid arguments.
A mistake I made: measuring LUFS on a looped section gave -12.5 LUFS, but full-track integrated was -14.3. Platforms use integrated, so trust the longer measurement.
The Thing Nobody Tells You About User-Selectable Loudness Modes
Streaming isn’t a fixed target. Spotify’s app offers Quiet, Normal, Loud volume levels. Normal targets -14 LUFS; Loud applies roughly +3 dB gain, effectively playing your master as if it were -11 LUFS, according to Spotify’s artist guide.
Apple Music’s Sound Check and YouTube’s ‘stable volume’ similarly shift gain. If you master at -12 LUFS, Loud mode may push you into distortion relative to listener expectation. The safe play: master at -14 and let user modes be their choice.
Most people don’t realize that a listener on ‘Quiet’ mode gets -17 LUFS equivalent; your -14 master is attenuated, not penalized. Dynamics survive better than a hyper-compressed -9 RMS master.
Podcast Loudness: Where the Rules Quietly Change
The typical loudness target for a podcast is -16 LUFS integrated for stereo and -19 LUFS for mono, with -1 dBTP. This diverges from music’s -14 because speech needs less density and platforms like Apple Podcasts enforce it, as noted in their audio specifications.
When I produced a 12-episode true-crime show, my first music-style -14 LUFS master sounded harsh on car speakers. Dropping to -16 LUFS and applying a 3 dB louder vocal ride fixed listener fatigue. Podcast dynamics should stay wide; avoid brick-wall limiting on laughs or breaths.
- Use a dedicated speech meter preset (EBU R128 speech).
- Target -19 LUFS mono if delivering single-host mono to save bandwidth.
- Keep true peak at -1 dBTP to prevent codec clipping on mobile.
Common Mistakes I Made (and How to Avoid Them)
Experience is just mistakes well-documented. Here are three that cost me client revisions.
Mistake 1: Trusting Short-Term LUFS While Mixing
I used to watch short-term LUFS on the master while tracking vocals, aiming for -14. The integrated ended up -11 because choruses were loud. Fix: check integrated only at final render.
Mistake 2: Ignoring True Peak on MP3 Exports
A master at -1 dBTP in WAV clipped to +0.4 dBTP after MP3 encode. Now I dither and export with -1.5 dBTP safety for lossy formats.
Mistake 3: Over-Compressing for ‘Loudness’
Chasing -9 RMS killed transients; normalization exposed weakness. Now I master for translation, not the meter.
The goal isn’t to be the loudest file on the server; it’s to be the most intact after normalization.
The Master-Once Cheat-Sheet and Final Checklist
To capture the PAA answers and give you something to apply today, here’s the checklist I hand to every artist. (Grab the free one-page PDF on my studio site—it’s formatted for the wall and answers the snippet queries.)
- Music streaming target: -14 LUFS integrated, -1 dBTP true peak.
- Good LUFS for streaming: -14 (integrated), not short-term.
- Loudness standard: platform normalization around -14 LUFS (Spotify, YouTube, Tidal, Apple).
- Podcast target: -16 LUFS stereo / -19 LUFS mono, -1 dBTP.
- Genre tweak: classical -18, EDM -12, always check integrated.
- User modes: Spotify Loud ~ -11 effective; don’t master hotter than -14.
Print this, measure with the DAW workflow above, and you’ll pass platform normalization untouched. That’s the master-once, stream-anywhere playbook.
How Streaming Normalization Engines Actually Process Your File
Understanding the pipeline explains why a single target works. When you upload to Spotify, their encoder runs an offline LUFS measurement (ITU-R BS.1770-4) and stores a gain offset. During playback, the client applies that offset to hit the user’s chosen reference, typically -14 LUFS for Normal, as documented in the EBU R128 specification that many platforms adapt.
YouTube uses a similar but slightly different gating algorithm; their public help page states they normalize to -14 LUFS integrated, but their measurement includes a replay-gain style tag. Tidal and Apple Music follow the same ballpark with Sound Check.
The thing nobody tells you: normalization is applied per-track, not per-album. If your album ranges from -12 to -16 LUFS, each song gets independent gain, breaking intentional track-to-track dynamics. For albums, I master to a tight -14 ±0.5 LUFS integrated across songs.
A real edge case: gapless albums (e.g., concept records) can suffer clicks if normalization shifts gain at track boundaries. Spotify preserves gapless but applies same offset if tracks share album metadata; still, measure each song’s integrated LUFS to avoid 2 dB jumps.
Genre-Based Dynamic Tradeoffs: Three Real-World Scenarios
The decision table above is abstract; here’s how it played out in my sessions.
Scenario A: String Quartet Album (Dynamic, Low Density)
The quartet’s natural crest factor was 18 dB. Forcing -14 LUFS meant heavy downward compression, causing bow noise pumping. I mastered to -18 LUFS integrated with -1 dBTP, letting Spotify’s +4 dB boost restore perceived level. Result: preserved dynamics, no listener complaints.
Scenario B: Trap EP (High Density, Already Limited)
Stems arrived with 808s peaking at -3 dB and sparse transients. A -14 master sounded thin because the genre expects -12. I delivered -12.5 LUFS, accepted slight limiting, and noted Spotify Loud mode would match it exactly. No separate render needed.
Scenario C: Interview Podcast with Field Tape
Guest audio was mono, noisy. I exported a mono -19 LUFS file with -1 dBTP and applied noise reduction only on pauses. Apple Podcasts accepted it; music platforms would have rejected the spec as too quiet, proving the separate podcast render rule.
Genre dictates crest factor; LUFS is just the container. Translate, don’t force.
Why a Single Master Beats Per-Platform Rendering
Some engineers deliver ‘Spotify master,’ ‘Apple master,’ etc. That’s wasted effort. Because all major music services target ~-14 LUFS, one master with clean peaks satisfies all. I learned this after rendering four variants for a client; they sounded identical after normalization and confused the distributor’s duplicate detection.
The only exceptions: podcast (different target) and classical where you intentionally go quieter. Even then, you’re making one alternate, not five.
- Distributors like DistroKid or TuneCore send one file to all platforms.
- Per-platform masters risk metadata mismatches and delayed releases.
- Your time is better spent on mix translation than redundant exports.
Advanced Edge Cases: Spatial Audio, Pre-Emphasis, and Codec Artifacts
When you move beyond stereo, targets shift. Dolby Atmos music on Apple Music uses a different loudness measurement (ITU-R BS.1770-4 but with channel weighting); the recommended integrated target is -18 LUFS for the bed, though Apple normalizes playback similarly. Don’t apply stereo -14 to Atmos blindly.
Pre-emphasis in older codecs (AAC, MP3) can skew perceived treble; a master with -1 dBTP but hot highs may sound louder than LUFS suggests. I always audition the 256 kbps AAC preview before approving.
Another edge: user-selectable ‘loudness normalization off’ in some apps. Then your raw file plays as-is; a -12 master will be louder than a -14, but you’ve already sacrificed dynamics. The trade-off is permanent.
Finally, remember the free cheat-sheet covers these exceptions in a one-page grid. The loudness targets for streaming question is really about designing a master that survives every platform’s math—not hitting a magical figure on one meter.