Stems Vs Multitracks: What’s The Difference?

If you’re getting ready to send a song off for mixing, you might have seen people use words like stems, multitracks, trackouts, session files, and rough mixes.

The confusing part is that these words often get used interchangeably, even though they don’t always mean the same thing.

For most mixing jobs, what I usually need is a folder of multitracks: individual audio files for each part of the song, all exported from the start of the session so they line up correctly.

If you’re not sure what to send, this guide will walk you through the difference.

And if you’re preparing a song for mixing and want me to check the files before you book, you can upload them here and I’ll happily take a quick look.

Table of Contents

  1. Stems vs Multitracks

  2. What Should You Send?

  3. Dry or Wet Tracks?

  4. Common Mistakes

    Unsure? Get in touch

What Are Multitracks?

Multitracks are the individual audio files that make up your song.

For example, a typical song might include separate files like:

  • Lead vocal

  • Backing vocals

  • Kick drum

  • Snare drum

  • Toms

  • Overheads

  • Bass guitar

  • Rhythm guitar left

  • Rhythm guitar right

  • Lead guitar

  • Piano

  • Synth

  • Percussion

Each file is its own separate part of the song.

This gives the mixing engineer full control over the balance, tone, panning, compression, EQ, effects, automation, and overall sound of the mix.

So instead of adjusting one finished stereo file, the engineer can shape each element individually.

That’s why multitracks are usually the best format to send for mixing.

What Are Stems?

Stems are grouped audio files.

Instead of sending every individual track separately, stems combine related parts into groups.

For example, a stem export might include:

  • Drums stem

  • Bass stem

  • Guitars stem

  • Keys stem

  • Vocals stem

  • Backing vocals stem

  • Effects stem

Each stem usually contains several tracks already blended together.

So a β€œdrums stem” might include the kick, snare, toms, overheads, rooms, samples, and drum effects all printed into one stereo file.

Stems can be useful in some situations, but they give the mixing engineer much less control than full multitracks.

Simple Example

Imagine your chorus has a vocal, drums, bass, guitars, and synths.

With multitracks, I can adjust the kick drum separately from the snare, brighten one guitar without changing the other, turn down a harmony vocal, or treat the lead vocal differently from the backing vocals.

With stems, I may only have a single β€œdrums” file, a single β€œguitars” file, and a single β€œvocals” file.

That means if the snare is too loud inside the drum stem, I can’t simply turn down the snare. I can only process the whole drum group.

That’s the key difference.

Multitracks give control. Stems give grouped control.

Black and white photo of an old audio mixing console with several meters showing levels and a keyboard below.

Which Should You Send For Mixing?

For a full mix, you should usually send multitracks.

That means each individual part of the song exported as its own WAV file, ideally starting from the same point in the timeline.

This gives the best chance of getting a detailed, polished mix.

Stems are usually better suited for situations where:

  • The song has already been mixed and only small grouped adjustments are needed

  • You’re sending files for a remix

  • You’re preparing backing tracks for live performance

  • You want alternate versions, such as instrumental, acapella, drums only, or TV mix

  • You need stem mastering rather than a full mix from individual multitracks

For standard online mixing, though, multitracks are almost always the better option.

If you’re not sure whether your song actually needs mixing, mastering or something in between, I’ve covered that separately in Does My Song Need Mixing Or Mastering?

What About A Project File?

A project file is the actual DAW session, such as a Logic, Pro Tools, Ableton, FL Studio, Cubase, Studio One, or Reaper session.

These can be useful in some cases, but they are usually not the safest way to send a song for mixing.

Project files can cause problems because they depend on things like:

  • The same DAW version

  • The same plug-ins

  • The same virtual instruments

  • The same samples

  • The same routing

  • The same software settings

  • The same operating system compatibility

Even if the project opens, missing plug-ins or files can completely change the sound.

That’s why exported WAV multitracks are usually much more reliable. I can import them into my own mixing session, line them up, and get to work without depending on your exact software setup.

Where Does the Rough Mix Fit In?

Alongside your multitracks, it’s also really useful to send a rough mix. This gives the mixing engineer a reference for the balance, effects, arrangement and general direction you were hearing while working on the song.

If you’re not sure exactly what a rough mix is or what it should include, have a read of What Is a Rough Mix?.

Close-up of a section of a mixing console with knobs and sliders, black and white photo.

Should You Send Dry Or Wet Tracks?

This depends on the sound.

As a general rule, give me clean versions where possible, but keep processing that is genuinely part of the character of the instrument or performance. If you’re unsure, sending both a dry and wet version gives me the most flexibility.

There are plenty of grey areas here, particularly with vocals, amp sims, synths and creative effects, so I’ve covered this properly in Should I Leave Effects On When Exporting Multitracks for Mixing?

What File Format Should You Use?

WAV is the simplest default for mixing, although AIFF is absolutely fine too. Avoid MP3 wherever possible, as it uses lossy compression and is much better suited to listening copies than source files for a mix.

The important thing is that your files are exported cleanly, at the same sample rate as your session, and all start from the same point so they line up correctly.

For the full export and preparation checklist, read Preparing Your Multitracks for Mixing.

Close-up of an audio mixing console with knobs and faders in black and white.

Common Mistakes To Avoid

Here are the biggest issues that cause delays when sending files for mixing.

1. Sending Stems When Multitracks Were Needed

If you only send grouped stems, the mix engineer has limited control.

For example, if all backing vocals are baked into one stereo stem, individual harmonies can’t easily be balanced, tuned, edited, or processed separately.

2. Exporting Files From Different Start Points

All files should start from the same point, usually bar 1 or the very beginning of the session.

Even if an instrument only enters halfway through the song, the exported file should still include silence before it enters so everything lines up correctly.

3. Sending Only The DAW Project

A Logic, Ableton, FL Studio, or Pro Tools session might seem convenient, but it can cause compatibility issues.

Exported WAV multitracks are usually safer.

4. Printing Too Much Processing

Avoid permanently baking in processing that is only there for the rough mix. Creative processing that is genuinely part of the sound is absolutely fine, and if you’re unsure, send both processed and clean versions.

5. Forgetting The Rough Mix

The rough mix is important. It tells the mixing engineer what you’ve been hearing and what direction the song is meant to go in.

Without it, there’s more guesswork.

Quick Summary

For most mixing jobs:

Send multitracks, not just stems.

A good mixing file package usually includes:

Stems are useful in some situations, but they are not the same as multitracks.

For a full mix, multitracks usually give me the most control and flexibility to work with.

Need Help Checking Your Files?

If you’re preparing a song for mixing and you’re not sure whether you’ve exported the right files, feel free to send them over before booking.

I’ll happily take a quick look and let you know whether everything is ready, or whether anything needs fixing first.

Upload your files here