How to Prepare Your Mix for Mastering (Checklist for Clean, Release-Ready Files)

You finished the mix. It sounds great in your studio. Now what? The gap between a finished mix and a release-ready master is where most self-produced engineers lose points — not because the mix is bad, but because the files they hand off are sloppy. Clipping on the export, a limiter left on the master bus, phase issues that only show up on a phone speaker, DC offset eating into your headroom. None of these are catastrophic, but each one forces the mastering engineer to work around your mess instead of focusing on your music.

This is written by YECK, founder of MixingGPT. I have been on both sides of this exchange — sending mixes to mastering engineers and receiving mixes from clients. The checklist below is the exact prep routine I run before exporting anything. It pairs with our guide on mixing for streaming LUFS and true peak and the broader mixing and mastering loudness guide. If you are also using AI tools to prep, check our best AI mastering plugins roundup.

The Pre-Mastering Checklist at a Glance

Full explanations for each item are below.

1. Mix Bus Headroom: Leave Room to Work

Your mix bus peaks should sit between -6 dB and -3 dB. That is not a suggestion born of superstition — it is the working range where a mastering engineer can apply EQ boosts, harmonic saturation, and compression without immediately running into the ceiling. If your peaks are at -0.3 dB, the engineer has to attenuate before doing anything, which adds an unnecessary step and can introduce rounding errors in fixed-point processing.

The simplest fix: pull your master fader or VCA down. This trims the overall output without changing the internal mix balance or the relationship between individual channels and their processors. If you start adjusting individual channel gains instead, every threshold-dependent plugin — compressors, gates, sidechain triggers — reacts differently and the mix shifts. A single global trim preserves all of those relationships. Do not strap a limiter on the bus to "tame" peaks — that is the mastering engineer's job, and a limiter on your export destroys transients irreversibly. For a deeper dive on managing levels throughout your signal chain, see our ultimate guide to gain staging.

2. Master Bus Processing: Bypass or Document

The golden rule: no limiter on the export. Beyond that, it gets nuanced. Some mixes genuinely rely on bus compression or tape saturation as part of their tonal identity — a multiband processor holding the tonal curve steady, a glue compressor on the stereo bus, tape emulation adding harmonic richness. In professional workflows, engineers who use a multiband "glue" chain on the mix bus keep the multiband and warmth stages engaged when sending to mastering but remove the limiter. The limiter is the only stage that is always removed; the rest is a judgment call. If removing a plugin changes the character of your mix in a way you are not happy with, leave it on. But document it.

Write down every plugin on your master chain, in order, with their settings. Include this in your delivery notes. The mastering engineer needs to know what is already shaping the stereo bus so they do not double up. If you have an EQ boost at 10 kHz and the engineer also boosts 10 kHz, you end up with harshness. If you want to understand what a professional mix bus chain looks like, read our breakdown of the inside a professional mix bus chain.

What to remove vs. what can stay

• Always remove: Limiters (Ozone Maximizer, Pro-L 2, L2 — anything catching peaks). These are mastering tools, not mix tools.
• Always remove: Final loudness EQ or "mastering EQ" that you added to make your rough master sound louder.
• Can stay (document it): Glue compression (2:1 ratio, slow attack, auto release) that is part of the mix's feel.
• Can stay (document it): Tape or console saturation that adds harmonic character.
• Can stay (document it): Subtle broad EQ shaping (e.g., a high-shelf at 12 kHz, +1 dB) that is part of the tonal balance.

3. Export Settings: Bit Depth, Sample Rate, and Format

Export settings determine the quality ceiling of the entire mastering process.

Bit depth: 24-bit or 32-bit float

24-bit is the industry standard for delivery to mastering. It gives you 144 dB of dynamic range — more than enough for any music. 32-bit float is also acceptable and is technically superior: it can represent values above 0 dBFS without clipping, which means inter-sample peaks during export are not destructive. In a 32-bit float file, a clip indicator on the master bus does not mean the audio is clipped — it means the signal exceeded 0 dBFS in the fixed-point display, but the floating-point data is intact and can be attenuated later without loss. Some mastering engineers prefer 32-bit float for exactly this reason. If your DAW offers 32-bit float export, use it. If not, 24-bit is perfectly fine.

Never export at 16-bit. That is CD quality and the final delivery format, not a working format. The extra bits in 24 or 32-bit give the mastering engineer headroom for processing without quantization noise.

Sample rate: match your session

