LUFS vs RMS vs Peak: What Each Loudness Meter Measures

Updated October 2026: a peak vs RMS vs LUFS comparison table, California's streaming-ad loudness law (in force since July 2026), current EBU R128 and ATSC A/85 revisions, and answers on −23 LUFS, RMS-to-LUFS conversion and peak-to-loudness ratio.

LUFS vs RMS vs peak: the short answer

Peak, RMS and LUFS answer three different questions. Peak (dBFS) is the single highest sample and tells you how close you came to clipping. RMS (dB RMS) is the average energy over a short window, with every frequency counted equally. LUFS (Loudness Units relative to Full Scale, defined in ITU-R BS.1770-5) is perceived loudness: the energy after K-weighting filters it like an ear and gating drops the silences. Use LUFS for loudness targets such as −23 LUFS or −14 LUFS, True Peak (dBTP) for the ceiling, and RMS only as a rough mixing guide. The one-line definition of the unit lives in our glossary entry for LUFS.

Table 1. Peak vs RMS vs LUFS at a glance. Sources: ITU-R BS.1770-5 (2023), EBU Tech 3341.

Why this matters

If you run any video product — a streaming service, an OTT platform, a conferencing app, a telemedicine tool — the loudest complaint you will ever get is about loudness: the ad that blares, the next episode that whispers, the one speaker on the call nobody can hear. Fixing that starts with measuring it correctly, and most teams measure it wrong because they reach for a peak meter that has nothing to do with perceived loudness. This article is the foundation: it defines every term you need before you can read the platform-target tables, the normalization standards, and the true-peak limiting rules in the rest of this section. Read it once and the words "−14 LUFS, −1 dBTP" stop being jargon and become an instruction you can act on.

The blaring ad is also becoming a legal problem outside broadcast. California's SB 576, signed on 6 October 2025 and in force since 1 July 2026, bars streaming services from playing ads louder than the programme they accompany, and the FCC opened a rulemaking on its CALM Act rules in February 2025 (MB Docket No. 25-72) that asks about streaming as well. SB 576 ties compliance to the FCC's CALM Act rules, which measure with ATSC A/85 in LKFS, the unit this article defines; we found no final FCC order in that docket as of our October 2026 check. The rules themselves are covered in loudness normalization with EBU R128, BS.1770 and ATSC A/85.

First, the decibel: it is a ratio, not a unit of loudness

Almost every confusion about loudness traces back to the decibel, so we start there. The decibel, written dB, is not a fixed amount of anything — it is a way of expressing how many times bigger one value is than another, on a compressed scale. It is a ratio, like "twice as much" or "a tenth as much", dressed up in logarithms so that very large and very small ratios fit on the same axis.

The reason audio uses a logarithm is that hearing is logarithmic. Going from a whisper to a normal voice and from a normal voice to a shout each feel like one "step up", even though the second step carries far more physical energy. A logarithm turns those equal-feeling steps into equal-sized numbers, which is exactly what we want from a loudness scale.

Because a decibel is a ratio, it always needs a reference — the "compared to what". When you see a suffix after dB, that suffix names the reference. dBFS means decibels relative to full scale, where 0 dBFS is the loudest sample a digital system can store and every real signal sits below it as a negative number. So −6 dBFS is half the maximum amplitude, −12 dBFS is a quarter, and so on. Here is the only piece of decibel arithmetic you need to keep:

a change of +6 dB  ≈ double the amplitude
a change of −6 dB  ≈ half the amplitude
a change of +20 dB = ten times the amplitude

Hold onto two ideas from this section. First, a decibel describes a ratio, never an absolute loudness. Second, the suffix (FS, TP, or the LUFS family below) tells you the reference the ratio is measured against. Every term in this article is a different answer to the question "decibels compared to what, and measured how".

Peak: the highest single sample, and why it lies about loudness

