ERASYOpen App

AI Music

LUFS for Spotify in 2026: Which Targets Are Actually Published

By Eddie Mathews··13 min read
LUFS for Spotify in 2026: Which Targets Are Actually Published — Erasy

Every mastering guide prints the same six-row table: Spotify -14, Apple Music -16, YouTube -14, Amazon -14, TIDAL -14, Deezer -15. We went to each platform's own documentation to source the rows. Five of the six are not there.

That is not a rounding quibble. LUFS for Spotify is a published number you can quote back at a page; the rest of that table is third-party measurement of playback behaviour, copied between blogs until it reads like a delivery spec. Here is what each platform actually publishes, read at source on 24 October 2026, and what to do with the gap.

LUFS targets for Spotify and streaming platforms — audio loudness meter showing integrated LUFS measurement for a mastered track

Key takeaways

Exactly one platform publishes a loudness target. Spotify: “-14 dB LUFS, according to the ITU 1770 standard”, true peak below -1 dBTP. Everything else in the usual table is inferred.

Apple's own guide contains zero occurrences of “LUFS”. We downloaded all 5,443 words of Apple Digital Masters and searched it. The one Apple loudness figure that exists is a -18 LKFS ceiling for Atmos and 5.1/7.1, not a -16 stereo target.

TIDAL and Deezer publish nothing measurable. TIDAL's help centre returns 0 articles for loudness, normalisation, mastering and LUFS; Deezer's one normalisation article gives no number at all.

-14 with -1 dBTP is still the right answer — just for a better reason. It is Spotify's published figure, and nothing else has a figure to disagree with.

You can measure it for nothing. Two passes of ffmpeg's loudnorm, verified with ebur128, landed our test file at -14.1 LUFS and -2.9 dBTP. No vendor involved.

What LUFS actually measures

LUFS means Loudness Units relative to Full Scale. It measures how loud something sounds to a human over time, rather than how tall the signal gets at any instant.

That distinction is the whole reason the standard exists. A peak meter tells you your loudest sample. It cannot tell you that a dense, limited mix at the same peak level sounds dramatically louder than a sparse, dynamic one. Platforms need to compare tracks the way ears do, so they normalise on perceived loudness.

The number you care about is integrated LUFS — the average across the whole track. Short-term and momentary readings are useful while you work, but integrated is what a platform reads and what decides how much it moves your file.

None of that is in dispute. The measurement is defined by ITU-R BS.1770 and the units are interchangeable with LKFS — the EBU says so in as many words. What is in dispute, once you go looking, is who has actually committed to a number.

Which platforms actually publish one

We took the six rows every guide prints and tried to source each one from the platform itself: its artist documentation, its help centre, its delivery specification. Where a help centre blocked a browser we queried its own search API instead. The results are not close.

PlatformWhat it publishes, read at sourceThe figure guides print
Spotify“-14 dB LUFS, according to the ITU 1770 standard”; “Keep it below -1dB TP max”-14 — correct and sourced
Apple MusicNo LUFS or LKFS figure for stereo. “Leave at least 1 dB of headroom”-16 — not an Apple figure
YouTube / YT MusicUpload encoding page carries bitrates only; no loudness content at all-14 — inferred from playback
TIDALHelp centre returns 0 articles for loudness, normalisation, mastering, LUFS-14 — no source found
DeezerOne normalisation article. It gives no number of any kind-15 — no source found
Amazon MusicNo artist-facing loudness target located; help path 404s-14 — not located
EBU R128 (broadcast)Target -23.0 LUFS ±1.0 LU; true peak “shall not exceed -1 dBTP”Rarely cited — the actual standard

One row of six is a specification. One row is a published broadcast standard that nobody mastering for streaming is bound by. The other five are observations about what happens to a file after it arrives, reprinted in a column headed as though the platform had asked for them.

Amazon is the row we are least sure about, and we are saying so rather than converting a failed lookup into a finding. We could not reach an artist-facing loudness document; that is not the same as Amazon having none. The TIDAL and Deezer rows are stronger, because in both cases we queried the help centre's own search index and it came back empty.

What Spotify publishes, word for word

Spotify's loudness normalisation page is the one piece of first-party documentation in this entire topic, so it is worth quoting rather than paraphrasing. It says tracks are adjusted to “-14 dB LUFS, according to the ITU 1770 standard”, that “negative gain is applied to louder masters” and “positive gain is applied to softer masters” to reach it.

On mastering it asks you to “keep it below -1dB TP (True Peak) max”, and adds that if your master is already louder than the target, keep true peak below -2 dB instead — the extra margin is there because a loud master has less room to absorb what lossy encoding does to inter-sample peaks.