If you tracked and mixed at 48 kHz, export at 48 kHz. If you worked at 44.1 kHz, export at 44.1 kHz. Do not upsample. Sample rate conversion is a lossy process — it interpolates new samples between existing ones, and every conversion introduces subtle artifacts. The mastering engineer will handle any sample rate conversion needed for the final delivery format (e.g., 44.1 kHz for streaming, 96 kHz for hi-res).

Format and normalization

• Format: WAV (Broadcast Wave Format / BWF is even better — it includes timestamp metadata). Never send MP3, AAC, M4A, or any lossy format.
• Normalization: Off. Always. Normalization changes the level of your file based on its peak, which means the mastering engineer receives a file that does not match what you approved in your studio.
• Dithering: If exporting at 24-bit from a 32-bit float session, apply dither (TPDF is fine). If exporting at 32-bit float, no dither needed. If your DAW handles this automatically (most modern ones do), do not add a separate dither plugin.
• Channels: Interleaved stereo. Not split L/R, not multi-mono. One stereo WAV file per song.

4. Session Cleanup: Silence, Fades, and Crossfades

Before you hit export, trim silence at the beginning and end, add fades to prevent clicks, and crossfade any edits that produce audible discontinuities.

Trim the silence

Your exported file should start just before the first audible sound and end just after the last reverb tail or cymbal ring fades to silence. A 10-second block of digital black at the start of your file is not just sloppy — it can confuse automated mastering tools and adds unnecessary file size. Leave 100-200 ms of silence before the first transient and 500 ms to 1 second after the final decay. That is enough for the mastering engineer to work with fades and spacing.

Fades and crossfades

Every edit point in your session — a comped vocal take, a punched-in guitar, a copied chorus — is a potential click. Apply short crossfades (5-15 ms) at every edit boundary. Check the start and end of the exported file for clicks: add a 5 ms fade-in at the very beginning and a 10-20 ms fade-out at the very end. These are inaudible but prevent the DC transient that some playback systems produce when a file starts or stops abruptly.

If you are dealing with a lot of edits and artifacts, tools like audio repair plugins can automate the cleanup. iZotope RX 12 has a dedicated De-click module that catches what manual editing misses.

5. Clicks, Pops, and DC Offset

DC offset happens when your waveform is not centered around zero — the entire signal is shifted up or down by a small number of sample values. You cannot hear it, but it reduces your available headroom and can cause clicks at the start and end of playback. Most DAWs have an offline "Remove DC Offset" function. Run it on every track that has recorded audio, then check the master bus.

Clicks and pops come from three main sources: edit boundaries without crossfades (covered above), plugin automation glitches, and buffer underruns during recording. The first two are fixable in the box. The third requires re-recording the affected section. To find them, solo each stem and listen with headphones at moderate volume — clicks that are inaudible on monitors are often obvious on headphones.

6. Phase Issues and Mono Compatibility

Your mix might sound incredible in stereo and fall apart in mono. This is not a theoretical concern — phone speakers, most Bluetooth speakers, club sound systems, and many car audio setups sum to mono or near-mono. If your low end disappears or your lead vocal gets buried when the stereo field collapses, you have phase cancellation. Fix it before mastering, because mastering cannot undo phase problems.

How to check

• Mono button: Most monitor controllers and DAWs have a mono summing button. Hit it. If anything disappears or gets quieter, you have a phase issue.
• Phase correlation meter: Insert one on your master bus. It should read between 0 and +1 most of the time. If it dips into negative territory, you have out-of-phase content that will cancel in mono.
• Goniometer / vectorscope: This shows your stereo width visually. A narrow vertical line is mono. A wide shape is stereo. If the shape inverts (goes past horizontal), you have severe phase issues.

Common culprits: stereo widener plugins on vocals or bass, multi-mic drum recordings with timing misalignment, and polarity issues between close mics and overheads. If you used a stereo widener on your bass, bypass it and check mono. If your kick drum disappears in mono, check the polarity alignment of your kick mic against the overheads — a polarity flip on one mic is the most common cause of low-end cancellation in drum recordings. These are the same fundamentals covered in our guide on common mix engineer mistakes to avoid.

7. Low-End Management

Low-end is the most common reason mixes come back from mastering with notes. Too much sub-bass eats headroom, triggers the mastering limiter prematurely, and makes the master sound quieter on streaming platforms. Not enough low-end and the master sounds thin and lifeless.

Before exporting, check your low-end on a system that reproduces sub frequencies accurately. Studio monitors with a subwoofer, or good closed-back headphones (like the Sony MDR-7506 or AKG K371). Listen for:

