What to Send a Mastering Engineer Before You Order a Master

What to Send a Mastering Engineer Before You Order a Master

Before you order a master, send the mastering engineer your final approved mix as a clean WAV file, a loud rough version if you have one, one or two reference tracks, notes about what you want protected, the song title and version details, and any required alternate deliverables such as clean, instrumental, performance, or radio versions. Do not send a random folder of unfinished bounces and expect the engineer to guess which one is final.

Ordering mastering should feel simple: send the final mix, explain the goal, and get back a release-ready master. The problems start when the mastering engineer receives three different files called final, a clipped MP3, no reference, no notes, and no clue whether the artist wants a loud rap master, a clean R&B master, a streaming-safe version, or an album-matched sequence. Then the job begins with questions instead of mastering.

A mastering engineer does not need your entire creative history. They need the correct mix, the correct context, and enough direction to make final decisions without guessing. The better your delivery package is, the more time goes into tone, loudness, translation, spacing, and quality control. The worse the delivery package is, the more time goes into file repair, clarification, and preventable revisions.

This guide is for artists who are about to order mastering for a single, EP, or small release. If your mix is not approved yet, start with the article on exporting files for stem mastering without costly mistakes or decide whether you need a mix revision first. Mastering is the final polish stage, not the place to solve every issue inside the session.

The Short Answer

Send one final clean pre-master WAV, one approved rough or loud reference bounce, one or two commercial reference tracks, brief notes about the desired sound, the exact song title and artist name, the sample rate and bit depth if known, and a clear list of deliverables. If the engineer offers stem mastering, send grouped stems only after they ask for them or after the service specifically requests them.

Item to send	Best format	Why it matters
Final mix	WAV or AIFF, clean, full length	This is the file the engineer masters
Loud rough	WAV or MP3 reference only	Shows the vibe if you mixed into a limiter
Reference tracks	Links or clearly named files	Shows tonal direction and loudness taste
Notes	Short text document or order note	Protects your priorities and reduces guessing
Version list	Main, clean, instrumental, performance, radio	Prevents missing deliverables after approval
Deadline	Release date and preferred review date	Helps the engineer schedule revisions realistically

The best delivery package is clear, not huge. If the engineer has to open ten files to figure out which one is final, the package is not clear. If the engineer can open one folder and immediately understand the song, target, and version needs, you did it right.

Send the Final Approved Mix First

The final approved mix is the most important file. It should be the version you would release if mastering only made it louder, cleaner, and more consistent.

Do not send a mix you secretly dislike and hope mastering will rebuild it. Mastering can improve translation, loudness, tone, spacing, stereo feel, and final polish. It cannot reliably fix a lead vocal that is too buried, a kick and 808 relationship that is wrong inside the mix, background vocals that are badly balanced, or edits that should have been cleaned before export.

Export the final mix from the beginning of the song to after the final fade or effect tail. Do not trim the first downbeat too tightly. Do not cut off the last reverb or delay tail. Do not fade randomly unless the fade is part of the approved mix. If the song has silence at the beginning or end for a reason, leave it and mention it.

A good file name helps more than people think. Use something like ArtistName_SongTitle_FinalMix_48k_24bit.wav. If you make a new version later, update the version number: v2, v3, approved, clean, instrumental. Avoid "final," "final2," "newfinal," and "realfinal" because those names stop meaning anything after a few bounces.

Remove the Right Master Bus Processing

If a limiter, clipper, or loudness chain was only there to make the rough mix loud, send a clean pre-master without it. If a bus compressor or saturation is part of the approved tone, ask before removing it.

This is where many artists get stuck. They hear the mix through a loud rough chain for weeks, then they remove everything from the master bus and the song suddenly feels smaller. That does not automatically mean the rough chain should be printed. It means the rough chain was helping you hear a temporary master. The mastering engineer needs to know what you liked about it.

