Mastering Prep Checklist for First-Time Clients

Mastering Prep Checklist Tool: What First-Time Clients Should Confirm

Before you send a song for mastering, confirm that the mix is final, the stereo bounce is clean, there is no clipping, loudness processing is not printed just to make the mix louder, the file format is high quality, the reference tracks explain your target sound, and the release format is clear. Mastering can polish, translate, sequence, and prepare a finished mix, but it cannot reliably fix an unfinished mix or restore dynamics that were already crushed.

First-time mastering clients often worry about the wrong things. They ask for the perfect LUFS number before they have checked whether the mix is clipping. They export three different "final" versions without explaining which one is approved. They send an MP3 because it sounds fine in the car. They leave a limiter on the master bus because the rough mix felt more exciting that way.

A good mastering handoff is not complicated. It is a clean final mix, a clear goal, and enough context for the engineer to make the right decisions. This checklist gives you the practical version: what to confirm before you upload the file, what notes to send, and when mastering is the wrong next step because the mix still needs attention.

If your mix is approved and you need a finished master for release, send the clean bounce, references, and release notes with the order.

Book Mastering Services

The Short Checklist Before You Send a Master

If you only check one section, use this one. These are the items that prevent most first-time mastering delays:

Final mix approved: no expected vocal swaps, beat changes, lyric edits, or arrangement changes.
Clean stereo bounce: one full-length WAV, AIFF, or FLAC export from the beginning to the final decay.
No clipping: the stereo mix should not hit or exceed 0 dBFS, and individual mix problems should not be hidden by the master fader.
No loudness-only limiter: remove limiters or maximizers that were added only to make the rough mix louder.
Reference tracks: one or two commercial songs with short notes about what you like.
Release use: streaming, Bandcamp, video, sync, club/DJ version, CD, or another format.
Notes: anything intentional that should not be "fixed," such as distortion, dark tone, lo-fi texture, or aggressive vocal tuning.

That is enough for many singles. More complex releases need more detail, but a clean version of this checklist gives the mastering engineer a solid starting point.

Mastering Is Not a Replacement for Mixing

Mastering works on the final stereo mix, not the individual lead vocal, snare, kick, ad-libs, synths, and background layers. That means mastering can shape the overall tone, loudness, punch, stereo image, spacing between songs, and delivery readiness, but it has limited control over problems inside the mix.

If the vocal is too quiet, mastering may bring it forward slightly by changing the overall tonal balance, but it cannot raise only the vocal the way a mix session can. If the hi-hat is painfully loud, mastering can soften the top end, but that may also darken the vocal and cymbals. If the low end is muddy because the kick and bass are fighting, mastering can help, but the best fix may be in the mix.

Use this decision table before sending the file:

Problem You Hear	Send to Mastering?	Better First Step
The whole mix is a little quiet compared with releases.	Yes.	Mastering can address final loudness.
The lead vocal is buried under the beat.	Not yet.	Fix the vocal balance in the mix.
The mix clips or distorts on the loudest chorus.	Not yet.	Remove clipping and rebalance before mastering.
The song needs final polish, translation, and release level.	Yes.	Send a clean bounce with references.
You still plan to replace the verse vocal tomorrow.	No.	Finish the mix decision first.

If the mix itself is not finished, mixing services are the cleaner next step. Mastering should be the final quality-control and release-prep stage, not the first time the record becomes balanced.

Confirm the Mix Is Actually Final

"Final mix" means the creative decisions are locked. The lead vocal take is approved. The tuning is approved. The beat or production is final. The arrangement is not changing. The fade is intentional. The effects that define the song are printed or clearly explained. The version you send is the version you want mastered.

This matters because every replacement mix usually needs a new mastering pass. If the engineer masters version 3 and you later send version 4 with a louder vocal, that is not a small note. It is a new source file. The previous master may not translate because the balance, tone, and peak behavior changed.

Before sending the file, play the bounce from start to finish outside your DAW. Use a normal media player, headphones, speakers, or the system you usually use to catch mistakes. Listen for:

