Inter-Sample Peaks: The Clipping You Can’t See
Updated August 2026 · by Loopin
Inter-sample (true) peaks are the clipping you can’t see on a normal meter — they happen between samples when the DAC reconstructs the waveform, so the analog peak overshoots past 0 dBFS even when every sample reads under it. The fix is to meter in true peak (dBTP) and limit to a −1 dBTP ceiling. You can cap them safely, free, in Loopin’s browser mastering.
What are inter-sample peaks?
Digital audio stores a series of samples, but playback doesn’t play those dots one at a time. The DAC (digital-to-analog converter) reconstructs a smooth, continuous waveform that passes through them — and that reconstructed wave can rise higher between two samples than either sample reads.
That overshoot is the inter-sample peak, also called the true peak. It’s the real level your speaker or headphone actually tries to produce, and it can exceed 0 dBFS even when the sample values never do.
This matters most on dense, limited masters, where fast transients and heavy limiting create waveforms that swing hard between samples. The louder and more squashed the master, the more often those reconstructed peaks poke over the line — which is exactly why loudness and true-peak safety are linked.
- Sample: a single stored value in the file
- Inter-sample peak: the reconstructed wave’s high point between samples
- True peak (dBTP): the metering unit that captures that overshoot
- The overshoot is invisible to a plain sample-peak meter
Why they cause clipping you can’t see
Here’s the trap: a normal (sample) peak meter measures the level of each digital sample. It can read a clean −0.1 dBFS and tell you nothing is wrong.
But when the DAC rebuilds the analog waveform, the peak between samples can go over 0 dBFS. At that point the signal clips — distortion you never saw on the meter because the meter was only looking at the sample values, not the wave that plays back.
- Sample-peak reads under 0 — looks safe
- Reconstructed wave overshoots 0 dBFS — actually clips
- The distortion appears on playback, not in the file’s sample values
- This is why ‘it measured fine but sounds crunchy’ happens
Lossy codecs make it worse
Streaming and delivery almost never use the raw WAV — the file gets encoded to a lossy codec like MP3, AAC, or Opus. That encoding process shifts the waveform slightly, and it can push borderline inter-sample peaks even further over the edge.
So a master sitting right at 0 dBFS can be clean as a WAV and then distort once it’s converted for a listener’s device. Leaving true-peak headroom is what protects you from that conversion.
You have no control over which codec a platform uses or at what bitrate, so you can’t tune the master to a specific encoder. The safe approach is to assume the worst and build in margin — a −1 dBTP ceiling gives the encoder room to move without pushing your peaks into audible distortion.
- MP3, AAC, Opus: lossy encoding can add overshoot
- A master at 0 dBFS has no room for the encoder to move
- Peaks that were borderline in the WAV go over after encoding
- Headroom below 0 dBFS is your safety margin
Meter and limit in true peak (dBTP)
The reliable cure is to stop trusting sample-peak readings for your final ceiling and use a true-peak meter and limiter instead. A true-peak limiter models the reconstructed waveform and holds that below your ceiling. Use these targets:
- Standard ceiling: −1 dBTP (safe for most streaming platforms)
- Amazon Music: −2 dBTP (stricter peak requirement)
- Loudness: reach about −14 LUFS without slamming the limiter
- Judge by dBTP, never by a plain sample-peak meter
Cap inter-sample peaks step by step
Here’s the fastest path from an invisible-clipping master to a clean, safe one:
- Go back to the mix and bounce to WAV at full quality with real headroom — peaks around −6 dB, no mix-bus limiter.
- Open Loopin’s free mastering tool and drop the file in.
- Let the true-peak limiter hold inter-sample peaks under a −1 dBTP ceiling while loudness targets about −14 LUFS.
- A/B against your original — confirm the peaks are controlled without the track sounding crushed.
- Check the true peak reads −1 dBTP, then download the 16-bit WAV.
- For Amazon Music, aim for a −2 dBTP ceiling instead.
Common mistakes
- Trusting a sample-peak meter for the final ceiling — it can’t see inter-sample overshoot.
- Setting the ceiling at 0 dBFS — leave −1 dBTP (or −2 for Amazon) for reconstruction and lossy encoding.
- Ignoring the codec — a WAV that’s clean can still clip after MP3/AAC/Opus conversion.
- Slamming the limiter past −14 LUFS — that drives peaks straight to the edge.
- Mastering from a pre-clipped MP3 — the overshoot distortion is already baked in; start from a clean WAV.
How Loopin handles true peaks
Mastering acts on the whole finished stereo file, so the last thing it should do is control the true-peak ceiling. Loopin’s chain ends in a true-peak limiter set to −1 dBTP, so inter-sample peaks are caught before they ever reach a codec.
That means you don’t need a separate true-peak plugin or a special meter — drop the mix into Loopin’s mastering tool, let it target about −14 LUFS, and the −1 dBTP ceiling protects you through lossy encoding.
Fix it free
Loopin’s online mastering ends in a true-peak limiter that holds inter-sample peaks at a −1 dBTP ceiling while targeting about −14 LUFS — all in your browser, free, no signup, nothing uploaded, no watermark. Drop in your mix, A/B it, and download a clean 16-bit WAV that won’t clip after encoding.
Frequently asked questions
What are inter-sample peaks?
They’re peaks that occur between samples when the DAC reconstructs the waveform on playback. The reconstructed analog wave can rise higher than any stored sample and exceed 0 dBFS, which causes clipping even when a normal peak meter reads under 0.
Why can’t I see inter-sample clipping on my meter?
A normal (sample) peak meter only measures stored sample values. The overshoot happens in the reconstructed wave between samples, so a sample-peak meter can read a safe −0.1 dBFS while the true peak is actually over 0. You need a true-peak (dBTP) meter.
How do I fix inter-sample peaks?
Use true-peak (dBTP) metering and a true-peak limiter set to a −1 dBTP ceiling (−2 dBTP for Amazon Music). That holds the reconstructed peak below the edge and leaves headroom for lossy encoding.
Do lossy codecs make inter-sample peaks worse?
Yes. Encoding to MP3, AAC, or Opus shifts the waveform and can push borderline inter-sample peaks over 0 dBFS. That’s why you leave true-peak headroom — a WAV that’s clean can still clip after conversion.
Can I cap true peaks for free?
Yes. Loopin’s free browser mastering ends in a true-peak limiter at a −1 dBTP ceiling, runs entirely in your browser with nothing uploaded, and exports a clean 16-bit WAV.