• Sub-bass rumble: Anything below 30 Hz that is not musical content. High-pass your master bus at 20-30 Hz, or high-pass individual tracks that do not need sub content.
• Kick and bass relationship: Are they fighting for the same space? The kick should own the punch (60-80 Hz), the bass should own the fundamental (80-120 Hz). If they overlap, use sidechain compression or EQ to carve space.
• Bass mono: Low frequencies should be mono. If your bass is stereo, sum it to mono below 120 Hz using a crossover or mid-side EQ.

For a complete approach to bass frequency management, see our guide on how to mix bass in 2026.

8. Check on Multiple Systems

Your monitors are one reference point. The goal of checking other systems is not perfection on each — it is catching problems your monitors mask.

The system rotation

• Studio monitors (primary): Your reference. This is where you make decisions. If your monitors are well-treated and you know their quirks, trust them for balance and frequency decisions.
• Closed-back headphones: Reveal low-end problems and reverb tails that monitors blur. Listen for mud in the 200-400 Hz range and harshness at 3-5 kHz.
• Earbuds (AirPods or equivalent): The reality of how most people will hear your track. If the vocal is too quiet on earbuds, it is too quiet. Period.
• Phone speaker: The ultimate mono compatibility test. If the hook is recognizable and the vocal is intelligible, you are in good shape. If it sounds like a muddy mess, go back and fix the low-mid buildup. If you hear audible peaking or distortion on the phone speaker, treat it as a genuine peak in the signal — small speakers expose level problems that larger monitors can mask.
• Car: The emotional test. Does the track make you nod your head? Does the chorus hit? Car speakers exaggerate low-end and upper mids, which reveals both excitement and problems.

Do not adjust your mix based on one system alone. If something sounds wrong on earbuds but fine everywhere else, note it — it might be an earbud-specific EQ curve. If something sounds wrong on three out of four systems, fix it in the mix.

9. Loudness Check Before Sending

Measure your mix's integrated loudness in LUFS before you send it. You are not mastering — you are just gathering information. The mastering engineer needs to know where the mix sits so they can plan their gain staging. If your mix is at -14 LUFS and the target is -9 LUFS, that is a 5 dB push — manageable. If your mix is already at -7 LUFS, the engineer knows they have almost no room to work with and will likely ask you to remove master bus processing.

Use Youlean Loudness Meter, Waves WLM Plus, or your DAW's built-in LUFS meter. Note the integrated LUFS, the true peak, and the loudness range (LRA). Include these numbers in your delivery notes. For context on what these numbers mean and how streaming platforms use them, read our streaming LUFS and true peak guide.

10. File Naming Conventions

Name your files clearly and consistently. The mastering engineer should be able to identify the artist, song, version, and format from the filename alone without opening it. Avoid spaces (use underscores), avoid special characters, and always include a version identifier.

Recommended format

ArtistName_SongTitle_MIX_24bit_48k.wav

Examples:

• YECK_MidnightDrive_MIX_v2_24bit_48k.wav
• YECK_MidnightDrive_INSTRUMENTAL_MIX_24bit_48k.wav
• YECK_MidnightDrive_CLEAN_MIX_24bit_48k.wav

The version number matters. If you send a revision, increment it. "v2" tells the engineer this is not the first version. "FINAL" is a trap — there is always a "FINAL_2." Use numbers.

11. What to Include With Your Files

A mastering engineer who knows what you want can deliver a better master in less time. Include the following with every delivery:

• BPM: Helps the engineer understand the energy and pacing. Also useful if they need to time-align anything.
• Song key: Relevant for tonal decisions — some engineers use it to check harmonic balance against the root note.
• Reference tracks: 2-3 commercially released songs in the same genre that represent the tonal balance and loudness you are aiming for. This is the single most useful thing you can provide. Be specific about what you like about each reference — the low-end on one, the vocal clarity on another.
• Known issues: "The second chorus has a slight harshness on the hi-hat" or "The bass is a bit loud in the bridge." Do not expect the engineer to find every problem — tell them what you already know.
• Master bus chain: List every plugin on your master bus, in order, with settings. Or state "master bus bypassed, no processing." Do not pre-attenuate the file to "help" the engineer — leave the mix at its native level. The mastering engineer has their own gain staging (analog attenuators, trim plugins) designed to hit their chain at the right level.
• Target loudness: If you have a specific LUFS target (e.g., -9 LUFS for a loud hip-hop master, -14 LUFS for a streaming-optimized master), say so. If you do not know, ask the engineer for a recommendation based on your genre.
• Versions needed: Main, instrumental, clean (no explicit lyrics), radio edit (shorter). List all versions you need mastered.
• Delivery format: Where will this be released? Streaming (Spotify, Apple Music), vinyl, CD, sync/licensing? Different formats require different mastering approaches.