The detail most tables leave out is that -14 is not the only number Spotify applies. Listeners pick a playback setting, and each one normalises to a different level.

Listener settingNormalises toWhat your -14 master does
Loud-11 dB LUFSGets 3 dB of gain, with Spotify's own limiting in the path
Normal (default)-14 dB LUFSPlays untouched — this is the setting to master for
Quiet-19 dB LUFSTurned down 5 dB; dynamics unaffected

That is the honest reason not to over-think the target. Your file is already being played back at three different levels depending on a setting you do not control, so the difference between landing at -14 and landing at -15 is noise inside a system that moves your track by five decibels on a listener's whim.

The Apple -16 that Apple never published

This is the row worth doing properly, because this page carried the -16 figure itself until today and we were wrong to.

Apple's own mastering document is the Apple Digital Masters guide. We downloaded the PDF, converted it to text and searched the whole thing: 5,443 words, and the strings “LUFS” and “LKFS” appear zero times. It is not buried in a footnote. It is not there.

What the guide does say about level is a headroom instruction — “our recommendation is to leave at least 1 dB of headroom”, to survive the oversampling in digital-to-analogue conversion — and then something close to the opposite of a target. Sound Check is described as letting listeners “hear all their songs at approximately the same loudness”, with no figure attached, and the guide closes the section by telling you to “always mix and master your tracks in a way that captures your intended sound, regardless of playback volume”.

Claim in circulationWhat Apple actually publishesWhere
“Apple Music targets -16 LUFS”No stereo loudness figure of any kindApple Digital Masters guide, searched in full
“Master to -16 for Apple”“Leave at least 1 dB of headroom”Same guide, clipping section
“Sound Check normalises to -16”“Approximately the same loudness” — no numberSame guide, Loudness Normalization section
(not in circulation)“Must not exceed -18 LKFS, per ITU-R BS. 1770-4”Video and Audio Asset Guide — Atmos and 5.1/7.1 only

That last row is the interesting one. Apple does publish a loudness figure, and nobody quotes it, because it is attached to a deliverable most independent artists never make. For Dolby Atmos and for 5.1 and 7.1 surround, integrated loudness “must not exceed -18 LKFS” with true peak at or below -1 dB TP. Note the verb: a ceiling you must stay under, not a target you aim at. And the same guide sets no loudness requirement for a stereo master at all.

So the -16 is a measurement of Sound Check's playback behaviour that has been reprinted long enough to acquire the authority of a spec. As an observation it is defensible. As a delivery target sitting in a table next to Spotify's published -14, it is a category error — and it is the one our own mastering walkthrough now corrects too.

Where the other five numbers come from

The honest answer is that they come from each other. The most thorough competitor page on this keyword — a 2026 guide running to nearly five thousand words — builds its table with an explicit “authority” column, and labels Apple Music, TIDAL, Deezer, Amazon, SoundCloud and YouTube as first-party.

Then its reference list cites a plugin vendor's engineering article for four of those rows, a production blog for Apple, and a listening-lab write-up cross-checked against YouTube's Stats for Nerds readout for the sixth. Only its Spotify and Netflix rows carry a direct link to the platform. The page is not dishonest — the references are right there for anyone who scrolls — but the table and the citations say different things, and the table is what gets screenshotted.

You can see the inheritance in the disagreements. Across the guides we read, TIDAL appears as -14 and as a -14 to -16 range; YouTube appears as -14 and as -14 to -23. Numbers that came from a published spec would not drift like that. Numbers that came from different people measuring playback on different material, at different times, drift exactly like that.

The genuinely published standard in this field is EBU R128, and it is worth knowing because it is where the vocabulary came from. It sets a Target Level of -23.0 LUFS with a ±1.0 LU tolerance, states that true peak “shall not exceed -1 dBTP”, and confirms that “LUFS” is equivalent to the “LKFS” used in ITU-R BS.1770. That -1 dBTP convention every guide repeats is not a streaming rule at all. It is a broadcast rule that streaming inherited.

What normalisation does to a loud master

Here is the mechanism, because it is worth being precise. The platform measures your integrated loudness, compares it to its target, and applies a gain offset on playback.

Deliver at -6 LUFS to Spotify's -14 and roughly 8 dB of negative gain is applied. Your track now plays at the same perceived level as everything else — but with whatever dynamic range you destroyed to reach -6 still destroyed. You paid the price and received nothing.

How Spotify loudness normalisation affects masters — comparison of an over-limited -6 LUFS master turned down 8 dB against a -14 LUFS master played at full level with dynamics intact

