Pre-Mastering Checklist: What to Check Before Sending Your Mix

Pre-Mastering Checklist: What to Check Before Sending Your Mix

Before sending your mix for mastering, confirm the mix is approved, remove loudness-only limiters, leave clean peak headroom, export a full-resolution WAV or AIFF at the session's native sample rate, include the correct final version, and write clear notes about references, fades, alternate versions, and any intentional mix-bus processing.

Pre-mastering is not mastering. It is the final quality-control pass that makes sure the mix you hand off is actually ready to be mastered. The mastering engineer should be making the final record louder, clearer, more consistent, and more translatable. They should not be guessing which bounce is final, repairing clipped vocals, undoing a limiter you forgot about, or trying to infer whether the noisy intro was intentional.

Use This Checklist After the Mix Is Actually Approved

The most important pre-mastering question is not technical. It is whether the mix is done. If you are still unsure about the lead vocal level, hook automation, kick and bass balance, intro length, or ending fade, solve that before mastering. Mastering can polish the approved mix, but it should not become the place where you keep changing the production.

A clean handoff starts with a clear decision: this is the final mix. If you need one last car check or headphone pass, do it before export. If the artist, producer, or client still has arrangement notes, finish those first. A mastering engineer can work faster and make better decisions when the mix has a single approved direction.

Think of pre-mastering as the bridge between creative mixing and final delivery. You are checking the mix file, not trying to make it louder. The more confident the handoff, the fewer revisions you need later.

Checklist 1: Confirm the Final Mix Version

Version confusion wastes more time than almost any plugin setting. Before export, make sure everyone knows which session and bounce are final. If you have files named "final," "final 2," "final fixed," and "real final," stop and clean that up before sending anything.

• Use one approved session: open the mix session that actually contains the final automation and edits.
• Mute unused print tracks: make sure rough vocals, old beat bounces, and test masters are not playing.
• Check the full song from start to finish: listen through the intro, hook, bridge, outro, and fade.
• Write the final version name clearly: include artist, song title, mix version, sample rate, and date if helpful.
• Export one main mix: alternate versions are useful, but the main approved mix must be obvious.

The file name should not require a phone call. A mastering folder with "Artist - Song Title - Final Mix - 24bit 48k.wav" is much easier to trust than "bounce 8.wav."

Checklist 2: Remove Loudness-Only Processing

If you put a limiter on the master bus just to make the mix louder for playback, remove it before sending the pre-master. Loudness limiting belongs in mastering unless that limiter is part of the mix sound and the mastering engineer specifically needs to hear it. A limiter that was only there for volume takes away transient information and can make the mastering stage less flexible.

Do not remove every mix-bus processor automatically. A gentle bus compressor, tape color, EQ curve, or saturation stage may be part of the mix. The key is intent. If the processor is making the record sound like the approved mix, document it. If it is only making the bounce louder, bypass it.

Master-bus processor	Usually keep?	Pre-mastering decision
Limiter or maximizer for loudness	No	Bypass unless requested as a reference only
Clipper shaving drum peaks	Maybe	Keep only if it is essential to the mix tone and not overdriven
Gentle mix-bus compression	Maybe	Keep if the mix was balanced into it and it defines the feel
Subtle tone EQ	Maybe	Keep if it is part of the approved mix, note it in the handoff
Stereo widener on the whole mix	Be careful	Check mono compatibility and remove if it causes phase problems
Metering plugin	Yes	It does not affect sound if it is truly meter-only

If you are unsure, export two files: one clean pre-master without the loudness limiter and one reference bounce with your loud demo chain. Label them clearly. The reference helps communicate the energy you liked, while the clean pre-master gives mastering room to work.

Checklist 3: Leave Clean Headroom

Headroom is the space between the mix's loudest peak and digital full scale. The main rule is simple: do not clip. You do not have to hit a magic number exactly, but a mix that slams 0 dBFS or shows red peak indicators is not a clean handoff. Many mastering engineers recommend leaving a few dB of peak room because it prevents accidental clipping and gives processing space.

Do not create headroom by putting a limiter on the mix. Lower the mix level or master fader if needed, then check the loudest section again. If individual tracks or buses are clipping before the master output, fix those too. A clean master fader cannot repair distortion printed earlier in the chain.

Use this practical test:

1. Find the loudest hook, drop, or final chorus.
2. Play it with the loudness limiter bypassed.
3. Watch the true peak or sample peak meter on the master output.
4. Confirm there is no clipping anywhere in the signal path.
5. If peaks are too hot, lower the mix cleanly and recheck.

Heavy low end can hide headroom problems because the mix may sound controlled while the meter is jumping. If your track has big 808s, use the heavy 808 mixing guide to solve kick and bass conflicts before you send the file for mastering.

Checklist 4: Export the Right File Format

Send a full-resolution WAV or AIFF file, not an MP3. MP3 is a lossy format, and lossy compression removes information that cannot be fully restored. It may be fine for quick listening, but it is not the ideal source for mastering.

Use the session's native sample rate unless your mastering engineer asks for something else. If the session was produced at 48 kHz, export at 48 kHz. If it was produced at 44.1 kHz, export at 44.1 kHz. Unnecessary sample-rate conversion adds another technical step and can create avoidable problems if done poorly.

