How to send stems to a client

A request for stems may mean grouped instrument bounces or individual multitracks. Clarify the contents before exporting, especially if they were not included in the original quote.

First, agree what "stems" means here

Stems combine related tracks into groups, such as drums, bass and vocals. Multitracks contain the individual recorded or programmed parts. Ask which the recipient needs, how the files will be used and whether processing should be included.

• Which groups? A remixer might want just drums, bass, vocals and "everything else." A sync licensor might have a fixed list. A label archive may require individual multitracks.
• Effects printed or separate? Reverbs and delays inside each stem, or as their own wet stem?
• Included or extra? If stems weren't in the original agreement, agree the extra work and fee before exporting (see what counts as in scope).

Export settings and checks

• Every stem starts at bar one. Even the ones that are silent for three minutes. The recipient can then align every file to the same start point. Include leading silence where a part enters later.
• Print past the last tail. Set the render range beyond the final note so reverb and delay tails finish naturally. Listen to the ending of each exported file to check for cut-off tails.
• Match the mix format. 24-bit WAV at the session's sample rate, same as the mix delivery itself. Use WAV to avoid further lossy encoding during processing.
• Keep bus processing in, decide about the mix bus. Group processing is what makes a stem sound like the record, so it's printed. The mix bus chain is the judgment call: print it if the stems should sum to the mix, leave it off if someone downstream will process the sum again. Ask, then write the answer in the notes file.
• Check shared bus processing. A compressor or limiter may respond differently to soloed groups, so the exported stems may not sum to the processed mix. Agree how to handle this and include a stereo reference.
• Watch levels on soloed groups. Shared bus processing can respond differently when a group is soloed. Check each exported stem for clipping.

Naming and the notes file

Use a consistent order and descriptive names, such as 01_Drums.wav, 02_Bass.wav and 03_LeadVox.wav. Put each song in its own folder and include a notes file with tempo, key, sample rate, processing choices and any unusual routing.

The sum check

Import the stems into an empty session at the same start position and compare their sum with the approved mix. Check for missing parts, level changes and cut-off tails. Nonlinear bus processing can behave differently when groups are rendered separately, so the sum may not null against the mix.

Delivering a folder this size

Large stem sets are easier to share through a delivery service than as email attachments. Check the following settings:

• Password on the delivery, and an expiry date agreed with the client. Tell the client how long the files will remain available and keep a separate backup. See how to send music privately.
• Download tracking. With files this large, "did it come through?" is a real question. A download record shows activity, but does not prove the complete file was saved. Ask for confirmation when needed.
• If the stems are a paid extra, gate them. A download that unlocks when the invoice is settled keeps the money conversation attached to the files, which is one way to follow the agreed payment schedule: how to get paid for mixing and mastering.

Frequently asked questions

What's the difference between stems and multitracks?

Stems combine related parts into groups such as drums, bass and vocals. Multitracks contain the individual tracks. Confirm which the recipient needs, since the export and checking work can differ considerably.

What format should stems be in?

Match the mix: 24-bit WAV at the session's sample rate, every file printed from bar one so they all line up. Use WAV to avoid further lossy encoding during processing.

Should stems have processing printed on them?

Processing on each group is often included, but confirm what the recipient needs. Mix-bus compression and limiting may react differently when stems are exported separately. State what was included and check the sum against the mix.

Why do all stems need to be the same length?

A common start point lets the recipient align the stems without rebuilding the timing. Export every file over the same range, including silence before its first note and space for the final effect tail.

Should I charge extra for stems?

If stems were not included in the quote, discuss the extra export, checking and upload work with the client before starting. Agree a fee and payment date where appropriate.