DIY Mastering Checklist: 12 Steps Before You Upload
Before you upload a DIY master, stop changing tone and run a fixed quality-control pass: confirm the final mix is the right version, trim starts and endings, check fades, verify no clipping or true-peak surprises, compare loudness without chasing one magic LUFS number, listen on several systems, preview codec damage, confirm file format, check metadata, archive the source, and reopen the final WAV in a second app before you send it anywhere.
The last stage of mastering is not creative. It is proof work. Most DIY release mistakes are not because the artist lacked a $10,000 analog chain. They happen because the final file had a clipped chorus, a click at the start, a wrong sample rate, a missing clean version, a rough bounce uploaded by accident, or a master that sounded fine in the DAW but fell apart after codec conversion. A checklist keeps the release from depending on memory.
If the release needs to translate everywhere and you do not want the final QC pass on your shoulders, get the master checked before upload.
Book Mastering ServicesUse This Checklist After the Master Is Done
This is important: the checklist is not a replacement for mastering. It is the pass you run after the tonal decisions are finished. If the vocal is too sharp, the 808 is too soft, or the hook needs more width, go back to the mastering chain and fix the master. Do not use the final upload pass to keep making random EQ, limiter, or loudness changes.
A good DIY workflow has two separate modes:
- Mastering mode: tone, loudness, dynamics, spacing, EQ, compression, limiting, and emotional impact.
- Upload QA mode: file correctness, clipping, starts and ends, metadata, translation, codec preview, naming, and archive safety.
Mixing those modes is how people end up with five files named "final," "final louder," "real final," and "upload this one." Pick the approved master first. Then run the same 12 checks every time.
The 12-Step DIY Mastering Checklist
| Step | Check | Pass condition |
|---|---|---|
| 1 | Version lock | The file is the approved final mix or master, not a rough bounce |
| 2 | Head and tail | No accidental silence, cutoff, click, or missing reverb tail |
| 3 | Fades | Start and ending are clean with no hard sample edge |
| 4 | Clipping | No sample clipping or audible limiter crunch |
| 5 | True peak | Ceiling leaves enough headroom for codec conversion |
| 6 | Loudness | Level fits the genre and reference without destroying dynamics |
| 7 | Reference A/B | Tonality, vocal level, low end, and width survive level-matched comparison |
| 8 | Playback systems | Monitors, headphones, earbuds, phone, or car reveal no release-stopping issue |
| 9 | Codec preview | AAC/MP3/streaming-style preview does not add obvious distortion |
| 10 | File format | WAV, correct sample rate, correct bit depth, dither only when needed |
| 11 | Metadata and naming | Artist, title, version, clean/explicit status, and file name are unambiguous |
| 12 | Archive and reopen | Source, final master, notes, and delivery files are saved and the final WAV opens elsewhere |
Step 1: Lock the Correct Version
Start by proving you are checking the right file. This sounds too simple, but it prevents more release problems than any limiter setting. Open the master folder and find the file that was actually approved. Confirm the title, artist, version, mix date, clean/explicit status, and whether it is the main master, instrumental, performance track, TV mix, or alternate version.
If there are multiple finals, stop and clean the folder. Move old references to an archive folder. Keep one active upload candidate. If you need multiple delivery versions, name them deliberately. For example:
ArtistName_SongTitle_Master_24bit_48k.wav
ArtistName_SongTitle_Clean_Master_24bit_48k.wav
ArtistName_SongTitle_Instrumental_Master_24bit_48k.wav
Do not upload from a folder full of guesses. The best-sounding master does not matter if the wrong version gets delivered.
Step 2: Check the Head and Tail
Open the file in an audio editor and zoom into the beginning. You are checking three things: there is no accidental silence before the song, the first transient is not chopped, and the file does not begin on a non-zero sample that clicks. Some songs need a breath or pickup before bar 1, so do not trim by rule. Trim by musical intent.
Then check the ending. Let the whole tail play. Reverb, delay, final 808 decay, vinyl noise, crowd texture, or a long synth release should end naturally. If the tail cuts suddenly, go back to the session and extend the render. If there is several seconds of dead silence that is not intentional, trim it. A clean ending feels deliberate; an accidental ending feels unfinished.
Step 3: Add or Confirm Fades
Fades do not need to be dramatic. A very short fade-in can prevent a click at the first sample. A short fade-out can smooth the last few samples after the musical tail ends. If the song has an arranged fade, that is a creative fade and belongs in mastering mode. The upload QA fade is just there to prevent clicks and hard edges.
Do not use automatic silence removal on the final master unless you inspect the result. It can cut quiet intros, reverb tails, or intentional room tone. Manual fades are safer because you see and hear exactly what changed.
Step 4: Check for Clipping Before You Look at Loudness
Open a meter that can show sample peak and true peak. First, check sample clipping. If the waveform has flat tops or the meter shows overs, the master is not ready. Do not assume the distributor will fix it. Do not normalize it down and call it solved. If clipping happened inside the limiter or during export, go back to the mastering session and fix the cause.
Then listen to the loudest hook. Clipping is not always visible as a simple red light. A vocal can spit on loud words, a hi-hat can smear, an 808 can buzz, or the full chorus can feel like it is folding inward. If the master sounds loud but smaller than the mix, the limiter may be working too hard. The mastering limiter settings guide explains how to separate loudness from limiter damage.
Step 5: Verify True Peak Headroom
True peak matters because encoded playback can create intersample peaks higher than the sample peak meter shows. That does not mean one ceiling works for every genre, but it does mean a master with no true-peak headroom is risky for streaming-style conversion.
A conservative ceiling around -1 dBTP is a common starting point for streaming masters, and louder masters often need more caution. If you are pushing a very loud hip-hop, EDM, drill, or pop master, check codec preview carefully. If AAC or MP3 preview adds gritty distortion that was not in the WAV, lower the ceiling or reduce limiter drive in the source session and render again.
Do not fix true peak by lowering the already-rendered file if the master itself is damaged. Lowering a clipped file just gives you quieter clipping. Go back to the limiter stage.
Step 6: Check Loudness Without Chasing a Magic Number
Streaming platforms use loudness normalization in different ways, and listener settings can change playback behavior. Spotify's normal playback target is commonly discussed around -14 LUFS, but that does not mean every master should be forced to -14 LUFS. A quiet acoustic song, a loud trap record, an aggressive rock song, and an ambient intro all need different dynamics.
Use loudness meters as feedback, not as the only target. Check integrated LUFS for the full song, short-term LUFS for the loudest hook, and loudness range if the song needs contrast. Then compare against genre references at matched loudness. If your master is louder but smaller, it is losing. If it is quieter but feels bigger and translates better, that may be the right choice.
For DIY mastering, the real question is: does the master feel competitive after level matching without audible distortion or crushed movement? If yes, stop chasing numbers.
Step 7: Do a Level-Matched Reference A/B
Load two or three reference tracks that fit the actual song. A moody R&B vocal master should not be compared only to an aggressive EDM master. A melodic rap record should not copy the low-end balance of a rock mix. Pick references with similar vocal density, low-end weight, and arrangement style.
Turn the references down to match your master. This step matters because louder almost always feels better for a few seconds. Once levels are matched, compare these areas:
- Vocal level: is the lead too buried, too sharp, or sitting naturally?
- Low end: does the kick/808 translate without swallowing the vocal?
- Midrange: does the master feel cloudy, hollow, or balanced?
- Top end: is the air clean, or do hats and sibilance feel brittle?
- Width: does the master stay wide without losing center focus?
If one area is wrong, return to mastering mode. Do not keep running upload checks while you are unhappy with the tone.
Step 8: Listen on Several Playback Systems
You do not need a perfect room to run useful translation checks. You need contrast. Use your best headphones or monitors, then check consumer earbuds, phone speaker, laptop speaker, car, or a small Bluetooth speaker. Listen to the whole song at least once on a small system. Then jump to the loudest hook and quietest section.
On full-range monitoring, focus on low end, stereo image, and depth. On earbuds, focus on harshness, vocal level, and distortion. On phone speakers, focus on whether the lead vocal and main rhythm still make sense without deep bass. In the car, listen for low-end buildup and vocal masking. If the master only works in one place, it is not ready.
Keep notes. "Too bright on AirPods" is more useful than "bad." "808 covers vocal on car chorus" tells you where to work. The checklist should point you back to the source of the issue.
Step 9: Preview Codec Damage
Streaming services and social platforms do not play your WAV directly to every listener. They encode it. Codec preview lets you hear whether AAC, MP3, or similar compressed playback creates obvious damage. Apple provides tools such as AURoundTripAAC for checking AAC encode behavior, and many mastering tools include codec preview options.
Listen for:
- vocal sibilance turning grainy
- hi-hats getting splashy or metallic
- distorted 808 harmonics getting rougher
- stereo effects collapsing strangely
- chorus impact shrinking after encode preview
If codec preview sounds worse than the WAV in a normal way, that is expected. If it reveals distortion, clipped peaks, or harshness that feels release-stopping, return to the master and fix it before upload.
Step 10: Confirm File Format, Sample Rate, and Dither
Most DIY artists should keep the final master as a WAV file, not MP3. Confirm the sample rate and bit depth match the delivery need. If you need to convert sample rate, do it once from the final source. If you need to reduce bit depth from 24-bit to 16-bit for a specific delivery, use dither once at that final reduction. Do not dither a 24-bit file and do not dither several versions in a row.
If this part is confusing, separate it from the rest of the checklist. The sample rate converter guide walks through when to convert, how to preserve bit depth, and why repeated conversion can damage files.
Also confirm the clean/explicit version format. If you need both versions, export both intentionally from the source session or approved master process. Do not create the clean version by destructively editing the final explicit WAV unless that is the only approved workflow.
Step 11: Check Metadata and Naming
Metadata needs depend on the distributor and release path, but the basics should be correct before upload: artist name, song title, version type, featured artists, clean or explicit status, release notes, composer/producer credits, and ISRC if one has already been assigned. Many distributors can generate ISRC codes, but you still need to keep the correct code tied to the correct recording once it exists.
File naming should remove ambiguity. A good file name does not need spaces, special characters, or emotional labels. It should make the version obvious:
ArtistName_SongTitle_Master_24bit_48k.wav
ArtistName_SongTitle_Clean_Master_24bit_48k.wav
ArtistName_SongTitle_Instrumental_Master_24bit_48k.wav
Do not use "final_final" names. If you need revisions, use v1, v2, v3, and keep a short notes file explaining what changed.
Step 12: Archive and Reopen the Final File
Before upload, create a release archive folder. Include the final master WAV, alternate versions, source mix, mastering session if available, reference notes, export settings, and any screenshots or text notes that explain the chain. You may need a clean version, radio edit, instrumental, TV track, or remix stem later. Future you should not have to rebuild the release from memory.
Then reopen the final WAV in a second app. Use another DAW, an audio editor, or a reliable media preview. Confirm it plays from start to finish, shows the expected length, and does not throw an error. This catches corrupted exports, incomplete bounces, and weird file-header problems before the distributor does.
After the file opens cleanly somewhere else, upload that exact file. Do not rename it again, drag a different version by accident, or make one more loudness tweak. The checklist is complete only when the same file you verified is the one you deliver.
When DIY Mastering Is Not the Best Move
DIY mastering can work for demos, low-stakes singles, rough releases, and artists who are building skill. It becomes riskier when the song is part of a paid rollout, playlist push, sync pitch, album campaign, or ad spend. If the mix is close but you are unsure whether the master is too loud, too dull, too sharp, or too small after conversion, hiring help can be cheaper than re-releasing a broken file.
A mastering service is useful when you need a second monitoring chain, a reliable final limiter stage, format decisions, codec checks, and someone who is not emotionally attached to the mix. That outside judgment is often the difference between "loud enough in my room" and "translates across normal listening situations." If the song matters commercially, Book Mastering Services before the deadline is one of the safest moves.
Extra Checks for Singles, EPs, and Albums
A single only has to work against itself and a few references. An EP or album has to work as a sequence. If you are uploading more than one song, run the 12-step checklist on each track, then do one sequence pass across the full release. Put the songs in the final order and listen to the last 20 seconds of one song into the first 20 seconds of the next. You are checking whether level, brightness, bass weight, and spacing feel intentional.
Do not force every song to the same LUFS number just because they share a project. A quiet intro, a hard single, an interlude, and a stripped vocal track should not all feel equally dense. Instead, match perceived energy. The listener should not reach for the volume knob unless the arrangement intentionally changes intensity.
Also confirm version consistency. If track one is 24-bit / 48 kHz and track two is 16-bit / 44.1 kHz, there may be a good reason, but it should not be accidental. If one file has two seconds of head silence and the next starts immediately, decide whether that spacing is musical. If clean versions exist for some songs but not others, label them clearly and keep them in separate folders so the wrong file does not land in the distributor upload.
Clean, Explicit, Instrumental, and Performance Versions
Many artists remember the main master and forget the alternate versions until the night before release. That is where mistakes happen. A clean edit may click where a word was muted. An instrumental may be louder because the vocal bus is gone. A performance track may need the hook left in and verses removed. A TV mix may need lead vocals removed but backgrounds kept. Treat each version as its own master candidate, not just an export preset.
Run the key checks again on each version: start, tail, clipping, true peak, codec preview, format, naming, and reopen test. The alternate version does not need a full creative remaster if it came from the approved master session, but it does need proof that it is not broken. When labels, DJs, sync contacts, or collaborators ask for alternate files, they expect those files to behave like finished masters.
A clean folder structure helps:
- 01_Main_Master: explicit or primary release version.
- 02_Clean_Master: clean edits with clicks checked.
- 03_Instrumental: instrumental master with level rechecked.
- 04_Performance_or_TV: special versions for live, sync, or promo use.
- 05_Archive: source mix, mastering session, notes, references, and old revisions.
That organization is not cosmetic. It prevents upload errors when the release window is tight.
FAQ
Should my master be exactly -14 LUFS?
No. Loudness normalization does not mean every song should be mastered to one number. Use LUFS as a reference, compare against genre tracks at matched volume, and prioritize clean translation, dynamics, and impact over hitting a single target.
What true peak ceiling should I use before upload?
A ceiling around -1 dBTP is a common conservative starting point for streaming masters. Very loud masters may need more caution, especially if codec preview adds distortion. If true peak issues appear, fix the limiter stage and render again from the source.
Do I need to upload WAV or MP3?
Use WAV unless your distributor gives different instructions. MP3 is a lossy format and should not be the source for a release master. If you need MP3 for sharing, create it as a separate reference copy, not the main upload file.
Should I dither every master?
No. Dither only when reducing bit depth, such as from 24-bit to 16-bit. Do not dither 24-bit masters, and do not dither repeatedly across several export versions.
How many speakers should I check before upload?
Use at least three different playback situations if you can: your main monitoring, earbuds or headphones, and a small speaker such as a phone, laptop, or car. You are listening for translation problems, not trying to make the song sound identical everywhere.
What should I do if the checklist catches a problem?
Go back to the source session or mastering chain, fix the cause, export a new master, and run the checklist again. Do not patch the already-exported WAV unless the issue is only naming or organization. Audio problems should be fixed upstream.





