---
title: "Peak-to-Loudness Ratio (PLR): Meaning and Limits | Gawergy Audio"
description: "Learn how PLR relates maximum true peak to integrated BS.1770 loudness, how it differs from crest factor, and why it is a descriptor rather than a target."
canonical_url: "https://gawergy.com/learn/peak-to-loudness-ratio"
md_url: "https://gawergy.com/learn/peak-to-loudness-ratio.md"
last_updated: "2026-09-23"
date_published: "2026-09-23"
---

# What Is Peak-to-Loudness Ratio (PLR)?

Peak-to-Loudness Ratio, or PLR, compares an audio segment's maximum true-peak level with its integrated loudness measured under BS.1770. It describes how far the programme's loudness sits below its highest reconstructed peak. That can inform distribution and dynamics discussions, but PLR is not a complete measure of punch, artistic quality, or the behavior of individual transients.

## Key takeaways

- AES guidance defines PLR from maximum true peak and integrated BS.1770 loudness over the same content segment.
- PLR differs from crest factor, which typically compares a peak with RMS over a specified window.
- A high PLR can reflect meaningful transients or one isolated outlier; the number alone does not distinguish them.
- There is no universal PLR target that makes every song better.

## What the AES definition actually says

The Audio Engineering Society's streaming-loudness technical document defines PLR as the relationship between a content segment's maximum true peak and its integrated BS.1770 loudness. In practical meter displays, the two reported levels are compared as a difference between dBTP and LUFS values, with the same segment defining both measurements. The result expresses a peak-to-programme-loudness gap. If a song's true peak stays fixed while its integrated loudness rises, that gap narrows; if loudness remains fixed while a taller true peak appears, the gap widens. Those are mathematical consequences of the definition, not judgments about music.

The *true-peak* part is important. PLR is not defined from the largest stored sample in the AES document. A reconstructed waveform can peak between samples, so a sample-peak substitution can change the value. The *integrated loudness* part also matters: it is not a short-window RMS value or a listener's subjective rating. ITU-R BS.1770 specifies the relevant loudness and true-peak methods. The [true-peak limiting article](/learn/true-peak-limiting) addresses controlling the maximum; the [RMS versus LUFS article](/learn/rms-vs-lufs) explains why an unweighted average does not stand in for standardized loudness.

Always state the segment. A PLR calculated for an entire song can differ from one calculated for a chorus, an intro, or a short transition, even when the same file is involved. The maximum may be set by one event while integrated loudness reflects the whole selected interval under its method. Comparing a whole-song PLR with a chorus-only PLR without identifying scope is misleading. The measure is meaningful only when both component readings refer to the same content and measurement conventions.

## PLR and crest factor are related but not identical

Crest factor commonly compares peak amplitude with RMS effective amplitude over a specified window. PLR uses a maximum true-peak estimate and integrated standardized loudness. Since RMS and LUFS differ in weighting, gating, time definition, and possibly channel handling, the two ratios need not match. A source spectrum can change the LUFS relationship without moving unweighted RMS by the same amount. A long quiet section can affect a whole-file RMS average differently from gated integrated loudness. The [crest-factor guide](/learn/crest-factor-music-production) covers the RMS-based concept more deeply.

The difference also affects interpretation. A short local crest-factor measurement can describe the attack relative to a nearby body. A whole-program PLR may be shaped by a maximum anywhere in the programme and integrated loudness across the selected segment. It is therefore a broad descriptor for distribution and programme dynamics questions, not an exact readout of one drum's punch. The AES document discusses PLR in the context of distribution loudness and peak control, which is a different context from source-level transient editing.

Neither ratio should be confused with EBU Loudness Range. LRA uses a distribution of short-term loudness readings to describe variation over longer time; it intentionally resists domination by isolated extremes. PLR explicitly includes the maximum true peak, so one unusual event can influence it. The [LRA guide](/learn/loudness-range-lra) explains why that statistical descriptor answers another question. Saying a master has 'good dynamics' because one of these numbers is high collapses distinct timescales and methods.

## Why PLR matters when playback gain is considered

A platform that raises a quiet master toward a playback reference can be constrained by that master’s highest peak. A larger gap between maximum peak and programme loudness may mean less simple upward gain is available under a fixed ceiling. The AES streaming document discusses distribution peak control and loudness management in this context. Spotify's current artist documentation similarly says it considers headroom when applying positive normalization gain. These are distribution relationships, not evidence that a master should be reshaped to hit a particular PLR.

Turning a master down through constant playback gain shifts peak and programme loudness together by roughly the same amount, so their difference remains broadly the same under consistent measurement. A subsequent limiter, codec, or other nonlinear process may change the relationship. The [loudness-normalization article](/learn/loudness-normalization) explains the basic gain model and its exceptions. This illustrates why PLR can remain informative even when absolute playback level moves: it describes a relationship within the content under the chosen measurement method.

A high PLR is not necessarily a problem for a listener. It can reflect intentional dynamic space, and a platform may choose to play the content below its nominal reference rather than force it through damaging peak control. Conversely, a very low PLR can reflect a dense aesthetic that an artist deliberately wants. The AES document's distribution recommendations are directed primarily to service behavior, not a universal mastering recipe. Keep that institutional context when interpreting its language about peak control.