For bit depth, 24-bit or 32-bit float WAV is usually safer than 16-bit for a pre-master. The goal is to preserve detail and headroom through the handoff. Dither is normally a mastering-stage decision when reducing bit depth for a final delivery format, so do not add dither to a 24-bit pre-master unless specifically instructed.

Export setting	Good pre-master choice	Why it matters
File type	WAV or AIFF	Preserves full audio quality
Bit depth	24-bit or 32-bit float	Keeps detail and avoids unnecessary truncation
Sample rate	Native session rate	Avoids unnecessary conversion
Normalization	Off	Do not force the peak to 0 dBFS
Dither	Usually off for pre-master	Leave final bit-depth reduction for mastering
MP3 export	No	Lossy compression is not the best source file

If you need a deeper export explanation, the sample-rate converter guide explains when conversion is useful and when it is better to leave the file at its original rate.

Checklist 5: Export the Full Song With Heads and Tails

Do not trim the file so tightly that the first transient starts at the first sample or the reverb tail cuts off early. Leave a little clean space before the song starts and enough tail after the final sound. This gives mastering room for fades, noise checks, and clean spacing.

Listen to the very beginning and very end after export. Many pre-master problems live there: a clipped first kick, a missing pickup breath, a cut reverb tail, a click after the fade, or a count-in that should have been muted. These small issues become obvious once the final master is louder.

If the song needs a specific fade, send notes. If you want the mastering engineer to shape the fade, leave the full ending and explain what you want. Do not guess by cutting the tail too early.

Checklist 6: Check Clipping Beyond the Master Fader

The master output is not the only place clipping can happen. A vocal bus, drum bus, 808 channel, effects return, or printed stem can clip before it reaches the final meter. If distortion is printed into the mix, mastering will reveal it instead of hiding it.

Check these areas before export:

• Vocal bus: loud hooks, ad-libs, stacked backgrounds, and delay throws.
• Drum bus: snare hits, kick peaks, clippers, and parallel compression returns.
• Low-end bus: 808 glides, bass notes, sub drops, and kick overlaps.
• Effects returns: reverb hits, delay feedback, and throws at transitions.
• Printed samples: loops that were already clipped before they entered the session.

If you hear crackles, clicks, harsh distortion, or sudden level jumps, fix them in the mix. Do not assume the mastering stage will remove them without tradeoffs.

Checklist 7: Make a Reference Bounce

A reference bounce is not the same as the pre-master. It is a separate file that shows the loudness, tone, or energy you have been listening to while approving the mix. If you used a limiter for rough playback, bounce that version and label it "reference only."

Send reference songs too, but choose them carefully. One or two strong references are better than six unrelated tracks. Pick songs that match the direction you want: vocal level, low-end weight, brightness, stereo width, or overall density. Do not expect mastering to turn a dark, quiet mix into a completely different production. References guide the final polish; they do not replace the mix.

A useful note sounds like this: "Use the reference for low-end weight and vocal brightness, but keep our outro fade natural." A vague note like "make it industry" does not help much.

Checklist 8: Include Alternate Versions Only When Needed

Alternate mixes can help, but too many files create confusion. Send alternates when there is a clear reason: vocal up, vocal down, clean version, instrumental, performance track, acapella, or TV mix. Label each file so the engineer does not have to open everything to understand it.

Common useful alternates include:

• Main mix: the approved version for mastering.
• Vocal up: lead vocal slightly louder if the artist is unsure.
• Vocal down: lead vocal slightly lower for backup comparison.
• Clean version: edited lyrics if needed for release or sync.
• Instrumental: final beat mix without the lead vocal.
• Acapella: vocal-only export if requested.

Do not send five unlabeled mix versions hoping the mastering engineer chooses the best one. That is still a mix decision. Make the decision first or ask for a mix review before mastering.

Checklist 9: Write Clear Handoff Notes

Good notes reduce revisions. Include the song title, artist name, desired output, references, intentional distortions, fade requests, alternate versions, and any known concerns. If the vocal is intentionally distorted, say so. If the intro noise is part of the beat, say so. If the snare is supposed to be dry and forward, say so.

Do not write a novel, but do not send an empty folder either. A few clear notes can prevent the mastering engineer from "fixing" something you wanted.

Note type	Useful example	Why it helps
Reference	"Use Track A for low-end size, Track B for vocal brightness."	Separates different goals
Intentional distortion	"808 grit is intentional; avoid smoothing it too much."	Protects creative tone
Fade	"Fade starts after the last vocal delay, around the final chord."	Avoids cut-off endings
Concern	"Check chorus sibilance and low-end translation."	Focuses the quality-control pass

Checklist 10: Do a Final Bounce Listen

After exporting, listen to the actual file you are sending, not just the DAW session. This is the step that catches wrong export ranges, muted effects, missing automation, clicks, cut tails, distorted bounces, and bad file names.