A useful delivery can include two bounces: a clean pre-master and a loud rough reference. The clean pre-master gives the engineer room to work. The loud rough tells them how aggressive, bright, wide, or hyped the song felt when you approved it. Label them clearly so the engineer does not master the rough by mistake.

Spotify's loudness guidance is a good reminder that loudness is not only about the number printed into your file. Spotify explains that playback normalization can apply gain changes during playback, and its mastering tips discuss true peak safety for lossy encoding. Apple Digital Masters guidance also emphasizes high-quality source files and avoiding clipping during encode checks. The practical lesson is simple: do not destroy the source file chasing volume before mastering.

Send WAV or AIFF, Not an MP3 as the Main File

The main mix for mastering should be a high-quality lossless file, usually WAV or AIFF. MP3 can be used for quick listening references, but it should not be the main source file unless there is no better option.

Mastering works from the quality of the file you send. A compressed MP3 may be convenient, but it can contain artifacts that become more obvious after EQ, limiting, widening, or loudness work. If you recorded and mixed at a higher quality, do not throw that away before the final stage.

Most online mastering workflows are comfortable with 24-bit WAV files at the song's native sample rate. Some engineers also accept 32-bit float or AIFF. The safest answer is to follow the service instructions. If the service page asks for a 24-bit WAV at 44.1 or 48 kHz with headroom, send that. If the engineer requests 32-bit float, send that. Do not upsample just to make the file look more professional.

If you are not sure whether your file is ready, compare it with the article on signs a mastering preset is not enough for release. That guide helps separate source-quality problems from final loudness problems.

Include a Rough Mix or Loud Reference Bounce

A rough mix tells the mastering engineer what you have been hearing while making decisions. It is especially useful if the clean pre-master sounds quieter or less exciting after removing the temporary limiter.

The rough mix does not have to be perfect. It just has to communicate the approved direction. If you have been playing a version for friends, sending it to collaborators, or driving around with it in the car, include that version as "rough reference" or "loud rough." The engineer can compare the clean file to the rough and preserve what matters while improving the final master.

Do not send five roughs unless each one has a clear purpose. One rough is usually enough. If there are two important versions, label why: "Artist loud rough" and "Label feedback rough," or "Version with brighter vocal" and "Version with darker vocal." Otherwise the engineer has to guess which reference matters most.

If you are mastering a group of songs, rough references also help preserve project direction. The engineer can hear which songs are meant to feel louder, softer, darker, wider, more intimate, or more aggressive before making the final sequence decisions.

Choose One or Two Reference Tracks

Reference tracks are useful when they are specific. They become confusing when they point in five different directions.

A reference track can show the mastering engineer the kind of low end, vocal brightness, punch, loudness, or overall polish you like. But the reference is not a command to copy another record. Your mix, arrangement, vocal tone, beat, and genre may not support the same exact result. Use references as direction, not as a guarantee.

Send one or two references with a short note for each. For example: "I like the controlled low end in this song," or "I like how the vocal stays bright without getting sharp," or "This is the loudness range I am aiming for, but I do not want the master to distort." Those notes are more helpful than pasting a playlist with no explanation.

Reference quality matters too. If possible, send links to official versions on a streaming platform or high-quality files you own. Do not send a low-quality rip and expect the engineer to treat its artifacts as part of the target sound.

Write Notes That Protect the Song

Good notes tell the engineer what matters most. Bad notes tell the engineer to make everything louder, cleaner, warmer, wider, punchier, and more professional without any priority.

Before ordering, write down the three things you care about most. Maybe the lead vocal must stay intimate. Maybe the 808 needs to hit hard without swallowing the vocal. Maybe the master should be competitive but not harsh. Maybe the song is for an EP and needs to sit between two other tracks. These priorities help the engineer decide what to protect when tradeoffs appear.

Use plain language. You do not need to sound technical to be useful. "The hook feels slightly sharp on earbuds," is better than guessing at a frequency if you are not sure. "Do not make the intro too loud compared to the drop," is better than saying "fix dynamics" with no context. A good engineer can translate practical notes into technical decisions.