missing intro or chopped first transient
cut-off reverb or delay tail at the end
wrong vocal version
muted ad-libs or accidental guide tracks
clicks, pops, or edit glitches
unexpected distortion on choruses
wrong song title or file name

Do not assume the export is right because the session sounded right. The bounce is what the mastering engineer receives. Check the bounce itself.

Export a High-Quality Stereo File

For mastering, send a high-quality stereo file. WAV and AIFF are common. FLAC is also lossless and can be useful when file size matters. Some distributors accept compressed formats too, but that does not mean a compressed file is the best source for mastering.

Keep the export at the same sample rate as the session unless the engineer asks for something specific. If the song was made at 48 kHz, export 48 kHz. If it was made at 44.1 kHz, export 44.1 kHz. Do not upsample only because a higher number looks more professional. Upsampling does not create detail that was never recorded.

For bit depth, 24-bit is a safe common handoff, and 32-bit float may be useful if your workflow and engineer support it. The key is to avoid sending a low-quality MP3 as the source for mastering. An MP3 is already lossy. Mastering a lossy file can exaggerate artifacts and gives the engineer less to work with.

Use clear file names:

Weak File Name	Better File Name	Why It Helps
final_final.wav	ArtistName_SongTitle_MixForMaster.wav	Shows the file is the mix source, not the mastered result.
song.mp3	ArtistName_SongTitle_48k24bit.wav	Identifies the quality and avoids lossy source confusion.
masterthisnew.wav	ArtistName_SongTitle_CleanMix_NoLimiter.wav	Tells the engineer the loudness limiter was removed.
bounce2.wav	ArtistName_SongTitle_ApprovedMix_2026-08-19.wav	Makes version control easier.

Simple names prevent the wrong file from being mastered. That matters more than clever naming.

Leave Real Headroom and Dynamics

Headroom means the mix has space below the digital ceiling. Dynamics mean the music still has movement between quieter and louder moments. Mastering needs both. If the stereo mix is already clipped, limited, and flattened for loudness, the mastering engineer has less room to add polish without creating distortion.

A common safe handoff is a mix that peaks several dB below 0 dBFS and does not clip. Some services recommend aiming around 6 dB of peak headroom because it is generous and easy to check. The exact number matters less than the principle: do not hit the ceiling, and do not use a limiter only to make the rough mix sound loud.

If you like the sound of your mix-bus compressor because it shapes the groove, tell the engineer and send it if it is part of the mix. If you added a limiter only because the reference was louder, remove it for the mastering version and include the limited rough as a reference. That gives the engineer the intent without locking them into the damage.

Do not create fake headroom by turning down an already clipped file. If the waveform clipped before export, lowering the master fader afterward does not restore the lost peaks. Go back into the mix, fix the gain staging or processing that caused the clipping, and export a clean version.

Handle Loudness Targets Carefully

Loudness is where first-time clients get conflicting advice. Streaming platforms use loudness normalization in different ways, and playback behavior can vary by device, user settings, and format. Spotify's artist documentation explains that it uses loudness normalization during playback and measures loudness during upload, but does not process or change the delivered audio before playback. It also lists -14 LUFS as a normal playback reference and gives true-peak guidance for avoiding distortion.

That does not mean every song should blindly be mastered to one number. A sparse acoustic song, an aggressive rap single, a club record, and a dense rock track may need different loudness decisions. The master should fit the song, the genre, and the release use. Chasing loudness without context can make the record smaller, harsher, or less emotional.

Give the engineer a target use instead of only a number:

Streaming single: balanced loudness, clean translation, and true-peak safety.
Club or DJ version: more competitive level and punch for loud systems.
Video or sync use: controlled dynamics and clean dialogue/music compatibility if needed.
EP or album: consistent tone and level across multiple songs.
Alternate master: a separate version if the release needs a different context.

If you are unsure, say that. A good mastering engineer can recommend the right direction when they know the genre, references, and release plan. "Make it loud but not harsh for streaming" is more useful than choosing a number from a random forum and treating it as law.

