Audio Clipping Detector

Find hard or near-clipping samples, first-event time, channel peaks, run counts, and exportable diagnostics locally.

Audio file

Clipping threshold (dBFS)

—Sample peak

—Samples over threshold

—First event

—Channels

Channel	Peak	Samples	Runs	First event

Choose an audio fileSample clipping detection flags decoded samples at or above your threshold. It cannot prove whether clipping happened earlier in an analog chain or detect inter-sample true peaks.

Audio Clipping Detector: Peak & Event Audit

Summarize threshold margin, per-channel peak spread, clipped runs and first-event evidence after the local sample scan completes.

Position quick-win audit

Audio processing cluster

Verify the source before trusting the render

Decode locally, confirm sample rate, channels, duration and level evidence, then apply the transformation. Keep codec, browser decode and export-format limits explicit.

Start: Audio Editor Inspect a File

All 24 audio tools

Sample RateResample rate, Nyquist and output frames Stereo → MonoDownmix, correlation and cancellation risk Speed ChangerDuration, pitch and resampling behavior Loop MakerLoop boundaries, seam and repeated duration Frequency AnalyzerFFT resolution and spectral evidence Bass BoosterLow-shelf gain and clipping headroom Audio JoinerClip order, transitions and output duration Loudness AnalyzerLUFS planning, peak and dynamics

Codec and measurement boundaries

Browser decoding differs across Safari, Chrome, Firefox, iOS, and Android. Rendered edits are exported as WAV unless a tool explicitly states another supported container. Loudness analysis is a practical BS.1770-style estimate rather than a certified meter, and sample clipping checks do not replace true-peak oversampling.

Threshold changes invalidate the report

A CSV generated at one threshold is no longer treated as current after the threshold changes; re-scan first. Sample clipping remains distinct from true-peak clipping.

Interpreting clipping evidence

Threshold choice changes what counts as clipping

A threshold near 0 dBFS finds only the hottest peaks, while a lower threshold flags more near-clipping samples. Keep the chosen threshold with the CSV/report so a later reviewer knows why an event was counted.

Sample peaks are not the same as inter-sample peaks

A decoded waveform can stay below 0 dBFS while reconstruction or lossy encoding creates higher inter-sample peaks. For mastering delivery, use a true-peak meter in the destination audio workflow in addition to this browser-local sample scan.

Inspect event clusters, not only the total count

A few isolated hot samples and a long flat-topped region can produce very different audible consequences. Use the first-event location and exported event data to inspect the waveform around each cluster before deciding whether gain reduction or repair is needed.