Sending well-prepared multitracks gives a mixing engineer the clearest possible picture of your production. The goal is to preserve the choices that define the song while making every track easy to identify, align, and play.
1. Agree on the handoff before exporting
Before you bounce files, confirm the delivery format and the engineer’s preferences. Ask about sample rate, bit depth, file type, whether they want mono tracks kept mono, and whether they prefer a particular transfer method. WAV or AIFF files are common uncompressed choices; avoid converting formats unnecessarily. A conversion cannot restore information discarded by an earlier lossy export.
Also clarify what you are delivering. “Multitracks” usually means separate audio files for individual recorded or instrument tracks. “Stems” often means grouped submixes, such as all drums or all backing vocals. The terms are sometimes used differently, so list what you plan to send and confirm that it matches the engineer’s workflow.
Send the complete session range for every file, from the same start point. This can mean exporting from bar 1 or from a shared timecode, even when a track is silent at the beginning. Consistent boundaries let the engineer import everything together without manually lining up performances. Include the song’s tempo and meter, and note any tempo changes. If the recording uses a click, say whether it is included as a separate reference file.
| Item | Practical default | Confirm when… |
|---|---|---|
| Format | Uncompressed WAV or AIFF | The engineer specifies another format |
| Bit depth | Preserve the session’s native export depth | You are changing sessions or rendering from a different system |
| Sample rate | Preserve the session rate | The engineer requests a delivery rate |
| Start and end | Same range for every file | There are pickups, long tails, or tempo changes |
| Processing | Print intentional sound; document alternatives | Effects are essential or uncertain |
These are workflow defaults, not universal requirements. Follow the engineer’s instructions when they differ, and do not upsample a session simply to make the sample-rate number larger.
2. Make the session easy to navigate
Give tracks names that describe their sound and role. “Kick In,” “Kick Out,” “Bass DI,” “Bass Amp,” “Lead Vocal,” and “Vocal Double” are more useful than “Audio 17” or “New Track 3.” Preserve distinctions that matter, such as left and right microphones, alternate takes, or separate vocal layers. Avoid renaming a group of unrelated files with ambiguous names such as “Other.”
Use a consistent numbering scheme if the session has many tracks.
For example, 01 Kick In, 02 Kick Out, and 03 Snare Top keep related files together in common file browsers.
Numbering is optional; clear names and unique identifiers are what matter.
Keep filenames reasonably short and avoid unusual symbols that may not transfer cleanly between operating systems.
Before export, remove unused tracks and empty playlists from the delivery copy if they could confuse the handoff. Do not delete material from your only session. Save a separate delivery version or make a copy of the project first. If a track contains a comp, choose the intended take and confirm that muted regions, edits, and fades behave as expected in the exported file.
Prepare a concise track list or session note. Include the song title, tempo, meter, key if known, sample rate, bit depth, and a map of unusual tracks. Mention which vocal is the lead, which guitar is the featured part, or which tracks are alternate takes. If a track name needs explanation, explain it here rather than assuming the engineer will infer its role.
3. Decide what processing to print
A mixing engineer needs the sound you intend, but may also need flexibility. Print processing that is part of the performance or identity of a sound: a guitar recorded through an amp, a committed synthesizer patch, or a vocal effect that defines a deliberate production choice. For effects that are easy to recreate and may need adjustment, ask whether the engineer wants a processed track, a dry track, or both.
When uncertain, provide clearly labeled alternatives if they are useful and manageable.
For example, deliver Lead Vocal - Dry and Lead Vocal - FX Ref, or send a processed guitar alongside its direct input when that DI is relevant.
Do not include duplicate versions of every track without explanation; large sets of nearly identical options make it harder to identify the intended sound.
Keep effects and automation understandable
If a delay or reverb is printed on a separate return, export that return from the same start point as the other files. If an effect is inserted directly on a track and its character is essential, print it or provide a reference version. Tell the engineer whether a printed effect is intended to remain, is only a guide, or is an alternate.
Automation does not always transfer with audio files. Volume rides, pans, plugin settings, and bus routing may be lost when tracks are exported individually. If a production move is important, print a reference mix that demonstrates it and describe the move in the notes. A reference mix communicates intent; it does not guarantee the engineer will reproduce every setting exactly.
Avoid normalizing individual tracks unless requested. Normalization changes file gain based on each file’s peak and can obscure the original balance. Leave sensible headroom and do not clip the export. A quiet track is not automatically a problem if it is clean and the engineer knows what it contains.
4. Export consistent, aligned files
Select the same start and end points for all exported tracks. A region beginning at the first audible sound can shift the track’s position and make alignment harder. Start every file at the session origin or at another shared point agreed with the engineer. Include sufficient tail after the final note for reverb, delay, and instrument decay to finish naturally.
Export mono sources as mono when they are truly mono, and stereo sources as stereo when their width or stereo effects are intentional.
Do not split a stereo track into two files unless the engineer requests it, and do not combine separate microphones or performances into one file merely to reduce the file count.
If a source is a stereo pair, label it clearly, such as Keys Stereo or Room Mics L-R.
Use the session’s actual sample rate and a suitable bit depth unless the engineer provides a delivery specification. The chosen rate should match the recorded session where practical; changing it requires sample-rate conversion, which is not the same as improving the source. If you must export at a different rate or bit depth, use your audio software’s standard high-quality conversion options and avoid repeated conversions. Dither is relevant when reducing bit depth; follow your software’s guidance and the engineer’s request.
Do not add a limiter or loudness processing to individual multitracks. Check that no export clips and that the files are not silent because of a muted track, disabled output, or incorrect selection. Listen to the beginning, a representative middle section, and the ending of the exports. This simple check catches missing count-ins, wrong takes, abrupt cutoffs, and tracks rendered from the wrong source.
5. Include references that explain the target
Provide one stereo reference mix that represents the arrangement and balance you want the engineer to understand.
It can include your rough mix processing; label it Reference Mix and say whether it is merely a guide or contains effects or production choices you want preserved.
If you have a second useful direction, such as a drier vocal or a more energetic chorus balance, include it only with a short explanation.
A reference can be a lossy file for convenient listening, but an uncompressed file avoids another encoding step. It should start at the same point as the multitracks when possible. Keep the reference separate from the audio files intended for mixing so it is not accidentally imported as another track.
Include a click track only if it helps establish tempo or is needed to interpret edits. If there are tempo changes, provide a tempo map or a note with bar positions and values. For a song recorded without a fixed click, say so; do not invent a precise tempo if the performance moves naturally. A rough estimate can still help, as long as it is labeled approximate.
6. Check for common problems before delivery
A short quality-control pass is more useful than assuming the export completed correctly. Re-import the files into a blank session or open them in a file player, then check the key details:
- All files begin and end at the agreed points.
- The number of files matches the track list.
- Mono and stereo files have the intended channel count.
- The exports play, are not silent, and do not contain unintended clipping.
- The rough mix and multitracks correspond to the same arrangement and edits.
- Filenames distinguish doubles, alternate takes, microphones, and effects returns.
- The final tail is long enough to preserve the song’s natural decay.
If the files do not line up, first check that the export range and timeline origin were identical. If one track is missing, verify that it was not muted, excluded by a selected-track export option, or routed outside the export path. If a stereo effect sounds different, check whether the effect was printed as a stereo file or collapsed to mono. If a file is much quieter than expected, inspect the source routing and automation before raising its level; the cause may be an export setting or an intentional dynamic part.
If you are unsure whether a process should be printed, make a clearly named alternative rather than silently choosing one version. Keep the number of alternatives practical, and explain which one represents your preference.
7. Package and deliver the handoff
Place the multitracks, reference mix, and notes in a clearly named project folder.
Keep the folder structure simple: a folder for Multitracks, one for References, and a short text or PDF file for notes is usually sufficient.
If you create an archive, confirm that it opens and contains the expected files before uploading.
Use the engineer’s preferred transfer service or delivery method; large audio sessions may exceed ordinary email attachment limits.
Name the project folder with the song title and a version or date that makes sense to both parties. Avoid sending several folders labeled only “final,” “final new,” or “final final.” If you need to replace a delivery, identify the changed files and the version they supersede. This prevents the engineer from mixing a vocal from one export with instruments from another.
Include contact and scheduling details only through the normal project communication channel, and keep the notes focused on the audio.
A useful note might say: “Tempo 96 BPM, 4/4.
Lead vocal is the comp in Lead Vox; Lead Vox FX Ref has the printed slap delay used in the rough mix.
Please keep the guitar amp tone; the DI is supplied as a backup.” That gives practical direction without prescribing every fader move.
8. Adapt the handoff to the recording setup
A home studio may use a different interface, DAW, or sample rate than the engineer’s room. That is normal when the files are exported correctly and share a common timeline. If the DAW offers consolidated export, choose the option that writes each track from the same range. If it offers individual track export, confirm whether effects, automation, panning, and master-bus processing are included; those options vary by software.
For live recordings, preserve separate microphones and note any phase or polarity decisions already made. Do not combine microphones just because they sound better together in your room; the mixer may need to adjust their balance. For programmed instruments, export audio when the engineer may not have the same plugins or sample libraries. MIDI can be useful as an extra, but it is not a substitute for rendered audio unless the engineer has compatible instruments and wants editable parts.
If a session contains tempo-synced effects, unusual instruments, or proprietary plugins, include a reference render and explain the dependency. A screenshot or session file may help when requested, but the multitracks and concise notes should remain usable on their own. No export checklist can remove every difference between monitoring systems or guarantee the mix will translate exactly; the engineer’s playback environment and the source recordings still shape the result.
Delivery checklist
Before sending, verify that you have the aligned multitracks, a useful reference mix, a track list, tempo and meter information where known, notes about printed effects and intentional processing, and a clear folder name. Then send the engineer a brief message stating what is included and which version to use. That small amount of organization makes it easier to focus the session on the music.