Audio Loudness Analyzer

Inspect decoded audio levels and gated K-weighted loudness estimates without uploading the source; results are diagnostic, not a certified broadcast measurement.

Audio file

—Integrated estimate

—Sample peak

—RMS

—Crest factor

Window	400 ms loudness estimate

Choose an audio fileThe integrated figure is a browser-local BS.1770-style K-weighted gated estimate. It is not a certified broadcast meter and does not perform true-peak oversampling.

Audio Loudness Analyzer: LUFS Targets & Gain Planning

Interpret browser-local loudness results against selectable LUFS targets with gain, peak-headroom and normalization planning evidence.

Target loudness

Peak ceiling

Source fidelity & reproducibility audit

Independently decode the selected local audio, fingerprint the source, inspect signal evidence, and rebuild the current processing plan from visible controls. This verifies browser-visible source and transformation math; it does not certify codec quality or mastering compliance.

Choose audio in the tool above, then refresh this source audit.

Browser-local source probe. Audio never needs to leave this page for this 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.

Measurement boundary stays explicit

The existing browser-local gated K-weighted estimate is preserved as an estimate, not relabeled as a certified loudness meter or true-peak analyzer.

Practical guide and verification

Use the interactive product above first. These notes add interpretation, verification and limits below the results and product controls.

Keep the meter boundary explicit

The browser workflow provides a BS.1770-style gated loudness estimate and sample-peak evidence, not a certified broadcast meter. Do not relabel the output as compliance proof or true peak when oversampled inter-sample peak measurement is not being performed.

Integrated loudness and short windows answer different questions

The integrated estimate summarizes the program after gating, while the 400 ms rows reveal local changes. A track can meet a long-term target and still contain very quiet or very loud sections that matter for editing.

Gain planning must respect peak headroom

If the loudness target suggests positive gain, compare that gain with the current peak before applying it. Reaching a target LUFS number by simple gain can push samples or inter-sample peaks beyond a safe ceiling.

Codec decoding can change what the browser sees

Compressed sources are decoded before analysis, and codec/browser support varies. Keep the original file, record the decoded sample rate and channels when relevant, and re-check a final rendered master rather than assuming the source analysis transfers perfectly.

Crest factor adds context to the loudness number

Two files can have similar integrated loudness but very different peak-to-RMS relationships. Use crest factor and peak evidence to distinguish a dense, compressed signal from one with more transient headroom.