The simplest thing a meter can report is the peak: the value of the single loudest sample in a stretch of audio, expressed in dBFS. A peak meter answers one narrow question — how close did the signal come to the digital ceiling at 0 dBFS, beyond which samples "clip" and distort. That is a real and useful question. It is just not the same question as "how loud is this".

The reason peak fails as a loudness measure is that loudness is about sustained energy over time, while a peak is one instant. Consider two clips. The first is a steady, dense pop master that sits near the top of the scale for three full minutes. The second is a sparse acoustic recording that is quiet almost everywhere except for one sharp drum hit that briefly touches the same level. A peak meter reports the same number for both, because both reached the same single highest sample. Your ears report that the first clip is dramatically louder, because it delivers far more energy across the whole duration. Peak measured the spike; it never measured the sustained loudness that the ear actually integrates.

There is a subtler problem with peak that we flag now and cover in depth later. The "peak" a normal meter shows is the highest stored sample — but when a digital signal is reconstructed back into a continuous analog wave for your speakers, the smooth curve drawn between samples can rise higher than any individual sample. That hidden overshoot is the inter-sample peak, and the measurement that catches it is True Peak, in dBTP. We define it properly in the True Peak section below; for now, just remember that even the peak number you trust can under-read the real signal.

RMS: an average of energy, closer but still not loudness

If a single peak is too narrow, the natural fix is to average. RMS — short for root mean square — is a way of averaging a signal's energy over a window of time rather than reporting one instant. The name describes the recipe: square every sample (which makes negatives positive and weights big values heavily), take the mean of those squares over the window, then take the square root to get back to the original scale. The result is a number that tracks the sustained level of the audio, not its momentary spikes.

RMS is a real step toward loudness. Go back to the two clips above: RMS correctly reports the dense pop master as far higher than the sparse acoustic track, because it measures energy across the window instead of one sample. For decades RMS-style meters (VU meters and their descendants) were the best practical loudness indicator available, and they are still useful.

But RMS has one blind spot that the ear does not share: it treats every frequency as equally loud. Human hearing does not. We are most sensitive to the midrange — roughly the band where speech lives — and much less sensitive to very low bass and very high treble at the same physical energy. A track with heavy sub-bass can carry enormous RMS energy down low that you barely perceive as loudness, while a track with a strong vocal presence can feel loud at lower RMS. RMS measures the energy correctly; it just measures it as if your ear were flat, and your ear is not. Closing that gap is the whole job of the next measurement.

One more trap hides in the words dB RMS and RMS dBFS: meters disagree by 3 dB about what a full-scale signal reads. Under the convention of AES17, the Audio Engineering Society's measurement standard, a full-scale sine wave reads 0 dBFS RMS, while a plain mathematical RMS of the same sine is −3.01 dBFS, because the RMS of a sine is 0.707 of its peak. Before you compare two RMS readings, check which convention each meter uses and what window it averages over; LUFS removes both ambiguities by fixing the filter, the windows and the calibration in one standard.

LUFS: loudness measured the way the ear hears it

This is the term the rest of the section is built on, so we define it carefully and in plain language first. LUFS stands for Loudness Units relative to Full Scale. It is a number, expressed on a decibel-style scale below a 0 ceiling (so real audio is negative, like −23 LUFS or −14 LUFS), that is engineered to match perceived loudness — how loud a human actually judges the audio to be — rather than its raw electrical energy.

LUFS is not a vendor's idea. It is defined by an international standard, ITU-R BS.1770, currently in revision 5 (published November 2023), titled Algorithms to measure audio programme loudness and true-peak audio level. When a streaming platform says "we normalize to −14 LUFS", it is pointing at a specific, reproducible algorithm from that document. The algorithm has three moving parts, and you can understand all three without any heavy math.

Part one: K-weighting — filter the audio like an ear