Choose References That Explain Taste

Reference tracks are not instructions to copy someone else's master. They are taste anchors. They help the engineer understand how bright, loud, wide, warm, clean, aggressive, or dynamic you expect the release to feel.

Send one or two references in the same general lane as your song. Then write one sentence for each reference. The sentence is important because the engineer does not know what you like about the song unless you say it.

Useful reference notes sound like this:

"Use this for vocal brightness and overall polish."
"Use this for low-end weight, but keep my song less harsh."
"Use this for loudness and punch, not for stereo width."
"Use this for how smooth the top end feels on headphones."
"Use this for album-level consistency across the project."

Avoid sending five unrelated references. If one is dark, one is bright, one is a club master, and one is an acoustic ballad, the target becomes unclear. Two well-explained references beat a long playlist with no notes.

Explain the Release Format

A mastering engineer needs to know where the song is going. A streaming release, DJ promo, video upload, CD, sync pitch, and physical format can have different priorities. Even when the source mix is the same, the deliverables may be different.

For most independent artists, the normal request is a high-quality mastered WAV for distribution plus a listening copy if needed. If you are uploading through a distributor, check its accepted file formats. DistroKid, for example, lists WAV, MP3, M4A, FLAC, AIFF, and WMA among uploadable formats, but a lossless source such as WAV, AIFF, or FLAC is still the better mastering handoff.

If the song is still being recorded or arranged, recording templates can keep session files cleaner before the mix stage. If the vocal tone is still inconsistent, fix that with the recording and mix chain first; vocal presets belong before mastering, not as a last-minute mastering request.

If you need alternate files, say so before the project starts:

clean version
instrumental master
performance track
TV track
club or DJ master
album sequence
video edit

Alternate versions may require separate exports from the mix session before mastering. For example, an instrumental master needs the instrumental mix, not only the final vocal mix. A clean version may require edited vocals. Do not wait until after mastering to ask for deliverables that need different source files.

Send the Loud Rough Mix as a Reference, Not the Source

Many artists have two versions by the time they are ready for mastering: a clean mix export and a loud rough bounce. The loud rough might have a limiter, clipper, or maximizer on the master bus because it helped the song feel closer to a release while you were sharing demos. That rough can be useful, but it should usually be a reference, not the mastering source.

The clean mix gives the mastering engineer room to work. The loud rough explains what you liked about the energy. Send both if the rough communicates something important. Label them clearly so nobody masters the wrong file:

Mix for mastering: clean export, no loudness-only limiter, no clipping.
Loud rough reference: your listening bounce with the rough limiter left on.
Note: one sentence explaining what the rough gets right, such as energy, brightness, or low-end weight.

This is especially helpful when you love the punch of the rough but know the limiter is working too hard. The engineer can aim for the same feeling with better control. Without that note, they may assume the clean mix is the whole target and miss the aggressive direction you were hearing in the rough.

Do not send only the loud rough and expect mastering to undo it. Once clipping, pumping, and harsh limiting are printed into the source, the master has to work around those artifacts. Sometimes the result can still be improved. It just has less ceiling than a clean mix with the rough included for taste.

Prep Multiple Songs as One Release, Not Separate Singles

If you are sending an EP or album, mastering prep includes sequence context. A group of songs should feel like one release, even when each song has its own energy. Send all approved mixes together when possible, along with the intended order. The mastering engineer can then judge tonal balance, loudness, spacing, and emotional arc across the project.

For multi-song releases, include:

the final track order
song titles exactly as they should appear
any intended transitions or gaps
which song should feel loudest or most aggressive, if any
whether singles were already released and need to be matched
any alternate clean, instrumental, or performance versions

Do not master five songs in isolation and then hope they sit together later. One song may be naturally darker, another may have more low end, and another may need to feel smaller so the next chorus lands harder. Album-level mastering is partly about those relationships. If the release is only one song, the checklist is simple. If it is a project, the checklist should describe the whole project.

Write a Short Mastering Brief

