Stems vs Multitracks: What Should You Send?

Production guides · Meme Plugins · 26 October 2026 · Updated 2 November 2026

Send stems when the recipient needs grouped mixes, such as drums, bass, instruments and vocals. Send multitracks when they need control of individual parts, such as separate kick, snare and vocal tracks. Agree an actual file list and processing plan before exporting: people often use “stems” to request either package.

The useful question is what the next person needs to change. A label alone does not define the handoff.

What each package preserves

A stem is a rendered submix. It may be mono, stereo or multichannel. A drum stem could combine several recorded drum tracks with their balance and processing already committed. Multitracks retain the individual elements for more detailed editing and mixing.

iZotope’s stems and multitracks explanation makes this group-versus-individual distinction. In practice, also say whether your individual files are raw, edited, tuned or printed through effects. A rendered synth part may already depend on sound design that the collaborator needs to keep.

1. Ask what decisions remain

  • New mix: the mixer may need individual parts and useful alternate prints so that kick, snare, vocal doubles and effects can be adjusted separately.
  • Stem mastering or a performance playback: grouped files may provide the intended limited control, if their categories are agreed.
  • Remix: ask which elements and processing the remixer wants. A stereo instrumental alone may not supply the requested flexibility.

Request the destination’s file specification. Do not impose one sample rate, bit depth or loudness figure on every delivery.

Example: turn an unclear request into an inventory

Suppose a collaborator says, “Send stems so I can remix the drums and rebalance the backing vocals.” This hypothetical request needs more detail: one combined drum file would prevent separate kick and snare changes.

A useful agreed inventory could be:

  • 01_Kick.wav, 02_Snare.wav and 03_Percussion.wav as separate parts.
  • 04_Bass.wav and 05_Keys.wav, with essential sound-design processing printed as agreed.
  • 06_LeadVocal.wav, 07_BackingHigh.wav and 08_BackingLow.wav so the harmonies remain separately adjustable.
  • Clearly labeled wet vocal references and separate reverb/delay returns if requested, with notes explaining which files overlap.
  • A dated stereo reference mix and a short delivery note.

If the collaborator instead wants just Drums, Bass, Instruments and Vocals with your balances preserved, agree those four stems. Do not silently send both sets in one folder with instructions to play everything at once.

2. Agree what “dry” means

Ask whether dry means no reverb and delay, no inserted processing, or an unedited original take. These are different requests. Label versions plainly, for example LeadVocal_Edit_Dry and LeadVocal_Edit_WetRef, and describe tuning or other committed treatment.

Shared effects need a decision too. If one return contains both vocal and guitar reverb, decide whether it travels separately or belongs in a particular stem. Avoid printing the same effect into several files and then adding the return again by accident.

3. Define the start, end and reference

Agree a common start point so files retain their relationships when imported together. Include intentional leading silence and needed effect tails. Give the recipient the tempo information, file format, version and any special import instructions. The separate WAV versus MP3 and sample-rate and bit-depth guides explain those export choices.

4. Rebuild the delivery before sending it

Import copies into an empty session at the agreed start. Check file count, alignment, missing parts and accidental duplicate effects. Compare against the reference and explain intentional differences.

Individually rendered stems may not exactly recreate a full mix passed through compression, saturation or limiting: those processors can respond differently when fed one group at a time. iZotope documents this nonlinear-processing issue. Agree whether close reconstruction is required rather than promising a perfect match automatically.

Handoff questions

Is a stereo beat a multitrack?

No. It is a combined mix. It cannot provide independent access to its original instruments.

Are separated stems the original multitracks?

No. Extracting elements from a finished mix estimates components; it does not recover the original session and every edit. State how the files were made.

Should every file be normalized separately?

Only if the agreed delivery calls for it. Separate normalization changes relative levels; verify the intended reconstruction instead of treating it as a routine cleanup step.

Once the file inventory is agreed, follow how to export aligned stems from a common start. Preserve leading silence and test late entrances in a blank session.

For complete mix versions, use the instrumental and alternate-mix workflow. For editable continuation, prepare a documented project handoff with the required media and references.


Browse all production guides → · Free browser audio tools