Before measuring energy, the algorithm passes the audio through a fixed two-stage filter called K-weighting, which reshapes the sound to approximate the ear's own frequency sensitivity. The filter does two simple things. It rolls off the deep bass with a high-pass filter (energy below roughly 100 Hz counts progressively less, about 6 dB less near 40 Hz, because we perceive it as less loud), and it gives a gentle boost of roughly +4 dB to the high frequencies above about 2 kHz with a "high-shelf" filter, reflecting the slight emphasis the head and ear add up there. K-weighting is the step that fixes RMS's blind spot: after this filter, equal measured energy corresponds much more closely to equal perceived loudness.

Part two: mean energy — average across the program

After K-weighting, the algorithm measures the mean energy (a root-mean-square-style power average) of the filtered signal across the whole piece of audio. For multichannel audio it sums the channels, and here is the one number worth remembering: the surround channels are weighted slightly higher (a factor of about 1.41, roughly +1.5 dB each) because sound arriving from behind is perceived as a touch louder, while the low-frequency-effects (LFE) "point-one" channel is left out of the loudness sum entirely. The summed, weighted energy is converted to the LUFS scale with a fixed calibration offset built into the standard, chosen so that a 0 dBFS, 1 kHz sine wave in the left, centre or right channel reads −3.01 LUFS.

Part three: gating — ignore the silences

A long film is full of quiet passages and outright silence. If you averaged those into the loudness number, a dialogue-heavy drama with long pauses would measure artificially quiet, and you would over-boost it. So BS.1770 applies gating: it measures the audio in short overlapping blocks of 400 milliseconds and throws away the blocks that fall below two thresholds. First, an absolute gate discards anything below −70 LUFS — true silence and room tone. Then a relative gate discards anything more than 10 LU below the average of what remains — the merely quiet moments. The final integrated loudness is the average of only the blocks that survived gating: the parts a listener would actually call "the program".

The payoff of all three steps together: two clips with the identical peak and even similar RMS can land 8 LUFS apart, and the LUFS number will agree with which one your ears call louder. That is why the entire streaming and broadcast world standardized on it.

There is no fixed formula to convert RMS to LUFS for that reason. The gap depends on how much of the energy sits in the bass, how much of the clip is silence, and which RMS window your meter uses. On full-band material such as pink noise the two readings land within a few dB of each other; on bass-heavy music or speech with long pauses they drift apart. If a spec is written in LUFS, measure LUFS. Psychoacoustic research uses two other units: the phon, built on the ISO 226:2023 equal-loudness contours for pure tones, and the sone, computed by the ISO 532 loudness models. Both are research tools; for programme audio in products, LUFS is the unit.

Figure 1. The same audio, three measurements: peak reports the loudest instant, RMS reports average energy, and LUFS reports perceived loudness after filtering like an ear and ignoring the silences.

Figure 2. The three real steps of the BS.1770 algorithm — filter like an ear, average the energy, drop the silent blocks — turn a raw waveform into one integrated LUFS number.

The vocabulary around LUFS: LU, LKFS, M, S, I

Four more words travel with LUFS, and they trip people up only because they are never defined. Here they are, each in one line.

LKFS (Loudness, K-weighted, relative to Full Scale) is the same number as LUFS — the same scale, the same algorithm. The two are interchangeable; North American broadcast documents (and the US CALM Act) write LKFS, while European documents write LUFS. If a spec says −24 LKFS and another says −24 LUFS, they mean the identical thing.

LU (Loudness Unit) is the relative cousin of LUFS. One LU equals one dB of loudness difference. You use LUFS for an absolute measurement ("this track is −16 LUFS") and LU for a difference or a tolerance ("turn it down 3 LU", "±1 LU allowed"). Same scale, but LUFS is anchored to full scale and LU is a gap between two loudnesses.