Listen at a normal level from beginning to end. Then jump to the loudest hook, the quietest intro, the bridge, and the outro. Check the file in a player outside the DAW if possible. If the exported file is wrong, fix the session and bounce again. Do not send the wrong file with an explanation unless there is no other choice.

If you are also handling your own final master, use the DIY mastering checklist after this handoff checklist. This page is about preparing the mix before mastering begins; the DIY checklist is about the final master before upload.

Red Flags That Mean the Mix Is Not Ready

• The artist still wants the vocal level changed.
• The master bus clips when the limiter is bypassed.
• The low end only works because a limiter is holding it down.
• The file is an MP3 or a converted bounce from an unknown source.
• The intro, ending, or fade has not been approved.
• The mix changes dramatically between headphones and speakers.
• You cannot tell which version is final from the file name.
• You are hoping mastering will fix arrangement or performance problems.

If any of those are true, pause the handoff. Fixing the mix now is faster than paying for mastering, hearing the same problem louder, and then returning to the mix anyway.

Simple Pre-Mastering Folder Structure

Keep the folder boring and obvious. A clean folder might look like this:

• Artist - Song Title - Final Mix - 24bit 48k.wav
• Artist - Song Title - Loud Reference Only.wav
• Artist - Song Title - Vocal Up - 24bit 48k.wav
• Artist - Song Title - Instrumental - 24bit 48k.wav
• Notes.txt
• Artwork or metadata files if requested

The folder should answer the basic questions before anyone presses play: what is final, what is reference, what is alternate, and what should the mastering engineer pay attention to?

Check the Mix Like Someone Else Will Hear It

One useful pre-mastering habit is to pretend you are receiving the file from another artist. You are not defending the mix anymore. You are inspecting it. That mindset makes it easier to hear problems you ignored while building the song.

Start with the loudest chorus. Then check the first ten seconds, the first vocal entrance, the biggest transition, the bridge or breakdown, and the ending. Those moments reveal most handoff problems. If the first vocal line is too quiet, mastering will not know whether the vocal should come up or whether the contrast is intentional. If the final chorus distorts, mastering will make that distortion more obvious. If the ending cuts off, the final master will feel amateur even if the middle sounds good.

Write down problems by category instead of randomly tweaking. Use categories like vocal level, low end, clipping, arrangement, export, notes, and versioning. If you find three mix problems, go back to the mix. If you find only export or labeling problems, fix the handoff and keep the approved mix intact.

When to Send Stems Instead of a Stereo Mix

Most mastering starts from a stereo mix, but sometimes stems are useful. Stem mastering can help when the vocal is slightly uncertain, the low end needs separate control, or the instrumental and vocal need different treatment. It is not a substitute for an unfinished mix. It is a controlled way to give the mastering engineer a little more flexibility.

If you send stems, keep them simple. Do not export twenty random groups unless requested. A practical stem set might be instrumental, lead vocal, background vocals, and effects. For some songs, drums, music, bass, and vocals make more sense. Every stem should start at the exact same point, use the same sample rate and bit depth, and sum back to the approved mix when imported together.

Label stems clearly. If the mastering engineer has to guess whether "vox print 3" is the lead, the stack, or the effects return, the handoff is not ready. Also send the approved stereo mix as the reference so the stems can be checked against the real mix.

What Not to Fix in Pre-Mastering

Pre-mastering is a quality-control pass, not a panic remix. Do not start changing every plugin because the song is about to leave your hands. If the mix was approved, preserve the creative choices and only fix real problems. Last-minute random changes often create new issues that nobody has time to approve.

Do not normalize the file. Do not add a limiter because the export sounds quieter than commercial songs. Do not convert sample rates just because a tutorial said higher numbers are better. Do not remove mix-bus tone processing that the whole balance depends on unless you have checked the mix without it. The goal is a clean, honest pre-master, not a louder rough master.

If you are nervous because the pre-master sounds quieter than released records, that is normal. Released records have been mastered. Compare tone, balance, and emotional impact at matched listening volume instead of chasing final loudness before the mastering stage.

FAQ

Should I remove all plugins from the master bus before mastering?

No. Remove loudness-only limiters and processors that were added just to make the bounce louder. Keep mix-bus processing that is part of the approved sound, but document it so the mastering engineer understands the intent.

How much headroom should I leave before sending a mix to mastering?

There is no single magic number, but the mix should not clip. Leaving a few dB of clean peak headroom is a practical target because it prevents accidental distortion and gives mastering room to work.

Can I send an MP3 for mastering?

Send a WAV or AIFF whenever possible. MP3 is a lossy listening format and is not the best source for mastering because audio information has already been removed during encoding.

Should I export at 44.1 kHz or 48 kHz?

Export at the native sample rate of the session unless your mastering engineer requests something different. Avoid unnecessary sample-rate conversion during the pre-mastering handoff.

Do I need to send a loud reference bounce?

A loud reference bounce can help if you have been approving the song through a rough limiter. Label it clearly as reference only, and send the clean pre-master separately for the actual mastering work.

What should I include in mastering notes?

Include the final version name, reference tracks, fade requests, alternate versions, intentional distortion or noise, and any concerns about vocal brightness, low end, or translation. Clear notes prevent avoidable revisions.