A mastering brief should be short and specific. The engineer does not need a full story about how the song was written. They need the approved mix, the target, the references, and any warnings.

Use this structure:

Song: artist name, title, and version.
Release use: streaming single, EP, album, video, DJ promo, or another format.
Goal: clean modern master, warmer tone, aggressive loudness, smoother top end, or better translation.
References: one or two songs with one-line notes.
Intentional choices: distortion, dark vocal, heavy low end, lo-fi texture, or unusual stereo effects.
Concern areas: harsh chorus, boomy low end, sibilance, quiet bridge, or mix translation issue.
Deliverables: mastered WAV plus any alternate versions.

Keep the brief honest. If you are worried the vocal is too low, say that before mastering. The engineer may tell you to revise the mix first, which is better than paying for a master that cannot solve the real problem.

Know When Stem Mastering Might Help

Standard mastering uses a stereo mix. Stem mastering uses grouped stems, such as drums, bass, music, lead vocal, and backgrounds. It gives the engineer more control, but it is not always necessary. More control also means more prep work and more chances to send files incorrectly.

Stem mastering may help when:

the overall mix is close but one group needs small control
the vocal level is slightly uncertain but the full mix session is not available
the low end needs treatment without affecting the whole track
the project needs polish but not a full remix

It is not a shortcut for a messy session. If the stems are poorly balanced, clipped, misaligned, or missing effects, stem mastering becomes a repair job. For a first-time client, a clean stereo master is usually simpler unless the engineer specifically asks for stems.

Final Pre-Send Audit

Before uploading the file, run this audit:

Play the bounce outside the DAW. Confirm the file is not corrupted and the full song plays.
Check the start and end. No chopped transients, missing count-in if needed, or cut-off final tail.
Confirm no clipping. The stereo mix should stay below the digital ceiling.
Remove loudness-only limiting. Keep creative mix-bus tone only if it is part of the approved mix.
Use a lossless file. Send WAV, AIFF, or FLAC unless the engineer requests something else.
Name the file clearly. Artist, song title, version, and "mix for mastering" are enough.
Attach references and notes. Do not make the engineer guess the target.
Confirm deliverables. Mastered WAV, streaming version, clean version, or other files should be agreed upfront.

If all eight are clear, you are ready to send the song to mastering services. If several are unclear, pause and fix the handoff first. Clean prep is faster than revisions caused by missing context.

FAQ

How much headroom should I leave before mastering?

Leave enough peak headroom that the mix is not clipping or hitting the digital ceiling. A common safe target is peaks around several dB below 0 dBFS, often around -6 dBFS, but the exact number matters less than sending a clean, unclipped, dynamic mix. Do not lower a clipped file and call it fixed.

Should I remove the limiter before sending a mix for mastering?

Remove any limiter or maximizer that was added only to make the rough mix louder. If a bus compressor, saturation plugin, or limiter is part of the creative tone, tell the engineer and consider sending both the printed version and a cleaner version. The key is not to destroy dynamics before mastering begins.

What file format should I send for mastering?

Send a lossless stereo file such as WAV, AIFF, or FLAC unless the engineer asks for another format. A 24-bit WAV at the original session sample rate is a common safe handoff. Avoid sending MP3 as the mastering source because it is already compressed and gives the engineer less quality to work with.

Should I master to -14 LUFS for streaming?

Spotify lists -14 LUFS as a normal playback reference for its loudness normalization, but that does not make one number the right creative target for every song. Tell the engineer the release context, genre, and references. The master should fit the record while staying clean enough to translate across platforms.

Do I need separate masters for streaming, club, and video?

Sometimes. A normal streaming single often needs one strong master. A club or DJ version may need a more aggressive level and different low-end priorities. Video, sync, or clean versions may need separate deliverables. Tell the engineer all release uses before mastering starts.

Can mastering fix a bad mix?

Mastering can improve a finished mix, but it cannot reliably fix every internal balance problem. If the vocal is buried, the kick and bass are fighting, the chorus clips, or the wrong take is printed, fix the mix first. Mastering works best when the source mix is already approved and emotionally correct.