That answers a question we see often: what is −23 LUFS in dB? It is a K-weighted, gated loudness 23 LU (23 dB) below the 0 LUFS reference of the scale, and it is the EBU R128 broadcast target. Because a full-scale 1 kHz sine reads −3.01 LUFS, a 1 kHz tone at −23 LUFS peaks at about −20 dBFS. It is not the same as −23 dBFS peak or −23 dB RMS: a programme at −23 LUFS usually has peaks much higher than −23 dBFS, and its RMS reading depends on the meter. Likewise, −14 LUFS is 9 LU louder than −23 LUFS, which is exactly how much gain a normalizer applies to move between the two.

The last three are the time windows the standard meters report, and you read all three on a real loudness meter. Momentary (M) loudness is measured over the most recent 400 ms — the instantaneous feel. Short-term (S) loudness is measured over the most recent 3 seconds — useful for catching a section that drifts loud or quiet. Integrated (I) loudness is the single gated average over the entire program — this is the number you deliver against, the one a platform checks for compliance.

For loudness monitoring, live operators watch Momentary and Short-term on an "EBU Mode" meter (EBU Tech 3341), while file-based QC reads Integrated, LRA and True Peak once per asset. Any BS.1770 meter does the file job; the free FFmpeg ebur128 filter is enough for a pipeline check:

ffmpeg -nostats -i episode.mov -vn -af ebur128=peak=true -f null -
# per-frame lines first, then a summary: I (LUFS), LRA (LU), True peak
# FFmpeg prints the true-peak value with a "dBFS" label: read it as dBTP

Loudness Range (LRA): how much the loudness moves

Integrated loudness gives you one number for a whole program, but it hides an important thing: how consistent that loudness is. A talk-radio show and a film with whispered dialogue and explosions can share the same integrated LUFS while feeling completely different to listen to. Loudness Range, abbreviated LRA and measured in LU, captures that spread — it describes how much the loudness varies across the program, from its quiet passages to its loud ones.

LRA is defined in EBU Tech 3342, a companion to the EBU R128 recommendation. The method measures short-term loudness across the whole program, builds a statistical distribution of those values, and reports the spread between roughly the 10th and 95th percentiles (after its own gating). A small LRA, perhaps 3–5 LU, means tightly controlled, consistent loudness — typical of a pop master or a podcast. A large LRA, 15 LU or more, means a wide dynamic journey — typical of a film score or a classical recording.

Why you care: LRA tells you whether a piece of audio will survive a loud, distracting environment. A film with a 20 LU range sounds magnificent in a quiet cinema and becomes unwatchable on a phone in a moving train, because the quiet dialogue disappears under the noise. Knowing the LRA before delivery tells you whether you need a separate, more compressed mix for mobile. It is a planning number, not a compliance number.

True Peak and dBTP: the overshoot a normal peak meter misses

We promised to return to this, and it matters enough to earn its own section. A standard peak meter reports the highest stored sample value. But audio is not played back as a staircase of discrete samples — a digital-to-analog converter reconstructs a smooth continuous wave that passes through those sample points. Between two samples, that reconstructed curve can rise higher than either sample on its own. That hidden overshoot is the inter-sample peak, and a sample-peak meter is blind to it.

True Peak, measured in dBTP (decibels True Peak), is the measurement that catches it. The method, also defined in ITU-R BS.1770, is to oversample the signal — typically by 4× — which means mathematically inserting interpolated points between the real samples to estimate the continuous wave, then reading the true maximum of that denser curve. The number it returns is often a few tenths of a dB higher than the sample peak, and occasionally more than a full dB higher.

A master that reads exactly 0.0 dBFS on a sample-peak meter can have true peaks at +0.7 dBTP or higher. When that file is decoded — especially after a lossy codec like AAC, which can add its own overshoot — those inter-sample peaks clip the analog stage of a phone or a pair of earbuds and you hear crackle. That is why streaming platforms set a True Peak ceiling below zero: the EBU R128 maximum permitted level is −1 dBTP, and most streaming services adopt −1 dBTP as well, leaving headroom for the overshoot the sample meter never showed. (The deep dive on inter-sample peaks and limiting lives in True peak, dBTP and the inter-sample peak problem.)

