Is your master competitive? Drop it in and see how its loudness, punch, width and tone compare with the benchmark.
Loudness per ITU-R BS.1770-4 / EBU R128 (K-weighting, gated), true peak by 4x oversampling. "Loudest 20%" = 3 s windows at or above the 80th percentile of short-term loudness. Spectrum bands are relative to total energy so they compare shape, not level. Hover a term for its definition.
Share of measurements inside the benchmark spread, weighted towards chorus loudness and density.
Sorted by severity. Every finding that has a fix states it.
Platforms normalise on the whole track, listeners compare choruses, so the report measures both. Choruses matching while the whole track is behind means the gap is arrangement, not mastering.
Every platform pulls both to its target. What is left is density and tone, not level. "Limited" means the platform would have to raise your track above its true-peak ceiling.
No. Decoding and measurement happen in your browser. The benchmark comparison sends only the measured numbers (a few kilobytes), never the audio, and the benchmark statistics themselves never leave the server.
WAV, AIFF, FLAC, MP3 and AAC/M4A, mono or stereo, at any sample rate. Use the lossless export you would send to a distributor: lossy encoding changes the true peak reading.
There is no single number. Spotify normalises to -14 LUFS, Apple Music to -16, YouTube and Amazon to -14, and all of them turn loud tracks down. Competitive releases are mastered well above those targets because density and tone survive normalisation and level does not. The benchmark shows where competitive releases actually sit, for the chorus and for the whole track.
Integrated loudness averages the whole track, intros and breakdowns included. Two tracks with the same integrated loudness can have choruses several dB apart. The loudest 20% (3 second windows at or above the 80th percentile of short-term loudness) isolates the sections a listener compares when your chorus follows someone else's in a playlist.
A set of commercially released, competitively mastered tracks measured with exactly the same analysis. Every metric is compared with the benchmark average and spread. "Matching" or "in range" means within one standard deviation of the average.
Lossy encoders overshoot the source peaks on decode, so -1 dBTP is the common recommendation and -0.3 dBTP is fine if you accept some overs. The report flags overs as a warning, not an error: many competitive masters have them and treat it as a trade-off for level.
Drop them one after the other. Each report replaces the previous one, so note the score, the gauges and the findings you care about before dropping the next file.