The reverse case is gentler. Spotify states that positive gain is applied to softer masters, so a quiet delivery gets turned back up. Being too quiet is the smaller error, because at least your dynamics survived the trip.

1
of 6 platforms publishes a target
0
LUFS mentions in Apple's own guide
-23
LUFS · the actual EBU standard
0
advantage from over-limiting

True peak, and why -1 dBTP

True peak measures the real analogue waveform between digital samples, which can rise above the highest sample your meter displays. Lossy encoding makes this worse — converting to AAC or MP3 reconstructs the waveform and can push inter-sample peaks higher still.

Unlike the loudness figures, this one has a paper trail. EBU R128 states plainly that the true peak level “shall not exceed -1 dBTP”, and notes that lower ceilings may be appropriate for data-reduced distribution. Spotify repeats the -1 and asks for -2 on masters already louder than -14. Apple asks for at least 1 dB of headroom and requires -1 dB TP on its immersive deliverables.

Three independent documents, one number. That is what a real convention looks like, and it is a useful contrast with the loudness column, where the agreement is an artefact of copying rather than of three parties arriving at the same place.

Practically: leave the ceiling at -1 dBTP and the encoder has room to work. Master to 0 dBFS and the encoded file can clip on playback while your original looked immaculate in the DAW.

Measure it yourself for nothing

Every route in this SERP is a vendor product, which is strange, because the measurement is a published standard and free software implements it. ffmpeg's loudnorm filter measures to ITU-R BS.1770 and costs nothing. We ran it in two passes on a deliberately over-limited test file while writing this, so the figures below are output we watched rather than output we are describing.

Pass one analyses and prints. Pass two takes those measured values back as arguments and writes the corrected file — the second pass matters, because a single-pass run guesses at material it has not finished reading yet.

StepWhat it reportedReading
Pass 1 · input-16.54 LUFS, -5.42 dBTP, LRA 2.30Where the file actually sat
Pass 1 · predicted-14.05 LUFSWhat it expects to achieve
Pass 2 · applied-14.2 LUFS, -2.9 dBTP, linearThe correction it made
ebur128 · verification-14.1 LUFS, peak -2.9 dBFSA different filter, same answer

That last row is the habit worth copying. The report printed by the filter that did the work is a prediction about a file it was still writing; re-measuring the finished file with ffmpeg's separate ebur128 filter is an independent check, and the two agreeing to within 0.1 LU is what tells you the pass did what it said.

What to do with the reading

If you need heavy limiting to reach -14, the mix is fighting itself. Balance and arrangement do that job better than a limiter ever will, and the result survives normalisation intact. And re-measure after you encode to AAC or MP3, because inter-sample clipping shows up in the version listeners actually receive, not in the master.

Why this matters on an AI release

Raw generator output frequently lands well off spec. Nothing in the generation process is aiming at a delivery target, so you get what you get, and on an AI-assisted release that is worth more attention than it would be otherwise — not because loudness is a detection signal, but because it reads as low-effort, and that impression attaches to a release that is already getting a closer look.

Keep the two problems separate in your head, because the industry conflates them constantly. Loudness is a quality question. Whether a platform tags your track as AI is a disclosure and screening question, and mastering has nothing to do with it.

YouTube settled this in its own documentation when it rolled out Gen AI labelling. Its help article lists automated AI mastering under the No Gen AI examples, alongside standard pitch correction, because the designation describes how the content was created. The declaration travels in delivery metadata from your distributor. No processing of the audio — mastering, cleanup, anything — changes it, and any tool that implies otherwise is selling you something it cannot deliver.

What processing genuinely addresses is narrower and worth being precise about: audible generation artifacts, and the automated screening some distributors run at upload. That is a real step with a real failure mode, and it is separate from both the loudness question above and the detection-accuracy question we have measured elsewhere.

Before the upload, not instead of the declaration

Clear the artifacts and the screening step

Undetectr targets audible generation artifacts and the automated screening distributors run at upload, and masters in the same pass. It does not and cannot change how a platform labels your track as AI — that is set by what your distributor declares.

What to actually do

Master to -14 LUFS integrated with -1 dBTP of true peak headroom. The advice has not changed; what has changed is that you now know it rests on one published figure from one platform rather than on a six-row consensus that does not exist.

That is a better position to be in, not a worse one. It tells you where the tolerance is. Nobody except Spotify has committed to a number you can miss, Spotify itself moves your track by five decibels depending on a listener's playback setting, and a landing zone of -16 to -13 is indistinguishable in practice from hitting -14 exactly. Spend the effort on the mix and stop chasing a decimal.