Figure 3. Every stored sample sits under 0 dBFS, yet the reconstructed analog wave overshoots the ceiling between samples — the inter-sample peak that True Peak (dBTP) catches and sample peak misses.

Putting the numbers together: a worked reading

Let the four measurements speak together on one imaginary delivery. Suppose your loudness meter, run across a finished 30-second commercial, reports this:

Integrated loudness  = −18.0 LUFS
Loudness Range (LRA) =   4.0 LU
True Peak (max)      =  −0.4 dBTP
Sample peak (max)    =  −1.1 dBFS

Read it as a sentence. The commercial's overall perceived loudness is −18.0 LUFS, which is moderate — louder than the −23 LUFS broadcast norm, quieter than a −14 LUFS music-streaming target. Its loudness range of 4.0 LU is narrow, so it is consistently loud throughout, with no quiet passages that will vanish on a phone. But look at the peaks: the sample peak is a comfortable −1.1 dBFS, yet the True Peak is −0.4 dBTP — the inter-sample overshoot added 0.7 dB the sample meter never showed. If your delivery spec demands −1 dBTP, this file fails on true peak despite looking safe on the sample meter, and you would lower it or apply a true-peak limiter before delivery. One derived number is worth reading too: the peak-to-loudness ratio (PLR), true peak minus integrated loudness. Here it is −0.4 − (−18.0) = 17.6 dB. A low PLR means a dense, heavily limited master; a high PLR means transients have room to breathe. Normalization makes PLR matter, because once every track plays at the same LUFS, the one with more peak-to-loudness headroom sounds punchier.

That single reading is the whole article in miniature: peak protects against clipping, True Peak protects against the hidden clipping, LUFS describes perceived loudness, and LRA describes how much that loudness moves.

A common mistake: "I normalized to 0 dB, so it's as loud as possible"

The single most frequent loudness error we see is treating peak normalization as loudness normalization. Peak normalization raises a file until its loudest sample just touches 0 dBFS (or some ceiling). It guarantees you used the full digital range — and it tells you almost nothing about how loud the result feels. Two files both peak-normalized to 0 dBFS can be 10 LUFS apart in perceived loudness, because one is dense and sustained and the other is sparse with one tall transient.

The consequence shows up the moment your audio meets a modern platform. Spotify, YouTube, Apple Music, and broadcast chains do not care about your peak — they measure your integrated LUFS and turn loud tracks down (and, on some services, quiet tracks up) to hit their target. Spotify, for example, normalizes to −14 LUFS by default, −11 LUFS on its Loud setting and −19 LUFS on Quiet, and asks for true peak at or below −1 dBTP, or −2 dBTP for masters louder than −14 LUFS (Spotify for Artists, checked October 2026). Long-form video is anchored differently: Netflix measures dialogue-gated loudness (loudness measured only where speech is detected) at −27 LKFS ±2 LU with a −2 dBTP ceiling; the full table is in LUFS targets per platform in 2026. A track you "maximized" to 0 dBFS but that sits at −9 LUFS will simply be turned down by the platform to match a −14 LUFS target, and all the clipping you risked to get loud buys you nothing. The fix is to mix and master to a LUFS target and a dBTP ceiling, not to a peak. Loudness is the goal; peak is only a safety rail.

LUFS, RMS and peak FAQ

What does LUFS stand for?

LUFS stands for Loudness Units relative to Full Scale. It is the unit of perceived loudness defined in ITU-R BS.1770-5 (November 2023); LKFS (Loudness, K-weighted, relative to Full Scale) is the same unit under its North American name.

LUFS vs RMS: which one should I use?

Use LUFS for anything you deliver, because platforms and broadcasters set their targets in LUFS or LKFS. RMS is fine as a quick density check while mixing, but it ignores how the ear weights frequencies and it averages silences in.

