CoProducer Check a mix

Free checklist · Updated 4 November 2026

Pre-release master checklist

NoDAW Labs · Lacquer

Before you upload a master, measure the exported file and confirm five things: integrated LUFS inside −14 ± 1.5, true peak at or below −1.0 dBTP, zero clipped samples, a sample rate of at least 44.1 kHz, and phase correlation of at least 0.2. Then check the tails, the export settings and the metadata below.

Download the PDFOne tidy file you can keep next to the bounce folder.

The five measured gates

GatePassIf it fails
Integrated LUFS−14 ± 1.5Gain first, not another limiter
True peak≤ −1.0 dBTPTrue-peak limiter last, re-measure
Clipped samples0Back to the unclipped mix
Sample rate≥ 44.1 kHzRe-export at a legal rate
Phase correlation≥ 0.2Mix work, not mastering work

01Loudness

The store measures the whole file, not the chorus. Measure the exported file the way a store would, then decide.

Go deeper

02True peak

A WAV that never touches 0 dBFS can still clip after MP3 or AAC. True peak is the number that belongs on the release sheet.

Go deeper

03Mono and phase

Phones, clubs and smart speakers collapse stereo. A wide chorus that vanishes in mono is a delivery risk, not a creative choice.

Go deeper

04Tails, fades and edges

Most last-minute export disasters are at the first and last second of the file.

Go deeper

05Sample rate, bit depth and export

Boring, visible, non-negotiable. These are the settings a distributor checks before it ever hears the song.

Go deeper

06Metadata and ISRC basics

Metadata is how a recording gets paid and found. Fix it before upload, because changing it afterwards is slow.

Go deeper

07The final proof

The last ten minutes before you press send.

Go deeper

Sources: ITU-R BS.1770 (loudness and true-peak measurement); EBU R 128; Spotify for Artists, loudness normalization; AES TD1008; IFPI ISRC Handbook. Platform figures for Apple Music, YouTube, TIDAL, Amazon Music and Deezer are commonly reported values, not numbers those services publish, and services change them. Treat the lane as a safe default, not a law.

Spotted a number that has moved, or a step we missed? Write to NoDAW@nodawlabs.com. How we test, cite and correct.