How to Prepare and Label Stems for Mixing

# How to Prepare and Label Stems for Mixing: The Complete Handoff Guide

Sending your project to a mix engineer is one of the most consequential steps in the production process, and it is also one of the most commonly mishandled. Poorly exported stems, inconsistent naming, and missing session information cost everyone time and money. When we receive a session at Animus Studios, the quality of the stem prep directly affects how quickly we can get into the creative work of [mixing](https://animusstudios.au/services/mixing) and how clean the final result will be.

Getting this right is not complicated, but it does require a methodical approach before you hit export. Whether you are working in Pro Tools, Logic Pro, or Ableton Live, the principles are the same. The goal is to hand off a set of files that any professional engineer can open, understand, and work with immediately, without needing to chase you for clarification.

This guide covers every element of a proper stem handoff: file format, sample rate, bit depth, headroom, naming conventions, tempo and key information, and reference tracks. Follow this process and your mix will start on the right foot.

---

File Format: WAV, Not MP3

Export your stems as WAV files. This is non-negotiable. MP3 and other lossy formats introduce compression artefacts that compound across processing chains. Even a high-quality 320kbps MP3 has had audio information permanently discarded, and that loss becomes audible once you start applying EQ, compression, and saturation in the mix.

AIFF is also acceptable if you are working on a Mac and your engineer has confirmed they can receive it, but WAV is the universal standard. Do not export as FLAC for mixing purposes. FLAC is a lossless format, but it adds an unnecessary decompression step and is not natively supported in all DAWs without additional plugins or conversion.

---

Sample Rate and Bit Depth

Export at the sample rate your session was recorded in. If you tracked at 48kHz, export at 48kHz. If you worked at 44.1kHz, export at 44.1kHz. Do not upsample your files before sending them. Upsampling does not add audio information and can introduce aliasing artefacts depending on the algorithm used. The mix engineer will work at whatever sample rate the project requires and handle any conversion needed for the final deliverable.

Bit depth should be 24-bit as a minimum. If your DAW supports 32-bit float internally and you want to export at 32-bit float, that is fine and increasingly common in modern workflows. It gives the engineer a little extra headroom in the digital domain. Do not export at 16-bit. That is a delivery format for consumer audio, not a working format for mixing.

---

Headroom: Leave Room to Work

This is the area where we see the most problems. Producers who have been working on a mix themselves often send stems that are already clipping or sitting dangerously close to 0 dBFS. A mix engineer needs headroom to apply gain, compression, and processing without immediately hitting the ceiling.

The standard expectation is that your stems should peak no higher than around -6 dBFS, with most material sitting comfortably between -18 and -12 dBFS RMS. If your session has been heavily processed and your master bus is already pushing hard, you may need to pull your faders down before exporting. Do not apply a limiter to individual stems before sending them. Do not apply a limiter to your master bus and then export stems through it. Send the engineer the raw, unprocessed signal with appropriate gain staging.

If you have been using a reference loudness target of around -14 LUFS integrated for streaming, that is a mastering consideration, not a mixing one. Your stems should not be pre-limited to hit that target. That work happens at [mastering](https://animusstudios.au/services/mastering), after the mix is complete.

---

Consolidate and Align to the Same Start Point

Every stem must start at the same point in the timeline, typically bar one, beat one, or the absolute beginning of the session at 00:00:00. This is how the engineer lines everything up in their DAW without manually nudging files into position. If your kick drum stem starts at bar one and your synth pad stem starts at bar 32 because that is where it first appears, the two files will be different lengths and will not line up when imported.

In Pro Tools, use the Consolidate Clip function to render each track from the session start. In Logic Pro, use the Export All Tracks as Audio Files option with the cycle range set to cover the full arrangement. In Ableton Live, use Export Audio/Video with the render start set to bar one. The point is that every file should be exactly the same length when you are done.

---

Stem Naming: Be Specific

Generic names cause delays. A folder full of files named "Audio 1," "Audio 2," and "Track 03" tells the engineer nothing. Every file should be named clearly and consistently so the engineer can build their session without opening each file to listen and guess what it contains.

A reliable naming convention follows this structure: ProjectName_StemName_Version. For example:

• ProjectName: Use the song title or a short identifier, no spaces (use underscores or hyphens)
• StemName: Be descriptive and specific, for example KickDrum, SnarTop, SnarBot, HiHat, OverheadL, OverheadR, RoomMic, BassDI, BassAmp, ElecGtr1, AcGtr, LeadVox, BackingVox1, BackingVox2, Synth1, Pad, Piano, StringsL, StringsR
• Version: Include a version number if you are sending revisions, for example V1, V2

A full example: `DarkHorse_LeadVox_V1.wav`, `DarkHorse_KickDrum_V1.wav`, `DarkHorse_BassDI_V1.wav`.

Group your files into folders by instrument family if the track count is high: Drums, Bass, Guitars, Keys, Vocals, FX. This makes importing into a new session much faster.

---

What to Include and What to Leave Out

Include These Elements

• Dry vocals: Send the raw vocal take with no reverb, no delay, no pitch correction applied. The mix engineer will handle spatial processing and may use Antares Auto-Tune or Melodyne for any tuning work. If you have already done tuning in your session and are happy with it, confirm this in your notes and send the tuned but otherwise dry file.
• DI and amp tracks separately: If you recorded bass or guitar with both a DI signal and a mic on an amp, send both. The engineer may want to blend them or re-amp the DI.
• Parallel tracks: If you have a parallel compression bus or a parallel drum bus that is part of your sound, send it as its own stem and label it clearly, for example `DarkHorse_DrumParallelComp_V1.wav`.
• Printed effects that are part of the arrangement: If a specific reverb tail or delay throw is integral to the arrangement and not just a mix effect, print it as its own stem.

Leave These Out

• Master bus processing (limiters, stereo wideners, master EQ)
• Send effects that are generic mix reverbs or delays (unless they are printed as part of the arrangement)
• Muted tracks that are not being used in the final arrangement

---

Tempo, Key, and Session Notes

Include a simple text document or PDF with your stems that covers the following:

• BPM: The tempo of the track, and whether it is a fixed tempo or uses tempo automation
• Key and mode: For example, A minor, F# major. This helps the engineer make informed decisions about harmonic processing and any pitch-based effects
• Time signature: Most tracks are 4/4, but flag it if yours is not
• Structure: A brief breakdown of the arrangement, for example Intro 8 bars, Verse 16 bars, Chorus 16 bars, Bridge 8 bars, Chorus out 16 bars. This helps the engineer navigate the session quickly
• Special notes: Flag any timing issues, tuning problems, or creative intentions you want the engineer to be aware of. If the guitar in the bridge is intentionally out of tune for effect, say so. If there is a click or noise on the vocal track at 2:34 that needs editing, flag it

---

Send a Reference Track

A reference track is one of the most useful things you can send alongside your stems. Choose a commercially released track that represents the sonic direction you are aiming for, whether that is the tonal balance, the width, the drum sound, or the overall energy. It does not need to be an exact match to your genre. It just needs to communicate something specific about what you are after.

Be clear about what you are referencing. "I want it to sound like this track" is less useful than "I love the low-end weight and the way the vocals sit forward in this mix." The more specific you are, the more efficiently we can work toward the result you want.

---

Checklist Before You Send

• WAV format, 24-bit minimum, matching session sample rate
• All stems peak no higher than -6 dBFS, no limiting applied
• All stems consolidated from the same start point, same file length
• Files named clearly and consistently
• Organised into folders by instrument group
• Session notes document included with BPM, key, time signature, and structure
• Reference track included with specific notes on what you are referencing

---

Getting your stems right before you send them is a professional skill that saves time, reduces revision rounds, and gives your mix engineer the best possible starting point. At Animus Studios we offer [remote mixing and mastering](https://animusstudios.au/services/remote-mixing-mastering) for artists across Brisbane and Australia, and the sessions that arrive well-prepared consistently produce better results. The prep work you do before the session is part of the record.