Can you convert RMS to LUFS?

No, not with a fixed formula. LUFS adds K-weighting and gating, so the gap between the two readings changes with the bass content, the amount of silence and the RMS window of your meter. Measure LUFS directly.

What is −23 LUFS in dB?

−23 LUFS is a perceived loudness 23 LU (23 dB) below the 0 LUFS reference of the K-weighted, gated BS.1770 scale, and it is the EBU R128 broadcast target. It is not −23 dBFS peak: peaks in a −23 LUFS programme sit much higher.

Is LKFS the same as LUFS?

Yes. LKFS and LUFS are the same measurement on the same scale; ATSC A/85 and the US CALM Act write LKFS (−24 LKFS), and EBU R128 writes LUFS (−23 LUFS). One LU equals one dB of loudness difference.

What is the peak-to-loudness ratio?

The peak-to-loudness ratio (PLR) is the maximum true peak minus the integrated loudness. A master at −1 dBTP and −14 LUFS has a PLR of 13 dB; higher values mean more transient headroom.

What loudness does Netflix require?

Netflix asks for dialogue-gated loudness (measured only on speech) of −27 LKFS ±2 LU, with BS.1770 as the measurement basis, and a true peak no higher than −2 dBTP. Per-platform targets are collected in our LUFS targets per platform in 2026 article.

What is loudness measured in?

Programme loudness is measured in LUFS (or LKFS), and loudness differences in LU. The phon (ISO 226:2023 equal-loudness contours) and the sone (ISO 532 loudness models) are psychoacoustic research units.

Where Fora Soft fits in

In the products we have built since 2005 — video streaming and OTT platforms, e-learning, telemedicine, and live conferencing — loudness is rarely a "nice to have"; it is where users notice the seams. On streaming and OTT work we measure every asset's integrated LUFS and True Peak before it enters the library, so an episode, an ad, and a trailer do not jump in volume when they play back to back. In real-time conferencing and telemedicine, the same vocabulary drives the automatic-gain and leveling stages that keep a soft-spoken patient and a loud clinician at a comfortable, even level. The recurring lesson across all of them is the one this article teaches: measure perceived loudness with LUFS and guard the ceiling with dBTP, and the "why is this so loud / so quiet" tickets mostly disappear. Our audio processing software development team builds LUFS metering, true-peak limiting and leveling into the pipeline, and our streaming development work keeps loudness consistent from ingest to playback. For VOD libraries and ad-supported channels, where California's SB 576 now applies to streaming ads, our OTT and IPTV platform development team builds the per-asset LUFS and dBTP checks into ingest and ad insertion.

The book

Audio for Video: A Complete Guide to Sound in Video Products: From PCM and Codecs to Loudness, Accessibility, and Real-Time Voice Processing

Loudness is named in this volume's title, and the chapters behind that word are where the vocabulary you just learned turns into a delivery process: the full BS.1770 algorithm with its filter curves and gating thresholds, EBU R128 and ATSC A/85 side by side, LRA and true-peak limiting, and the meters and command-line tools that report them. It gets there from the material itself — sampling, bit depth, channels and the codecs your renditions are encoded with — so a number like −16 LUFS stops being a target someone handed you and becomes one you can defend. 1,229 pages, and the real-time voice chain that has to hit the same levels live is in the same book. Written by Nikolay Sapunov, CEO at Fora Soft.

Read it on Amazon →Kindle & paperback · Fora Soft Video Engineering Handbook

See our case studies

References

