πŸ”’ Your files stay on your device β€” core audio processing runs locally. Privacy details β†’
Multi-track release QC Β· local analysis Β· CSV/JSON report

Album Loudness Analyzer

Compare a whole release at once: gated loudness approximation, RMS, sample peak, crest factor, stereo correlation, album range and target flags β€” without changing or uploading any track.

Before-and-after illustration of Album Loudness Analyzer: Album track batch becomes Album QC report through Measure track loudness.
Before → process → afterSee the signal story, then hear it in the workspace.

MEASUREMENT MAP

Album Consistency Table

Turn a signal into evidence you can inspect. A useful analyzer connects the raw trace, the measurement window and a clearly labeled result without pretending that one number explains the whole recording.

Before-and-after illustration of Album Loudness Analyzer: Album track batch becomes Album QC report through Measure track loudness.
Album track batchMeasure track loudnessAlbum QC report
An analysis path: a bounded signal window produces comparable metrics and a visual trace while preserving the context needed to interpret them.
Open the full signal breakdownBest source, processing logic, limits and three-pass listening check
  1. Start with the right material

    Finding unexpectedly loud, quiet, clipped, flat or phase-risky tracks before an album, EP, podcast series or sample delivery is released.

  2. Understand the transformation

    Every selected file is decoded locally and scanned with the same bounded peak, RMS, gated loudness-estimate, crest-factor and stereo-correlation calculations before album aggregates and flags are resolved.

  3. Verify the usable result

    Sortable per-track metrics, album range and consistency flags plus CSV and JSON reports in the chosen track order; the source files are not modified.

Track outliers

Where this workflow stops

Browser measurements are digital release checks, not calibrated SPL readings or a substitute for platform certification and listening. The labelled loudness value is an approximation unless the implementation explicitly passes a full standard conformance test.

THREE-PASS CHECK

Make the final decision by ear

  • Use the same window and settings when comparing two files.
  • Treat estimates as evidence, not as a substitute for listening.
  • Export or note the measurement context alongside the result.
Per track
Duration, sample rate, channels, gated energy loudness approximation, RMS, sample peak, crest and stereo correlation.
Album QC
Duration-weighted album loudness approximation, loudness range, loudest peak, target flags and phase-risk count.
Report
Exact visible track order and album aggregates exported locally as CSV or structured JSON.

How to check album loudness online

  1. Load multiple mastered tracks or start with the three-track synthetic QC demo.
  2. Choose a comparison preset; it creates flags only and never changes audio.
  3. Analyze locally, then compare loudness approximation, RMS, peak, crest and stereo correlation across the tracklist.
  4. Sort or manually reorder the release and export the final visible rows plus album summary as CSV or JSON.

Analysis-only release QC

This dashboard measures many independent tracks together. It does not normalize, limit, resample, tag or export audio. That makes it distinct from Loudness Normalizer and the single-file Audio File Analyzer: the value here is cross-track consistency, order-aware album aggregates and a reusable QC report.

What β€œloudness approximation” means

The meter calculates 400 ms multi-channel energy blocks, removes blocks below an absolute βˆ’70 threshold, then applies a relative gate 10 dB below the first gated mean. The result uses the familiar βˆ’0.691 energy offset, but it is deliberately labeled an approximation because this implementation does not claim certified K-weighting, channel weighting or true-peak oversampling.

Limits worth knowing

Privacy: selected tracks are decoded and measured in this browser. They are not uploaded and no modified audio is created. Normal page assets may still be requested when the page loads.

Album Loudness Analyzer: quick answer and technical limits

Quick answer: A batch release-QC workspace that measures multiple tracks consistently and compares their duration, level, crest and stereo behavior as one ordered album or playlist.

Best for
Finding unexpectedly loud, quiet, clipped, flat or phase-risky tracks before an album, EP, podcast series or sample delivery is released.
How it works
Every selected file is decoded locally and scanned with the same bounded peak, RMS, gated loudness-estimate, crest-factor and stereo-correlation calculations before album aggregates and flags are resolved.
What you get
Sortable per-track metrics, album range and consistency flags plus CSV and JSON reports in the chosen track order; the source files are not modified.

Know before you use it: Browser measurements are digital release checks, not calibrated SPL readings or a substitute for platform certification and listening. The labelled loudness value is an approximation unless the implementation explicitly passes a full standard conformance test.

Privacy: Selected audio is processed in this browser and is not uploaded to AudioWrench. Normal page assets can still be requested as described in the privacy notice. Privacy details β†’

FAQ

Does this tool normalize or change my album tracks?
No. It is analysis-only release QC. The selected files are decoded and measured locally, but no normalized or modified audio is created or downloaded.
Is the integrated loudness value official LUFS?
No. It is explicitly labeled a gated energy loudness approximation. It uses 400 ms block energy, an absolute gate and a relative gate, but does not claim a certified BS.1770 meter or true-peak oversampling.
What does stereo correlation show?
It compares left and right sample movement from minus one to plus one. Near plus one means strongly similar or mono-compatible; near minus one means inverted opposition and is flagged as a likely phase risk.
Are the album tracks uploaded?
No. Audio payloads are decoded and measured on this device. Only normal page assets may be requested; the selected files and generated reports are not sent to AudioWrench.

Related analysis tools