Sending tracks to a mixing engineer for the first time can feel a bit daunting. What format? How many tracks? Should the kick and bass be on separate tracks or together? Do you leave your effects on or strip everything back?
These are all reasonable questions, and getting them right matters more than you might think. A well-prepared session means the engineer can get straight into the creative work. A poorly prepared one means the first hour gets spent on admin, troubleshooting, and back-and-forth emails that could have been avoided entirely.
This guide covers everything you need to know before you hit send.
What Are Multitracks / Stems, and Why Not Just Send a Stereo Mix?
A stereo mix is a single two-channel file with everything baked in. It's what ends up on streaming platforms. A "stem", even if the term is often used nowadays to describe individual tracks, is really a grouped, isolated export of a part of your song: all your drums on one file, all your synths on another, your various vocals on a third, and so on.
Sending individual multitracks gives the mixing engineer something granular to work with. They can balance your kick against your bass, push the vocals forward in the chorus, and make the low end translate properly on different systems. None of that is possible with a stereo mix, and only barely with a few grouped stereo stems. You want to essentially hand over all the ingredients instead of the finished dish, and let someone who does this every day decide how to best cook it, without making major changes.
How to Organize and Name Your Files
This is where most people go wrong, and it's also the easiest thing to get right with a bit of preparation.
Name every file clearly and consistently. "Kick_Out.wav," "Bass_Synth.wav," "LeadVocal_Dry.wav" are good. "final_v3_REAL_FIXED.wav" is not. Your engineer has seen hundreds of sessions. A clean file name tells them immediately what they're dealing with and saves time that would otherwise be spent listening through unlabeled files trying to figure out what's what.
Group your files logically. Drums together, bass elements together, melodic elements together, vocals together.
Technical Specifications
Format: WAV/AIFF, always. Not MP3, not AAC, not anything compressed. If your DAW defaults to something else, change it.
Sample rate and bit depth: Export at the same sample rate and bit depth your project was recorded in. If your session is 44.1kHz / 24-bit, export at 44.1kHz / 24-bit. Don't upsample and don't downsample. Just match the session.
Start point: Every track should start at the very beginning of the project, bar one, beat one. Even if the kick doesn't come in until bar 16. This is critical. It's how everything stays in sync when the engineer imports your files.
Leave headroom: Don't clip your tracks. If individual tracks are hitting 0dBFS or going into the red, pull them down before exporting. Most of the time though, even if the summed signal of all your tracks together may be hitting the red, your individual tracks will be fine. But always doublecheck that no file is clipping above 0dBFS.
A Few Things to Sort Before You Export
Before you actually bounce anything down, three things are worth getting right that will make a real difference to what the engineer can do with your tracks.
Effects as inserts versus send effects. If you have reverb or delay running as inserts directly on a track, either minimize the wet balance before exporting or, better yet, switch to send effects and export the FX channels separately. The reason is that heavily wet sounds are difficult to gate or compress, and what sounds balanced in your mix will often feel exaggerated once the engineer starts working. The exception is any distortion, reverb, or delay that is doing genuine sound design work and gives the track its identity. If it's part of the character of the sound, keep it exactly as it is.
Master bus processing. Deactivate any limiting, EQ, or compression on your master bus before exporting. All of it. The engineer needs dynamic range and headroom to work with, and a limiter on the master output bakes in decisions that should happen at the mastering stage, not before.
EQ on individual tracks. Try to go easy on low cuts and high cuts on individual sounds. Filtering out frequencies during production is a natural instinct, but once they're gone they're gone. The engineer can always filter as needed during the mix, but they can't bring back what isn't there. Leave more in than you think you need to.
What to Include Beyond the Audio
A short note goes a long way. Include the tempo and time signature of the track, the key if it's relevant, any reference tracks you have in mind, and any specific notes about what you want the mix to achieve. If there's a section you're not happy with, say so. If the drop needs to hit harder than anything else, say that too.
The more context you give, the less guesswork is involved, and the closer the first mix will be to what you're hearing in your head.
How to Actually Send the Files
Once everything is exported, named, and organized into a folder, you need to get it to your engineer. This is where things get surprisingly messy for a lot of people.
Avoid random download links that expire after seven days. Avoid sharing a Google Drive folder full of unlabeled files with no context. Avoid sending individual files over email. None of these are professional workflows and all of them create unnecessary friction.
Full transparency here: I use Echoe with my own clients because it keeps the track layout clean, links never expire, and we can use playlists and versioning to stay organized as the mix develops. Timestamped comments on the waveform mean feedback happens in context rather than in a chain of emails saying "around the two minute mark the snare feels a bit thin." It just makes the whole process smoother.
A Quick Checklist Before You Send
- •WAV format, correct sample rate and bit depth matching your session.
- •All tracks start at bar one beat one and have equal length.
- •No clipping, peaks safely below 0dBFS.
- •Master bus limiter bypassed.
- •Files named clearly and grouped logically.
- •Tempo, key, and reference tracks included in your notes to the engineer.
If all of that is ticked off, you're in good shape.
Conclusion
Preparing tracks properly is one of those things that takes fifteen minutes upfront and saves hours on the other end. A well-organized session is a signal that you take the work seriously, and it gives the engineer the headroom they need to focus entirely on making the mix sound as good as possible.