1. ITU-R BS.1770-5, Algorithms to measure audio programme loudness and true-peak audio level (November 2023). The controlling specification for LUFS/LKFS: the two-stage K-weighting filter, the multichannel energy sum with surround weighting (~+1.5 dB) and LFE excluded, the 400 ms gating blocks with 75% overlap, the −70 LKFS absolute gate and −10 LU relative gate, and the 4× oversampled True Peak (dBTP) measurement. https://www.itu.int/rec/R-REC-BS.1770/
2. EBU R128 v5.0, Loudness normalisation and permitted maximum level of audio signals (November 2023; checked October 2026). Defines the −23 LUFS programme target, the ±0.5 LU tolerance (±1 LU for live), and the −1 dBTP maximum permitted true-peak level that this article cites for the streaming ceiling. https://tech.ebu.ch/files/live/sites/tech/files/shared/r/r128v5_0.pdf
3. EBU Tech 3341, Loudness Metering: 'EBU Mode' metering to supplement EBU R128 loudness normalisation. Source for the Momentary (400 ms), Short-term (3 s), and Integrated meter definitions used in the vocabulary table. https://tech.ebu.ch/docs/tech/tech3341.pdf
4. EBU Tech 3342, Loudness Range: A measure to supplement EBU R128 loudness normalisation. Defines Loudness Range (LRA) in LU as the statistical spread of short-term loudness across a programme. https://tech.ebu.ch/docs/tech/tech3342.pdf
5. ITU-R BS.1771-1, Requirements for loudness and true-peak indicating meters. Companion to BS.1770 specifying how compliant loudness and true-peak meters must behave. https://www.itu.int/rec/R-REC-BS.1771/
6. ATSC A/85:2026-07, Techniques for Establishing and Maintaining Audio Loudness (July 2026; the first major revision since 2013, with new annexes on streaming and a loudness and true-peak quick reference; the "CALM Act" recommended practice). Source for the North American −24 LKFS practice and the LKFS terminology, distinguished here from the EBU's −23 LUFS. https://www.atsc.org/atsc-documents/a85-techniques-for-establishing-and-maintaining-audio-loudness-for-digital-television/
7. EBU Tech 3344, Guidelines for distribution and reproduction in accordance with EBU R 128. Source for the extra true-peak headroom that lossy codecs need at the distribution stage, the reason streaming ceilings sit at −1 dBTP or lower. https://tech.ebu.ch/docs/tech/tech3344.pdf
8. Lund, Thomas, ITU-R BS.1770 Revisited (TC Electronic). Engineering paper on the rationale and behaviour of the BS.1770 gating and K-weighting design, used here for the plain-language explanation of why gating exists. http://magnetic.beep.pl/Loudness/Lund_BS1770_revisited.pdf
9. California Senate Bill 576 (Umberg), streaming-service commercial loudness, signed 6 October 2025, operative 1 July 2026 (bill text: leginfo.legislature.ca.gov, bill 202520260SB576); reported by ABC7, October 2025. https://abc7.com/post/gov-newsom-signs-new-california-law-limiting-volume-ads-streaming-platforms/17963511/
10. FCC, Notice of Proposed Rulemaking FCC 25-16 on the CALM Act rules, MB Docket No. 25-72 (adopted 27 February 2025; Federal Register, 11 March 2025), including questions on streaming loudness. https://www.govinfo.gov/content/pkg/FR-2025-03-11/html/2025-03800.htm
11. Spotify for Artists, Loudness normalization (checked October 2026): −14 LUFS Normal, −11 LUFS Loud, −19 LUFS Quiet; true peak ≤ −1 dBTP, or ≤ −2 dBTP for masters louder than −14 LUFS. https://support.spotify.com/us/artists/article/loudness-normalization/
12. FFmpeg Filters Documentation, ebur128: EBU R128 / BS.1770 loudness meter with true-peak mode. https://ffmpeg.org/ffmpeg-filters.html#ebur128-1

How we sourced this: every number about the LUFS algorithm (K-weighting, gating thresholds, block length, surround weighting, 4× true-peak oversampling) comes from ITU-R BS.1770-5 itself, and every target from the body that publishes it, not from secondary summaries. Checked October 2026.