If the song is loud rap, aggressive trap, R&B, acoustic, pop, or dance music, say that. Different genres tolerate different levels of density, brightness, and limiting. The guide on what to ask a mastering service for loud rap songs is useful because it shows how to talk about loudness without only asking for a maximum number.

List Every Deliverable Before Checkout

If you need more than one version, say so before the master is started. Clean, explicit, instrumental, performance, TV, and radio versions can change the workflow.

A single streaming master is simple. Multiple versions require planning. If you need a clean version, the clean mix should be exported before mastering. If you need an instrumental, send the final instrumental mix. If you need a performance version with backing vocals but no lead, prepare that mix clearly. Do not assume the mastering engineer can create those versions from one stereo file.

For albums and EPs, list track order and any spacing preferences. Do you want songs to flow tightly? Do you need extra silence between tracks? Are there skits or transitions? Is one track intentionally softer? These choices are part of mastering when the release is more than one song.

Also mention deadline needs realistically. If your release is tomorrow, the engineer may have fewer revision options. If the distributor deadline is two weeks away, say that too. A clear timeline helps everyone avoid rushing the wrong step.

When to Send Stems Instead

Only send stems when the service asks for stem mastering or when the engineer agrees that stem control is needed. Do not send stems as a substitute for choosing the final mix.

Stem mastering can help when the mix is close but needs a little more control over groups like drums, bass, vocals, music, or effects. It is not the same as sending every raw track. If you send 80 files, you are probably asking for mixing or stem mixing, not mastering. That changes cost, timeline, and expectations.

When stems are requested, export full-length, time-aligned, clearly labeled files. Include the stereo rough mix so the engineer can rebuild the intended balance. Make sure the stems play together and match the approved mix before sending them. If the combined stems do not match your rough, fix the export before uploading.

If you are choosing between stereo mastering, stem mastering, and mix work, read how to choose a mastering service for your first Spotify release. It will save you from paying for the wrong stage.

What Not to Send

Do not send every bounce you have, unfinished session exports, clipped rough masters, unlabeled alternates, or files that require the engineer to guess which version is approved.

A messy upload folder is one of the easiest ways to slow down mastering. If the folder contains old hooks, rejected mix versions, beat snippets, random phone references, and three files called final, the engineer has to stop and clarify the basics before making any sonic decision. That extra friction matters because mastering depends on confidence. The engineer should be evaluating tone, loudness, translation, and final polish, not acting as a detective for your file system.

Remove anything that is not part of the job. If a rough is only there as a vibe reference, label it "rough reference." If a clean version is approved, label it "clean mix." If an instrumental needs mastering, label it "instrumental mix." If a file is old but you want the engineer to hear one specific thing from it, explain that in the notes instead of letting it sit in the folder with no context.

Also avoid sending screenshots of settings as a replacement for audio. A mastering engineer cannot master a screenshot of your limiter, and most do not need to know every plugin on your mix bus unless a specific problem is being discussed. Send the correct audio first. Then use notes to explain the decisions that matter.

If the Mix Changes After You Order

If you change the mix after ordering, tell the engineer immediately and send one clearly labeled replacement file. Do not quietly add a new file to the folder and hope they notice.

Mix changes happen. Maybe a collaborator asks for the hook vocal up. Maybe you catch a click at the end of the second verse. Maybe the clean version has the wrong word muted. The issue is not that revisions exist. The issue is version confusion. If the engineer masters v1 and you later say v3 was the real final, the whole process loses time.

When a replacement is necessary, use a clear name such as Artist_Song_FinalMix_v2.wav and write one sentence explaining the change. Keep the old file out of the active upload folder if possible. The engineer should know exactly which file to master and which files are references only.

If the new mix changes the tone, low end, vocal level, or ending fade, mention that too. A small file change can create a different mastering decision, so the note helps the engineer review the right details instead of assuming the new file is identical.

Pre-Order Mastering Checklist

Use this checklist before you place the order. It catches the mistakes that usually slow down the first pass.

