Stem file structure guide — how to name, organise, and deliver stems properly

What stems are — and what they are not

Stems in the professional sense refers to grouped submixes of individual track elements: all the drums mixed together as one stereo file, all the synths mixed together as another, all the vocals as a third. Stems give a mix engineer or remixer control over major elements of the track without access to every individual sound.

Multitracks are the individual component files — the kick drum, the snare, the hi-hat, the bass, each melody synth, each vocal layer — exported separately with no summing between elements. Multitracks give the maximum flexibility for mixing or remixing but require the most organisation to manage.

Bounces or exports are typically the full stereo mix or individual track groups exported from the final session, used for mastering or sync consideration.

The terminology is used inconsistently in the industry — "stems" is often used to mean multitracks in casual conversation. When delivering, be explicit about what you are providing: individual tracks, grouped submixes, or both.

Naming conventions — the single most important practice

Good stem naming answers three questions immediately: what is this sound, where does it sit in the arrangement, and which version of the track does it belong to.

[TrackTitle]_[StemGroup]_[StemName]_[Version].[format]

DarkMatter_Drums_Kick.wav
DarkMatter_Drums_Snare.wav
DarkMatter_Drums_Hats.wav
DarkMatter_Bass_Synth.wav
DarkMatter_Synths_Pad.wav
DarkMatter_Synths_Lead.wav
DarkMatter_Vocals_Lead.wav
DarkMatter_Vocals_Harmony_L.wav
DarkMatter_Vocals_Harmony_R.wav
DarkMatter_FX_Riser_Breakdown.wav

Stem grouping — how to divide a track

The right grouping depends on the purpose of the delivery.

Technical specifications for stem delivery

Format: WAV at the session's native resolution (24-bit / 44.1 or 48 kHz is standard). Never deliver MP3 stems — any subsequent processing compounds the quality loss from the original encoding.

Level: Export stems at a level that preserves headroom. Stems should not clip at 0 dBFS. A peak of -6 to -3 dBFS is a typical target for mix-ready stems. Confirm with your recipient if they have specific level requirements.

Length: All stems should be the same length — start at bar 1, beat 1, end at the same point. A mixing engineer cannot align stems of different lengths without manual adjustment. Some engineers prefer stems that include any reverb or delay tails beyond the arrangement's end point — confirm preference.

Phase coherence: When stems are summed together in a mixing session, the result should be identical to the original mix (minus any stems-bus processing applied post-summing). If your stems do not sum correctly, check for phase issues in the session before exporting.

Solo export: Export each stem channel or group in solo to avoid bleedthrough from other elements. Some DAWs offer a batch stem export; verify the output is correct for each stem.

Folder structure for a stem pack

Organise the stem pack folder clearly. A typical structure:

DarkMatter_StemPack_v1/
├── DarkMatter_Mix_v1.wav          (the full stereo mix as reference)
├── DarkMatter_Instrumental_v1.wav (if applicable)
├── Drums/
│   ├── DarkMatter_Drums_Kick.wav
│   ├── DarkMatter_Drums_Snare.wav
│   └── DarkMatter_Drums_Hats.wav
├── Bass/
│   └── DarkMatter_Bass_Synth.wav
├── Synths/
│   ├── DarkMatter_Synths_Pad.wav
│   └── DarkMatter_Synths_Lead.wav
├── Vocals/
│   ├── DarkMatter_Vocals_Lead.wav
│   └── DarkMatter_Vocals_Harmony.wav
└── FX/
    └── DarkMatter_FX_Riser.wav

Include a text file (README.txt or session_notes.txt) at the root of the folder with:

• Track title and ISRC
• BPM and key
• Session sample rate and bit depth
• Any notes the recipient needs (specific stem group conventions, effects tails, anything non-standard)

Storing stems in TYFRA Vault

TYFRA Vault's Project structure is well suited to stem storage. Create a Project for the track and use color-coded folders to replicate the stem group structure — Drums, Bass, Synths, Vocals, FX — within the project. Each stem is uploaded as an individual track within its folder.

Track Revisions handle iteration — if you re-export the drums after a session change, the new export becomes v2 of the drum stem rather than a separate file with a new name. The original v1 is retained.

Share links generated for a stem project point to the specific revision at the time of sharing. Your mix engineer always knows exactly which stems they received, even if you continue working on the project and upload subsequent revisions.

Metadata fields — BPM, key, instruments — can be applied to each stem individually so the context travels with the file.

Related on TYFRA