How to Deliver Stems to Your Mix Engineer

Deliver stems as consolidated WAV files, all starting from the same zero point, named clearly, at the session sample rate, with nothing printed you did not intend. That is a clean handoff, and a clean handoff is the difference between a mix engineer starting work in ten minutes and spending half a day untangling your session. The mix does not go wrong because the engineer is bad. It goes wrong because the stems arrived as a pile of oddly named files at three different lengths with a limiter still on the mix bus. Fix the delivery and you save a revision round, a day, and a chunk of your budget.

What is a stem, and what should you send?

A stem is a consolidated audio file of one element or group, printed from the start of the session to the end, so it drops into the engineer's timeline at bar one and lines up automatically. Send every element the song needs: kick, snare, hats, bass, each synth, each vocal, and so on, grouped sensibly. Not the master. Not a two-track bounce. The parts.

Every stem must start at the same timestamp, usually bar one or absolute zero, even if the part does not enter until the chorus. If your stems start wherever the audio happens to begin, the engineer has to manually realign every file, and one misplaced stem ruins the timing. Consistent start points are non-negotiable. This is a version-control problem as much as an audio one, the same reason I stress keeping song versions and stems organized.

How should stems be named and formatted?

Name them so a stranger understands them, because to your engineer that is what you are. "Audio 7.wav" is useless. "LeadVox_Main.wav" is a gift. Use a consistent scheme:

• Element name first: Kick, Bass, LeadVox, PadSynth.
• A qualifier if needed: LeadVox_Dry, LeadVox_FX.
• No spaces or special characters that break on other systems.

Format: WAV, 24-bit, at the session sample rate. Do not resample. Do not send MP3s. Tell the engineer the tempo and key in a text file alongside the stems, because they should not have to guess or measure it. Missing tempo and key is exactly the kind of blank-field problem that makes me say metadata is the money, even inside your own workflow.

What should you not print into the stems?

Master-bus processing. Take the limiter, the bus compressor, and the master EQ off before you print stems. Those belong to the mix and the master, not the parts. If you print stems through a mix-bus limiter, the engineer inherits your squashed dynamics and cannot undo them. Send the raw, unprocessed elements and let the engineer do their job on a clean canvas.

Also decide, per vocal and per key part, whether you want it dry or with your effects printed. Usually send both: a dry version so the engineer controls the sound, and an FX version in case your creative reverb is part of the song. Label them clearly. Ambiguity here is what causes a back-and-forth that eats days. Guessing games between collaborators are the failure mode I described in why Dropbox and email are not a workflow.

How do you make the handoff repeatable?

Write down your stem-delivery spec once and reuse it for every song. Naming convention, format, start point, what to print dry, what to leave off. Then every delivery to every engineer looks the same, and both sides know what to expect. Ad hoc deliveries are where mistakes live, because you reinvent the process under deadline every time.

Keep the delivered stems, the tempo and key, and the version note in one place tied to the track, so when the engineer asks "is this the final arrangement," the answer is one click, not a scroll through your messages. A messy handoff is one of the avoidable mistakes coordinating a music release. Run your stem deliveries through Track Pitch so the right files, named right, reach the right person with the tempo and key attached. The engineer starts mixing instead of detective work.