The instinct genuinely worth unlearning is that louder competes. Under normalisation it does the opposite: it hands away the dynamic range that would have made the track stand out, in exchange for a gain offset the platform immediately reverses.

And once the file is right, the harder problem is the one loudness cannot touch. Nobody is going to find a correctly mastered track by accident. If you have finished work sitting on a drive, a paid sync placement in TV, film, games or ads pays on a brief rather than on algorithmic reach — and selling direct to the listeners you already have beats waiting to be discovered by a recommendation engine. Getting the master to spec removes a reason to skip your track. It does not create a reason to play it.

Frequently asked questions

The Erasy logo mark, shown beside the author byline for Eddie Mathews, Editor

Eddie Mathews — Editor, Erasy

Eddie reads the help-centre article and the specification rather than the roundup, and marks the difference between what a company has documented and what a tutorial has assumed. Where the public record does not settle a question, this site says so.

What LUFS should I master to for Spotify?+
Spotify publishes the number: it normalises to -14 dB LUFS integrated, measured to the ITU 1770 standard, and asks you to keep true peak below -1 dBTP. That makes -14 the one platform target in this whole article you can point at a page and verify. Master much louder and Spotify applies negative gain, so you gave up dynamic range for nothing.
What LUFS does Apple Music use?+
Apple does not publish a LUFS figure for a stereo master. We downloaded Apple's own Apple Digital Masters guide and searched all 5,443 words of it: the strings "LUFS" and "LKFS" appear zero times. What Apple does publish is a headroom instruction — leave at least 1 dB — and the advice to master in a way that captures your intended sound regardless of playback volume. The -16 figure you see everywhere is a third-party measurement of Sound Check's behaviour, not an Apple specification.
So is the -16 LUFS figure for Apple Music wrong?+
It is not an Apple specification, which is the part that matters. As a rough description of where Sound Check lands a track on playback it is a reasonable observation, and people have measured it for years. The error is in how it gets presented: as a delivery target you are supposed to hit, sitting in a table next to Spotify's published -14 as though the two carried the same authority. One is a spec and the other is a measurement of someone else's playback.
Does Apple publish any loudness number at all?+
One, and it is for a different deliverable. Apple's Video and Audio Asset Guide requires that integrated loudness "must not exceed -18 LKFS, measured per ITU-R BS. 1770-4" for Dolby Atmos and for 5.1 and 7.1 surround, with true peak not exceeding -1 dB TP. That is a ceiling on an immersive file, not a target for a stereo master, and the guide sets no loudness requirement for stereo at all.
What is true peak and why -1 dBTP?+
True peak measures the analogue waveform level between digital samples, which can sit above your highest sample value. A -1 dBTP ceiling leaves lossy encoders room, because converting to AAC or MP3 reconstructs the waveform and can push inter-sample peaks higher than your digital meter showed. The figure is not arbitrary: EBU R128 states that true peak "shall not exceed -1 dBTP", and that is where the convention comes from.
How do I measure LUFS without buying anything?+
ffmpeg measures integrated loudness and true peak for free, to the same ITU-R BS.1770 standard the platforms use. Run its loudnorm filter in analysis mode to get your input figures, then apply those measured values in a second pass. Verify the file you wrote with the separate ebur128 filter rather than trusting the report from the filter that did the work.
Should I master separately for each platform?+
For one release, no. Only one platform publishes a target, most distributors accept a single master anyway, and normalisation is a gain offset rather than a quality judgement — being 1 or 2 LU off costs you nothing audible. A single file near -14 integrated with -1 dBTP of headroom is defensible everywhere, and the effort is better spent on the mix.
Does mastering my track change whether a platform labels it as AI?+
No. YouTube's own help documentation lists automated AI mastering under its No Gen AI examples, alongside standard pitch correction, because the designation describes how the content was created rather than what was done to the file afterwards. The declaration travels in delivery metadata. No amount of audio processing — mastering, cleanup or anything else — changes a platform's AI label.

Read at source on 24 October 2026: Spotify's loudness normalization page; Apple's Apple Digital Masters guide (PDF downloaded, converted to text and searched in full — 5,443 words, zero occurrences of LUFS or LKFS); Apple's Video and Audio Asset Guide for the -18 LKFS immersive ceiling; EBU R128 for the -23 LUFS target and the -1 dBTP rule; Deezer's volume normalisation article; and YouTube's recommended upload encoding settings. TIDAL's and Deezer's help centres were queried through their own search APIs because the pages block automated browsers; the zero counts are theirs, not ours. The Amazon Music row records a lookup we could not complete, not an absence we established. The ffmpeg figures are from a two-pass run on a synthetic test file in October 2026, reproducible with the loudnorm and ebur128 filters on any machine.