## One peak can dominate a programme value

Because PLR uses the *maximum* true peak, a single brief outlier can raise the reported ratio even if it contributes little to the integrated loudness. The value may then say more about one event than about typical transients across the song. If that outlier is an accidental click, it may be reasonable to investigate it; if it is an intentional accent, removing it merely to lower PLR could damage the arrangement. The number tells you where to look, not what to do. A waveform and an event-level audition can identify whether the maximum is representative.

A different programme can have many strong attacks but no one extreme outlier. Its PLR might be similar to that of the first programme while the musical motion is very different. Spectrum and temporal structure also affect integrated loudness, so two programmes with the same PLR can have different perceived density. The [same-LUFS-different-loudness article](/learn/same-lufs-different-loudness) examines related perceptual limits of integrated loudness. PLR inherits those limits and adds the sensitivity of a maximum measure.

The reverse problem is also possible: a programme's loudness can rise through sustained energy while the maximum stays near a ceiling. PLR narrows, but the music may feel intentionally fuller rather than objectively worse. A clipped or limited version might have a lower ratio and a more appropriate aesthetic, or might lose valued transient detail. Listening at a matched output level is necessary to decide. The [peak-control versus loudness article](/learn/peak-control-vs-loudness) explains why the measurement change and sonic judgment must be separated.

## Compare like with like before interpreting a change

Use a true-peak meter consistent with the relevant standard and an integrated loudness meter over the same final segment. Reset the meters appropriately and check whether a codec, sample-rate conversion, or downstream gain stage changed the file after the initial measurement. FabFilter's Pro-L 2 offers both loudness and true-peak displays; its documentation also notes small true-peak differences between compliant meters. A minor meter disagreement does not necessarily imply a meaningful change to the audio. A large disagreement calls for checking mode, signal path, and analyzed interval.

The measurement can be reported precisely: maximum true peak of the exported PCM file, integrated LUFS of that same file, and PLR under those definitions. If an encoded version is the delivery artifact, it can be measured separately rather than assuming it has the identical peak. Do not mix a plug-in's pre-export peak with a platform's post-encode loudness and call the difference a single authoritative PLR. The [sample-peak versus true-peak article](/learn/sample-peak-vs-true-peak) explains the peak-side measurement point.

Interpret the number together with its components. A PLR can change because the true peak moved, because the integrated loudness moved, or both. Those paths have different sonic implications. A brief clip of one attack, broad compression of a phrase, and a static gain offset can all affect meter readings differently. Naming the cause is more useful than celebrating or fearing a standalone ratio.

## No PLR value is a universal quality score

The AES document notes that excessive peak limiting can make programme material less clear or more fatiguing, and that a higher peak-to-loudness ratio can be associated with a clearer result in some contexts. That is a contextual observation, not proof that raising PLR always improves music. An uncorrected spike can inflate the ratio; a delicate sustained passage can have a modest ratio while sounding beautiful. Production aesthetics, genre, playback conditions, and listener intent remain decisive. The [louder-master article](/learn/louder-master-not-always-better) treats those tradeoffs without moralizing against loud masters.

The practical role of PLR is diagnostic. It links a final reconstructed maximum with broad standardized loudness so distribution constraints and programme density can be discussed clearly. It can flag unusual relationships worth investigating, but it cannot describe every attack, the movement between sections, or the subjective power of the track. Crest factor, LRA, short-term loudness, waveform inspection, and listening may answer complementary questions. Each should be chosen because it fits the problem, not because more metrics must always be collected.

The key boundary is between understanding and a recipe. PLR tells you what was measured. It does not prescribe a target, a limiter setting, a shaved-peak amount, or a processing chain for any source. Public engineering knowledge is most useful when it reveals why measurements differ and when they apply. The artistic decision still belongs to the music.

## About G-Clipper Pro

G-Clipper Pro may change the maximum peak and broad loudness differently. PLR describes the measured relationship after processing; it is not a G-Clipper setting target.

## Sources & References

- [Recommendations for Loudness of Internet Audio Streaming and On-demand Distribution](https://aes.org/wp-content/uploads/2024/01/20210924_TD1008_v3.13.pdf)
- [BS.1770: Algorithms to measure audio programme loudness and true-peak audio level](https://www.itu.int/rec/R-REC-BS.1770-5-202311-I)
- [FabFilter Pro-L 2 Help - Metering](https://www.fabfilter.com/help/pro-l/using/metering)
- [FabFilter Pro-L 2 Help - Loudness metering](https://www.fabfilter.com/help/pro-l/using/loudnessmetering)
- [Loudness normalization on Spotify](https://support.spotify.com/au/artists/article/loudness-normalization/)

## Continue Reading

- [Crest Factor in Music Production](https://gawergy.com/learn/crest-factor-music-production)
- [What Is Loudness Range (LRA)?](https://gawergy.com/learn/loudness-range-lra)
- [True Peak Limiting: What It Is and What It Isn’t](https://gawergy.com/learn/true-peak-limiting)

## Sitemap

See the full [Gawergy.com sitemap](https://gawergy.com/sitemap.md).