"Stems? Deliverables? What Do They Actually Want?" - A Composer's Guide to Professional Delivery

You know that moment when you've poured your heart into a composition, the client loves it, and then they ask for "stems and deliverables in broadcast WAV format"? And you're sitting there thinking, "I made music... what's all this other stuff?"

Here's the thing - there are tons of ways professional composers handle delivery requirements. Hans Zimmer's team at Remote Control Productions has one approach, indie game composers working solo have another, and TV composers dealing with tight deadlines use yet another system. All of them work in their respective contexts.

What You'll Master in This 10-Minute Guide:

• What stems actually are (and why everyone wants them)

• The standard deliverable formats that work for 90% of projects

• A simple workflow that prevents last-minute panic

• File naming conventions that make you look professional

• Quality control checklist so nothing gets missed

Perfect for: Intermediate composers ready to work professionally but confused by technical delivery requirements
You'll need: Your DAW and a completed track to practice with
Time investment: 10 minutes to read, 30 minutes to set up your delivery workflow

What Are Stems, Really?

Okay, so everyone talks about stems like you should just know what they are. Let's fix that.

Stems are essentially organized groups of your instruments bounced as separate audio files. Think of them as the major food groups of your composition - instead of serving a complete meal, you're providing the meat, vegetables, and starches separately so the client can adjust the portions.

Here's why clients want them:

For Film/TV: The mix engineer needs to balance your music against dialogue and sound effects. If your strings are too loud during a quiet conversation, they can turn down just the strings stem without affecting your percussion.

For Games: The audio programmer might need your drums to duck when there's combat audio, or they might want to layer your melodic elements differently based on gameplay. Stems give them surgical control.

For Trailers/Commercials: They might love your track but need a version without the lead melody for voiceover, or they want to extend just the rhythmic elements for a longer cut.

Austin Wintory has talked about how for games like Journey, stems were crucial because the development team needed to create smooth transitions between different emotional states. Having separate melody, harmony, and rhythm stems let them craft those seamless musical moments that respond to player actions.

The Standard Stem Configuration That Works

Now, different composers organize stems differently. Some go super detailed with individual instrument stems, others keep it simple with just a few groups. Thomas Newman's team might deliver 20+ stems for a major film, while an indie game composer might deliver 4-6 stems for a mobile game.

If you're not sure what the client expects, here's a solid standard approach that works for most projects:

The "Big Four" Stem Setup:

1. Melodic Stem - Lead instruments, solos, main themes

2. Harmonic Stem - Pads, chords, harmonic support

3. Rhythmic Stem - Drums, percussion, rhythmic elements

4. Full Mix - Everything together (your original track)

For More Complex Projects, Add:

5. Bass Stem - Low-end elements separated for mix control

6. Effects/Sweeteners - Impacts, risers, special sounds

7. Vocals - If your track includes any vocal elements

Why this works: It gives clients meaningful control without overwhelming them with 47 different tracks they don't know how to use.

Professional Deliverable Formats

Here's where things get technical, but don't worry - it's simpler than it sounds.

The Gold Standard: 48kHz, 24-bit WAV files

Why these specs?

• 48kHz is the standard for film/TV/games (matches video frame rates)

• 24-bit gives plenty of headroom for professional mixing

• WAV is universally compatible and uncompressed

Winifred Phillips, in her book "A Composer's Guide to Game Music," emphasizes that understanding these technical requirements isn't just helpful - it's essential for working professionally. Game developers and film mixers have specific technical pipelines, and delivering in the wrong format can cause real problems.

When You Might Need Different Formats:

For Online/Streaming Content: Sometimes 44.1kHz is fine
For Podcast/Radio: They might want MP3s for file size
For Broadcast TV: They might specify "broadcast WAV" with embedded metadata

The safe approach: When in doubt, ask specifically. But if you deliver 48kHz/24-bit WAV files, you'll be right 90% of the time.

Setting Up Your Delivery Workflow

Alright, here's a workflow that scales from small indie projects to major productions. You can adapt this to whatever DAW you're using.

Step 1: Organize Your Project for Stems

Before you even start bouncing, organize your tracks into the stem groups. Most DAWs let you route multiple tracks to buses:

• Create Bus 1: "Melodic"

• Create Bus 2: "Harmonic"

• Create Bus 3: "Rhythmic"

• Create Bus 4: "Full Mix"

Route your instruments to the appropriate buses. Your violin and flute go to Melodic, your piano chords go to Harmonic, your drums go to Rhythmic. Everything also goes to Full Mix.

