The confusion around true peak vs peak mastering is why your mastered track keeps getting rejected by Spotify.
You hit 0 dBFS thinking you’ve maximized loudness, but streaming platforms see something different. The AAC encoding process can add up to 1 dB of peak level to your file. What looked clean in your DAW causes distortion after upload. Spotify requires -1 dBTP on quieter masters and -2 dBTP on louder ones, while Apple Music asks for -1 dBTP. Understanding what true peak is, how intersample peaks form between samples, and why you need a true peak limiter will save you from repeated rejections. Your music will sound the way you intended on any platform.
What Is Peak vs True Peak in Audio Mastering
Peak (dBFS) Explained
A mix with a peak meter showing -6.2 dBFS means that number represents the loudest moment in that section. Every audio file consists of individual samples, and each sample has a level. Peak measurement shows the absolute loudest point of a signal, which is the highest level any single sample reaches.
Full scale, 0 dBFS, marks the absolute maximum level in the digital domain. Your signal clips when it hits 0 dBFS. Digital clipping produces harsh, unpleasant distortion. Analog distortion can sometimes add warmth or character, but digital clipping sounds broken.
Everything operates digitally inside your DAW. Your meters read the level of individual samples. Your meters show green and everything appears clean if no sample exceeds 0 dBFS. This measurement system works well to monitor individual digital samples, but it tells an incomplete story about what happens during playback.
What Is True Peak (dBTP)
True peak measurement predicts what the analog waveform will do between those samples. The difference matters because your music doesn’t stay digital forever. The signal passes through a digital-to-analog converter in your audio interface, someone’s headphone amp, a phone, or a car stereo at some point.
The converter reconstructs a continuous analog waveform from individual digital samples through a process called interpolation. The reconstructed waveform can peak higher than any individual sample in the digital file. The analog curve connecting two samples that are both below 0 dBFS can overshoot and exceed 0 dBFS.
These overshoots are inter-sample peaks, and they can cause distortion in the analog output even though the digital meters never showed clipping. A regular peak meter only reads the level of each individual digital sample, while a true peak meter predicts what the analog waveform will do between those samples.
True peak metering uses oversampling to calculate the inter-sample peaks and show you the real maximum level your signal will reach after conversion. It oversamples by a factor of 4x or higher. The result is measured in dBTP, which stands for decibels true peak. A file that reads -0.1 dBFS on a sample peak meter might read +0.3 dBTP on a true peak meter.
The Key Difference That Causes Rejections
The reconstruction filter applied during digital-to-analog conversion rounds off the stepped digital audio signal to provide a smooth listening experience. These filters can cause changes in the audio levels, which becomes problematic for signals close to 0 dBFS.
A high-end digital-to-analog converter has headroom to compensate for this issue, but cheap speakers and consumer devices won’t handle these inter-sample peaks. Your mix might not sound distorted in the studio, but your peaks can become clipped when played through budget playback systems.
Every major streaming platform has a true peak requirement for this reason. Spotify, Apple Music, YouTube, and Tidal all recommend keeping true peaks at or below -1 dBTP. Your master might pass your DAW meters but still cause audible distortion on the platforms where your listeners hear it if you only look at regular peak meters and ignore true peaks.
Why Spotify Rejects Your Master: Inter-Sample Peaks Explained
True Peak vs Peak Mastering: What Happens During AAC Encoding
Lossy encoding transforms your WAV file into a smaller AAC or MP3 by discarding audio information the encoder determines is perceptually irrelevant, then reconstructing the signal at playback using mathematical models. That reconstruction introduces its own inter-sample behavior. A file measuring +0.3 dBTP before encoding might jump to +1.0 dBTP or higher after the process completes.
The encoder didn’t add distortion on purpose. It lacked enough headroom to reconstruct the signal cleanly. Codecs apply filtering to reduce file size, and those filters produce level discrepancies between your original uncompressed file and the compressed version. The greater the compression, the easier distortion occurs.
How Intersample Peaks Form Between Samples
Your digital file passes through a reconstruction filter at playback that rounds off the stepped digital waveform and creates a smooth analog output. The interpolation process between consecutive samples generates small differences in eventual output levels. If two consecutive samples sit very close to 0 dBFS, the reconstructed curve arcing between them can exceed the digital ceiling and produce a brief burst of distortion in the analog output stage.
This phenomenon remains invisible to conventional sample peak meters. Standard meters measure individual sample values, but the reconstructed analog waveform operates continuously. The curve can spike higher than any single sample shows between those measured points.
Why 0 dBFS Isn’t Safe
A master delivered at 0 dBFS sample peak with inter-sample peaks at +0.5 dBTP will emerge from the AAC encoder with audible distortion. Not obvious clipping. Something subtler: a hardness, a brittleness on loud transients that wasn’t in your original file. Most listeners won’t identify it as distortion. They’ll just sense something feels off.
Because of this encoding behavior, Spotify requires -1 dBTP on quieter masters and -2 dBTP on louder ones. Apple Music asks for -1 dBTP. The platforms aren’t being precious about headroom. They’re accounting for what their encoders do to files.
High-end converters handle inter-sample peaks better, but cheap CD players, phone speakers, and budget earbuds lack the headroom. Your mix sounds clean in the studio but clips on consumer devices.
Real-Life Example: Before and After Encoding
Many commercial hits contain inter-sample peaks. Travis Scott and Drake’s “Sicko Mode” measures 2.4 dBTP. Dua Lipa’s “Levitating” hits 1.8 dBTP. Doja Cat’s “Say So” reaches 0.8 dBTP. These tracks passed through mastering engineers who either ignored true peak limits or accepted the distortion as part of the loudness race.
The issue varies between converter grades and playback electronics. An audiophile DAC accommodates the headroom, but cheaper systems clip audibly. Measurements from popular songs show true peaks ranging up to +3 dBTP during the loudness wars era.
Spotify’s True Peak Requirements and Platform Standards
Spotify’s -1 dBTP Requirement
Your master’s loudness level determines Spotify’s true peak requirement. The platform recommends -1 dBTP for tracks mastered at -14 LUFS or quieter. Masters pushed louder than -14 LUFS require -2 dBTP to account for the increased risk of encoder clipping.
The difference centers on how hard you’re hitting your limiter. Louder masters generate higher inter-sample peaks during the encoding process. Push harder into limiting and your true peak level rises. Spotify uses Ogg Vorbis and AAC encoding to reduce bandwidth. These compression methods can cause peaks to exceed zero if your original file was already close to 0 dBFS.
A balanced master around -14 LUFS with -1 dBTP proves safe across all platforms. More than 87% of Spotify users never change the default -14 LUFS normalization setting. This means your track will be turned down if mastered substantially louder anyway. Files that don’t adhere to the -1 dBTP ceiling may experience sound artifacts during the normalization process.
Apple Music and Other Streaming Platforms
Apple Music targets -16 LUFS with -1 dBTP true peak when Sound Check is enabled. YouTube operates at -14 LUFS but recommends -2 dBTP for extra safety against AAC encoding issues. Tidal uses -14 LUFS with -1 dBTP, while Amazon Music sits at -13 LUFS with -2 dBTP.
The variation in LUFS targets matters less than the consistent true peak requirements. Platforms adjust playback volume through normalization, but they can’t restore dynamics lost to over-compression. True peak limiting remains the absolute requirement for preventing encoding distortion beyond the loudness specification.
Some engineers use -1.5 dBTP for Apple Music as extra protection, though -1 dBTP is usually enough. Netflix mandates that true peaks must not exceed -1 dBTP for all content.
What Happens If You Exceed the Limit
Files exceeding true peak limits don’t get rejected automatically in most cases. The encoded version develops subtle distortion that wasn’t present in your original master. The conversion process adds gain, and the louder your master, the more gain the conversion produces.
The encoding adds artifacts that create a harsh, brittle quality on loud transients without proper true peak management. Listeners won’t identify it as clipping, but something feels off. Consumer devices like cheap earbuds and laptop speakers can’t handle peaks close to 0 dB well. The digital-to-analog conversion causes audible clipping.
Spotify’s normalization turns down tracks louder than -14 LUFS anyway. This eliminates any perceived loudness advantage while leaving the compression artifacts intact. You end up with a lifeless-sounding track at the same playback volume as a more dynamic master.
How to Use a True Peak Limiter Correctly
Setting Up Your True Peak Limiter
You need nothing more than a button on your limiter plugin to engage true peak mode. Nearly every modern limiter offers this feature. The first step is to set my output ceiling to -1.0 dBTP, which establishes the brick wall maximum level.
A single limiter doesn’t handle both loudness maximization and true peak control very well, so I use two instances on my master bus. The main limiter shapes dynamics and pushes perceived loudness while adding character. The second limiter catches any remaining inter-sample peaks that slip through. I set a low ratio with fast attack and release times for this secondary unit[173]. The goal is to shave off just enough volume and prevent clipping without affecting transients.
You can also use one limiter with true peak mode disabled and the ceiling around -1.0 dB, then add a second instance with true peak enabled and both threshold and ceiling linked higher than the first instance’s ceiling. A steep low-pass filter between 17 and 22 kHz before limiting can reduce true peak levels by approximately 1 dB and require less aggressive limiting.
Recommended True Peak Limiter Plugins
FabFilter Pro-L 2 delivers detailed loudness metering with support for EBU R128 and ITU-R BS.1770-4 standards. The visual feedback proves helpful during precise mastering work. It features eight limiting algorithms and support for Dolby Atmos 7.1.2. Hold Shift while adjusting gain and it compensates output volume to prevent the louder-is-better illusion.
Brainworx bx_limiter True Peak offers CLASSIC mode for controlled sound and MODERN mode for faster, louder limiting suited to harsh transients. The onboard high-pass and low-pass filters prevent extreme frequencies from triggering excessive gain reduction. The Foundation control acts like a tilt filter and shapes low-end before it hits the limiter.
iZotope Ozone Maximizer has both Maximizer and Vintage Limiter modules with true peak options. The Magnify Soft Clip section blends soft clipping to reduce load on the limiter, while Transient Emphasis maintains snap when pushing loudness.
True Peak Limiting vs Standard Peak Limiting
True peak limiting can soften transients and create a closed-down quality in the high frequencies. Some engineers avoid it on purpose and prefer to lower the output ceiling rather than accept the sonic compromise. The difference becomes most audible on material with aggressive transients or dense high-frequency content.
Standard peak limiting addresses sample-level peaks and leaves inter-sample peaks uncontrolled. True peak limiting uses oversampling to predict and prevent these between-sample overshoots.
When to Enable True Peak Mode in Your Session
Turn on true peak limiting from the beginning of your mastering session if you plan to use it. Work through it the entire time and you’ll hear its effect in context. This lets you make informed decisions about how much limiting to apply. Activate it after completing other processing and you may produce unexpected results that require adjustment of earlier decisions.
How to Fix and Prevent Spotify Upload Rejections
Measuring True Peak Before Export
Open a true peak meter plugin on your master channel before exporting your master. iZotope Insight provides accurate immediate monitoring during playback. I open the finished track in iZotope RX and check the Waveform Statistics window to get a faster-than-realtime overview. This method scans the entire file in seconds and doesn’t require playback.
Watch the maximum true peak value throughout the track. Adjust your limiter settings and recheck if it exceeds your target ceiling. The measurement should remain stable below your intended threshold in every section of the song.
Leaving Proper Headroom for Encoding
Set your limiter’s output ceiling to -1.0 dBTP as standard practice. This threshold prevents inter-sample peaks from causing encoder clipping and maintains competitive loudness. Masters pushed louder than -14 LUFS need -2.0 dBTP instead. True peak levels climb higher the harder you push into limiting.
You create a losing battle when you attempt to maintain extreme loudness while reducing only true peaks. Codec clipping can still occur even with controlled true peaks if the overall loudness remains excessive.
Checking Your Master After Rendering
Analyze your exported file using the same true peak meter after you render it. Export at your session’s native resolution without changing sampling rate or bit depth. The export process can introduce peaks that weren’t visible during playback.
Open the bounced file in your metering plugin and verify the maximum true peak value matches your pre-export readings. Any discrepancy indicates a problem in your export settings or limiter configuration.
What to Do If Your Track Already Got Rejected
Plugins like Wavelab, Ozone and Sonnox offer codec preview features that let you assess encoding results before upload. Use these tools to audition how your master sounds after AAC conversion. The preview reveals whether reducing true peaks alone solves the issue or if you need to lower overall loudness.
Reducing true peaks without addressing excessive limiting may produce problematic encodes. Backing off your limiter a bit provides cleaner results than aggressive true peak control on a crushed master in some cases.
Table of Contents
Conclusion
The difference between peak and true peak comes down to what happens during conversion and encoding. Regular peak meters show your digital samples, but true peak reveals what listeners hear after your track passes through converters and codecs.
I recommend setting your limiter to -1.0 dBTP as standard practice. Use -2.0 dBTP instead for louder masters above -14 LUFS. The extra headroom prevents encoding artifacts without sacrificing loudness.
You’ll avoid repeated rejections and maintain the sonic quality you intended. Your masters will translate cleanly across all playback systems, from high-end monitors to budget earbuds.
