Streaming loudness targets for every platform (2026)
Streaming services use loudness normalization to reduce level differences between tracks. This guide explains the reference levels, true-peak recommendations and playback settings to check when preparing a master.
How streaming loudness normalization works
Every major streaming service measures a track's integrated loudness in LUFS (Loudness Units relative to Full Scale, defined by the ITU-R BS.1770 standard) and adjusts playback so songs sit at a consistent level. If your master is louder than the platform's reference, it gets turned down. Some platforms also turn a quiet master up, though only within limits, leaving headroom so the boost doesn't push true peaks into distortion after lossy encoding.
There are three LUFS measurements worth knowing:
- Integrated LUFS. The average loudness across the whole track. This is the number platforms normalize to, and a useful reference for estimating playback gain.
- Short-term LUFS. A ~3-second rolling average, useful for watching dynamics section to section.
- Momentary LUFS. A ~400 ms window, useful for catching transient-heavy moments.
Normalization changes playback gain; it does not undo compression, limiting or clipping in the master. Two versions can play at the same integrated loudness and still differ in dynamics and tone. Choose the processing for the song, then compare it at the expected listening level.
Platform loudness targets at a glance (2026)
| Platform | Reference loudness | True-peak ceiling | Adjusts |
|---|---|---|---|
| Spotify | −14 LUFS | −1 dBTP (−2 if > −14 LUFS) | Up & down |
| Apple Music | −16 LUFS | −1 dBTP | Up & down (Sound Check) |
| YouTube / YT Music | −14 LUFS | −1 dBTP | Down only |
| Tidal | −14 LUFS | −1 dBTP | Up & down |
| Amazon Music | −14 LUFS | −2 dBTP | Up & down |
| Deezer | −15 LUFS | −1 dBTP | Up & down |
| TikTok | Not verified | Not verified | Check current app playback |
| Bandcamp | No normalization | n/a | Plays as-is |
Check the service’s current delivery requirements and playback settings. Spotify lists Normal at −14 LUFS, Loud at −11 and Quiet at −19. Its documented limiter applies in Loud mode; Normal gain for quiet tracks is constrained by available headroom. The web player and some third-party devices do not normalize playback.
So what should I master to?
There's no single right number; it depends on the genre and the intent of the record. As a reference, −14 LUFS is roughly where Spotify, YouTube, Tidal and Amazon land playback, so a master near it is heard close to as delivered. Many records are mastered hotter than that on purpose (see the ranges below); quieter, dynamic genres sit below it.
A quieter master is not automatically a better one. Reducing processing can change the density, low-end weight or impact intended for the record. Compare with relevant releases at matched loudness and discuss the result with the artist.
On true peak, the specs ask for −1 dBTP, and −2 dBTP for Amazon and for anything hotter than −14 LUFS on Spotify. A higher measured peak does not establish whether distortion is audible. Check the file and a decoded test encode, then listen to both.
Example loudness ranges
| Genre / context | Illustrative range | What to consider |
|---|---|---|
| EDM | −4 to −8 LUFS | Check whether limiting changes the kick and bass relationship. |
| Metal | −5 to −9 LUFS | Compare drum transients and guitar density at matched loudness. |
| Hip-hop / trap | −6 to −8 LUFS | Listen for changes to the vocal, kick and bass as the level increases. |
| Pop / rock / electronic | −8 to −12 LUFS | Compare the dynamics and tone with relevant reference tracks. |
| Indie / folk / singer-songwriter / downtempo | −13 to −15 LUFS | Check that quieter details and changes between sections remain audible. |
| Classical / jazz / acoustic / ambient / orchestral | −16 to −18 LUFS | Consider the arrangement and intended playback environment when choosing dynamics. |
Album consistency matters more than any single number. Master the record so tracks feel coherent relative to one another, then check the loudest track against the platform reference.
Treat these ranges as examples, not requirements for a genre. Arrangement and production choices matter as well as level. Clipping and limiting may be intentional parts of the sound, but measure their effects and listen to the result rather than judging quality from LUFS alone.
Same level, different master
The table below shows the gain adjustment for an example master at −7.5 LUFS, using the listed normalization references:
| Platform | Adjustment | Plays your master at |
|---|---|---|
| Spotify (Normal) | −6.5 dB | −14 LUFS |
| Apple Music | −8.5 dB | −16 LUFS |
| YouTube | −6.5 dB | −14 LUFS |
| Tidal | −6.5 dB | −14 LUFS |
| Amazon Music | −6.5 dB | −14 LUFS |
| Deezer | −7.5 dB | −15 LUFS |
| Bandcamp | none | −7.5 LUFS |
These are gain calculations for the stated settings. Actual playback depends on the service, device and normalization mode. Matching integrated loudness does not make two differently processed masters sound identical. You can preview gain changes with the loudness tool.
Why true peak, not sample peak
A limiter set to 0 dBFS at the sample level still produces inter-sample peaks, overshoots that appear when the signal is reconstructed by a converter or re-encoded by a lossy codec (AAC, Ogg Vorbis). A file that reads 0.0 dBFS on a sample meter can measure +1 dBTP or more after Spotify or Apple encodes it. Whether that is audible depends on the material: listen to the source and the decoded test file to assess any audible change.
Check true peak as well as sample peak, and test the decoded file when assessing a codec. The metering guide explains those measurements. Recommended margins reduce risk but do not predict whether a particular artifact will be audible.
Settings and assumptions to check
- Mastering to the "Loud" mode number (−11). Loud is one playback setting, not a delivery requirement. Choose the master’s dynamics by listening rather than targeting this setting’s reference level.
- Reading sample peak instead of true peak. A 0.0 dBFS sample reading does not rule out higher inter-sample peaks. Measure true peak as well.
- Ignoring the Amazon −2 dBTP exception. Check the stated delivery recommendation and measure a decoded test encode. The source peak alone does not predict audible distortion.
- Chasing a single number across an album. Relative balance between tracks beats hitting −14.000 on every one.
- Treating an assumed target as a delivery requirement. Where a service does not publish a target, check the result in the current app instead of prescribing a mastering level from an unverified number.
How to check your master in seconds
The Soneam loudness tool measures integrated LUFS, true peak and dynamics and provides playback previews. Analysis uploads audio for server processing; the original upload is deleted afterward. Previews are simulations, not a guarantee of playback on every service and device.
Frequently asked questions
What LUFS should I master to for Spotify in 2026?
There's no single number; it depends on genre and intent. Spotify normalizes to about −14 LUFS in Normal mode, so a master near it is heard close to as delivered, but −14 is a reference, not a ceiling: many records are mastered hotter on purpose and the density can carry through the turn-down. On true peak the specs ask for −1 dBTP, −2 for Amazon, which loud masters often exceed on purpose; read yours and decide rather than find out after the encode.
Does TikTok normalize loudness?
We have not verified a single published TikTok normalization target that applies across playback contexts. Do not treat −14 LUFS as a confirmed TikTok delivery requirement. Check the uploaded result in the app and retain the master you approved.
What's the difference between true peak and sample peak?
Sample peak is the highest digital sample value. True peak estimates the peak of the reconstructed waveform using oversampling. Encoding can change the waveform, so checking codec-related peak changes requires measuring the decoded encode.
Why does my master sound quieter on Spotify than other tracks?
Check the playback mode, device and whether normalization is enabled. A quiet track may not reach the reference if there is insufficient peak headroom. Tonal balance, dynamics and album normalization can also affect comparisons.
Is the loudness war over?
Normalization reduces playback-level differences when it is active. It does not remove the tonal and dynamic effects of mastering, and it is not enabled in every listening context. Choose the level for the music and check normalized as well as unnormalized playback.
Should I make separate masters per platform?
Usually a single high-quality stereo master is sufficient. Confirm the distributor’s format requirements and the release plan. Separate versions may be appropriate for a different format or use, such as CD or a DJ release.
Try the client’s loudness preview before sharing a master. It plays the master at an estimate of the selected service’s level, changing playback only and never the delivered file. How each service is modeled.
Review a mix with your client
Send a review link for lossless playback, waveform comments and approval. Clients do not need an account. Review links have no expiry unless you set one. On Free, released delivery files are available for 30 days at a time and can be released again.