Step 2: Bounce Settings

Set your bounce settings once and save them as a preset:

• Format: WAV

• Sample Rate: 48kHz

• Bit Depth: 24-bit

• Dither: Off (you're staying at 24-bit)

Step 3: File Naming Convention

This is where you separate the pros from the amateurs. Use this format:

[ProjectName]_[CueName]_[StemType]_[Version]

Examples:

• SpaceGame_MainTheme_Melodic_v1.wav

• SpaceGame_MainTheme_Rhythmic_v1.wav

• SpaceGame_MainTheme_FullMix_v1.wav

Why this works: Everything sorts alphabetically, clients can instantly see what each file is, and you can track versions without confusion.

Step 4: Quality Control

Before sending anything:

• Level Check: All stems should peak around -6dB to -3dB

• Phase Check: Solo different stem combinations to make sure nothing sounds weird

• Length Check: All stems should be exactly the same length

• Listen Test: Play everything back to make sure it sounds like your original mix

Try-It-Yourself: Set Up Your First Professional Delivery

Grab a track you've been working on and practice this workflow:

1. Organize your project into the four main stem groups

2. Set up buses in your DAW for each stem type

3. Bounce a test delivery using the professional specs

4. Create a folder with proper file naming

5. Listen back to make sure everything sounds right

Time yourself - once you've done this a few times, the whole process should take less than 15 minutes for a typical track.

If This Approach Doesn't Fit You...

For Simple Projects: Some clients just want the full mix and maybe a "music only" version (without vocals or lead instruments). That's totally fine for smaller projects.

For Complex Orchestral Work: You might need more detailed stems - strings, brass, woodwinds, percussion as separate groups. The principle is the same, just more granular.

For Interactive Game Music: You might need to deliver loops, stingers, and transitions as separate elements entirely. The organization principles still apply.

For Podcast/YouTube: Often they just want the full mix in MP3 format. Don't overthink it if the project doesn't require professional film/game delivery standards.

Real-World Example: Game Music Delivery

Let's say you're delivering music for an indie adventure game. Your delivery folder might look like this:

AdventureGame_Music_Delivery_v1/
├── AdventureGame_MainMenu_FullMix_v1.wav
├── AdventureGame_MainMenu_Melodic_v1.wav
├── AdventureGame_MainMenu_Harmonic_v1.wav
├── AdventureGame_MainMenu_Rhythmic_v1.wav
├── AdventureGame_Exploration_FullMix_v1.wav
├── AdventureGame_Exploration_Melodic_v1.wav
├── AdventureGame_Exploration_Harmonic_v1.wav
├── AdventureGame_Exploration_Rhythmic_v1.wav
└── Delivery_Notes.txt

The Delivery_Notes.txt file might include:

• Tempo information

• Key signatures

• Any special technical notes

• Loop points for game tracks

• Brief description of musical intent

Professional Communication

When you deliver stems, include a brief note explaining what you've provided. Something like:

"Hi [Client Name], attached are the stems for [Project Name]. I've provided melodic, harmonic, and rhythmic stems as discussed, plus the full mix. All files are 48kHz/24-bit WAV format. The melodic stem contains the main themes and lead instruments, harmonic has the chord progressions and pads, and rhythmic has all percussion elements. Let me know if you need any adjustments or have questions about the delivery!"

This shows you understand what you're providing and why it's organized this way.

What's Next?

Now that you understand stems and deliverables, you might want to dive deeper into:

• Professional project organization - how to set up your DAW sessions for easy stem creation

• Client communication - how to discuss technical requirements professionally

• Advanced delivery formats - surround sound, immersive audio, and platform-specific requirements

The key thing is that professional delivery isn't about being complicated - it's about being organized and predictable. When clients know they can count on you for clean, properly formatted deliveries, they'll keep coming back.

Your Delivery Workflow Challenge

This week, take one of your existing tracks and practice the professional delivery workflow:

1. Set up proper stem organization

2. Bounce everything with professional specs

3. Name files with the proper convention

4. Create a delivery folder

5. Write brief delivery notes

Time the whole process and see how streamlined you can make it. Professional composers often have this down to a 10-15 minute routine, regardless of project complexity.

Once you've got this workflow down, delivering professional stems becomes as automatic as saving your project file. And that confidence shows when you're communicating with clients about technical requirements.

Drop a comment below if you try this workflow - I'd love to hear about any challenges you run into or improvements you discover along the way!