Free audio health check
Is your track ready to release?
Drop a song and get an instant report card — loudness, true peak, clipping, dynamics and mono compatibility, scored 0–100, with a verdict for every streaming platform. Runs in your browser. Nothing uploaded.
What it checks, and why each matters
Integrated LUFS
How loud the track actually plays after streaming normalization. Master to the wrong target and your song is either turned down (lost dynamics) or plays quieter than everything around it.
True peak (dBTP)
Inter-sample peaks that clip during MP3/AAC encoding even when the waveform looks safe. The reason platforms recommend a -1 dBTP ceiling.
Clipping
Hard distortion baked into the file from pushing the gain too far — the single most common reason an AI track sounds harsh.
Dynamics (PLR)
Peak-to-loudness ratio. AI tracks arrive pre-compressed; this flags when there's no range left and more limiting would only distort.
Mono compatibility
Whether the track survives being summed to mono — phone speakers, club systems and smart speakers all do this, and out-of-phase content vanishes.
DC offset
A silent waveform shift that wastes headroom and can thump on playback. Removed with a high-pass at ~25 Hz.
How does the AI Mix Auditor measure loudness?
It computes integrated loudness with the ITU-R BS.1770-4 algorithm — the same K-weighting filter and gating that Spotify, Apple Music, and YouTube use to normalize playback — entirely in your browser. True peak is measured at 4x oversampling to catch inter-sample peaks.
What does the score mean?
A 0-100 release-readiness score weighted by how much each issue actually matters: true peak and clipping carry the most weight (they cause audible distortion), then loudness, mono compatibility, dynamics, and DC offset. 80+ is release-ready; below 55 needs work before you upload.
Is my file uploaded to a server?
No. The entire analysis runs in your browser using the Web Audio API. Your audio never leaves your device, and there is no account or email required.
What's the difference between true peak and sample peak?
Sample peak is the loudest single sample. True peak reconstructs the analog waveform between samples and catches inter-sample peaks that exceed it — these clip during lossy encoding (MP3, AAC) even when the sample peak looks safe. That's why platforms recommend a -1 dBTP ceiling, and why the auditor measures true peak, not just sample peak.
Can it fix the problems it finds?
The auditor only diagnoses. To fix the issues — true peak, loudness, clipping, stereo balance — run the free mastering tool, which corrects all of them automatically to the platform you choose.