Check true peaks and clipping before final delivery

Measure the actual export

Record the file, meter and relevant settings, measured sample peaks, true peaks and loudness where available. ITU-R BS.1770 defines measurement algorithms for programme loudness and true-peak level. Use a tool that reports what you intend to assess, not an unrelated peak display.

Listen to the suspected passage

Note the exact time and audible problem, such as an unwanted crackle or harsh transient. Compare against the approved source where available. A numerical warning and an audible defect are different observations; neither should be dismissed without checking. Avoid claiming that every high reading proves an identical problem.

Use destination guidance in context

Spotify publishes mastering recommendations alongside normalisation information. Confirm the current route and intended listening context rather than treating one value as a guaranteed way to sound louder everywhere. Do not reduce or limit the artist’s master automatically without authority to make a new version.

Approve any change explicitly

Send the engineer a focused measurement and listening note, then review the replacement export against the same passage. Keep the old version, new version and approval. Recheck the complete master if processing changes. This guide does not certify submitted files, repair clipping or promise a universal loudness advantage.

Sources and review

Reviewed 4 November 2026. Platform requirements and plan terms can change. Examples are planning aids, not a promise of account access, release acceptance or earnings.

• ITU-R BS.1770 measurement
• Spotify mastering and normalisation guidance

Continue your release planning

• WAV or FLAC for distribution: choose a lossless master
• Approve a mastering revision with a clear version record

Ask the DistroBolt team about your release. Send a concise question and release reference; never send account passwords or verification codes.