1. Listen to the final mix all the way through from start to finish.
2. Confirm the file does not clip and the ending tail is not cut off.
3. Export a clean WAV or AIFF at the requested sample rate and bit depth.
4. Export or label the loud rough separately if you want the engineer to hear it.
5. Choose one or two reference tracks and explain what you like about them.
6. Write short notes about loudness, tone, low end, vocal brightness, and priorities.
7. List all versions needed: explicit, clean, instrumental, performance, radio, or EP sequence.
8. Put everything into one folder with clear file names.
9. Remove old or rejected bounces from the upload folder.
10. Send the file transfer link and notes before or immediately after ordering.

This checklist is simple because the best mastering prep is simple. The goal is to remove uncertainty. When the engineer knows what file is final, what the target is, what versions are needed, and what problems you are worried about, the first master is more likely to land close.

A Clean Mastering Delivery Folder Example

A good mastering folder should let the engineer understand the release without opening a long message thread.

Use one folder for the song. Inside that folder, include the final mix, the loud rough or reference bounce, the notes, and any needed alternate versions. A simple structure might be Final Mix, Reference, Notes, and Alternates. If you are sending stems, create a separate Stems folder so the engineer does not confuse full mixes with grouped parts.

The final mix should be the main file. Name it clearly, such as Artist_Song_FinalMix_48k_24bit.wav. If you are unsure about sample rate or bit depth, do not invent a new export setting at the last second. Send the highest-quality version from the session and tell the engineer what it is. A clean 24-bit WAV or AIFF is usually safer than an MP3, and lossless files give the engineer more room to work.

The rough reference should be labeled as a reference, not as the final mix. Many artists send a loud self-master because they like the energy. That is fine as long as the engineer knows it is not the clean source file. Label it Artist_Song_LoudReference.mp3 or Artist_Song_RoughMaster.wav. Then explain what you like about it. Maybe the vocal feels exciting. Maybe the bass level feels right. Maybe the hook has the right energy. The engineer can use that information without being forced to master from a crushed file.

The notes file can be short. Include the song name, artist name, deadline, release goal, reference tracks, known concerns, and version needs. You do not need a full essay. You need the information that affects mastering decisions. If the vocal is intentionally dark, say that. If the 808 is supposed to feel heavy, say that. If the clean version must match the explicit version, say that before work starts.

If you need multiple deliverables, list them before ordering. Do not assume every mastering order includes clean, instrumental, performance, acapella, radio, and show versions. Those may require separate exports or extra checking. The cleaner you are before checkout, the less likely you are to create a last-minute revision that was really a missing deliverable.

This is also where recurring release workflow becomes easier. Once you have one clean delivery folder, save it as your own prep template. The next time you order mastering, duplicate the structure and replace the files. That keeps every future release more organized.

FAQ

Should I send a WAV or MP3 to a mastering engineer?

Send a WAV or AIFF as the main file. MP3 can be useful as a rough reference or quick listening file, but it should not be the main source for mastering if you have a clean lossless export.

Should I remove the limiter before mastering?

Usually yes if the limiter was only used to make the rough mix loud. If the limiter, clipper, or saturation is part of the approved sound, send a clean version and a loud rough, then ask the engineer which one they prefer to use.

How much headroom should I leave for mastering?

Do not chase an exact number at the expense of the mix. The practical goal is a clean, unclipped file with no heavy final limiting unless requested. Follow the mastering service's file-prep instructions when they give a specific target.

Do I need to send stems for mastering?

Not always. Standard mastering usually works from one stereo mix. Send stems only if you ordered stem mastering or if the engineer asks for grouped stems because the stereo mix needs limited balance control.

How many reference tracks should I send?

One or two strong references are enough for most singles. More references can be confusing unless each one has a clear note, such as one for low end and one for vocal brightness.

Should I send clean and instrumental versions before mastering?

Yes, if you need those versions. Prepare and label the clean, instrumental, performance, or radio mixes before mastering so the engineer can master each deliverable consistently.