If you are working with AI mastering tools alongside a human engineer, our comparison of MixingGPT vs LANDR vs iZotope Ozone covers what each can and cannot do at the mastering stage.

Pre-Mastering Prep by Scenario

Three common scenarios, each requiring different levels of prep:

• You are sending to a professional mastering engineer: Run the full checklist. Every item matters. Sloppy files mean revision rounds, and some engineers charge for revisions beyond the first round.
• You are mastering yourself with AI tools (Ozone 12, MixingGPT): You can skip the delivery notes, but do not skip the technical checks. AI mastering tools still need clean headroom, no master bus limiter, and mono-compatible mixes. They are less forgiving of DC offset and clipping than a human engineer who can see the problem and work around it. See our guide on how to master a song at home.
• You are sending to an online mastering service (LANDR, eMastered): These services apply automated processing with no human judgment. This means your prep matters even more — there is no engineer to catch your mistakes. Remove all master bus processing, ensure -6 dB headroom, check mono compatibility, and export at 24-bit. Read our eMastered review for what to expect from automated services.

Where Mix Preparation Is Going Next

The fundamentals of mix delivery have not changed much in two decades. Three trends are starting to shift that:

• AI-assisted pre-mastering checks: Tools like MixingGPT and iZotope's Mix Assistant now analyze your session and flag issues before export — DC offset, phase problems, headroom, even tonal balance against reference tracks. This does not replace the manual checklist, but it catches the things you missed. Expect this to become standard in DAWs within 2-3 years.
• Automatic loudness metadata: File format standards like MPEG-D DRC already support embedded loudness and dynamic range metadata. If streaming platforms adopt this more broadly, mastered files could carry LUFS data that tells Spotify and Apple Music exactly how loud the file is, reducing platform-side normalization guesswork. Mix prep would then include measuring and documenting LUFS as a formal step, not just a courtesy note.
• Cloud-based collaboration: The delivery process itself is changing. Instead of emailing WAV files and notes, engineers are using cloud platforms that sync session data, reference tracks, and version history in real time. This makes the "delivery notes" part of the checklist automatic — the engineer sees your master bus chain, your LUFS measurements, and your references without you writing them down. But the technical prep — headroom, phase, export settings — still has to be done right.

Frequently Asked Questions

How much headroom should I leave on my mix bus before mastering?

Aim for peaks between -6 dB and -3 dB on your mix bus. This gives the mastering engineer enough room to work with EQ, compression, and limiting without clipping or having to attenuate first. If your peaks are hotter than -3 dB, pull your master fader down — do not add a limiter to tame them.

Should I leave master bus processing on when exporting for mastering?

The cleanest approach is to bypass all master bus processing — no limiter, no final EQ, no bus compression that is part of the “sound.” If your mix relies on bus compression or tape saturation as an integral part of the tone, leave it on but document exactly what plugins and settings are on the chain in your delivery notes. Never leave a limiter on.

What export settings should I use for mastering?

Export at the same sample rate as your session (do not upsample). Bit depth should be 24-bit or 32-bit float. Use WAV format — never MP3, AAC, or any lossy format. Disable all normalization, dithering (unless your DAW requires it for 24-bit export), and any “apply master effects” checkboxes that are not part of your intended mix.

Should I check my mix in mono before sending it to mastering?

Yes. Mono compatibility is critical because many playback systems — phone speakers, Bluetooth speakers, club systems — sum to mono. If your low end disappears or your vocals get masked in mono, you have phase cancellation issues that need fixing before mastering, not after.

What information should I include when sending files to a mastering engineer?

Include the BPM, song key, target loudness (if you have one), reference tracks (2-3 commercially released songs in the same genre), any known issues you want addressed, whether the mix has master bus processing on or off, and the sample rate and bit depth of your files. Also note if you want instrumental and clean versions mastered.

Do I need to remove clicks, pops, and DC offset before mastering?

Yes. Clicks, pops, and DC offset are problems that should be fixed in the mix, not the master. DC offset shifts your waveform and eats headroom. Crossfade edits, trim silence at the start and end of the track, and use a click remover or manual editing to clean up any transient artifacts before exporting.

Verified June 2026. This checklist reflects current industry practice for mix delivery to mastering engineers. DAW versions referenced: Logic Pro 11.x, Pro Tools 2026.x, Ableton Live 12.x. Export settings and loudness standards align with streaming platform requirements as of mid-2026. If you spot an outdated detail, reach out to YECK.