The project is done. The mix is approved, the invoice is paid, and you have moved on to the next session. Then the email lands: “Hey, can you send me the stems and the project file? My friend wants to take a look at it.” Suddenly you are facing a question no one prepared you for: how to handle delivering stems to clients without giving away the work that makes your mixes sound like yours.
Your stomach drops a little. That session represents hours of routing, processing, and decisions that are yours. Handing it over feels like giving away the recipe. But refusing outright feels petty, and the client technically paid you. So what is the right move?
Delivering stems to clients is one of those gray areas that every working engineer hits eventually, and almost no one talks about it before it happens to them. There is no industry rulebook, which is exactly why it causes so much friction. This guide walks through when to say yes, what to charge, how to protect your credit, and which files you should never hand over no matter what.
Stems Are Not the Same as Your Session File
Before anything else, get the terminology straight, because clients almost never do.
A stem is a printed audio bounce of a single instrument or group: the full vocal bus as one WAV, all the drums summed to one file, the guitars as another. Stems carry your processing baked in. They are flat, finished, and ready to drop into another session. A request for stems is reasonable and common.
A project file is something else entirely. That is your actual DAW session: every plugin, every automation lane, every routing choice, the whole architecture of how you built the mix. When a client asks for “the project file” or “the session,” they are asking for the blueprint, not the building.
These two requests deserve two different answers. You can be generous with one and firm on the other. Most of the conflict around delivering stems to clients comes from engineers treating both requests as the same thing, then either oversharing or overreacting.
Why Clients Ask in the First Place
Understanding the reason behind the request makes the conversation easier. Clients ask for stems for a handful of predictable reasons.
Sometimes they want stems for a remix or a live performance backing track. Sometimes a sync placement or a label requires deliverable stems as part of the package. Occasionally a client wants to shop the mix to another engineer for a second opinion, which stings but is their right. And sometimes they simply heard the word “stems” somewhere and assume they are supposed to have them.
Ask before you assume. A quick “What are you planning to use them for?” tells you whether this is a routine remix request or someone trying to take your work to a competitor.
When to Say Yes to Delivering Stems to Clients
In most cases, printed stems are fair game. The client paid for a finished product, and stems are a reasonable part of that product for many genres.
If you mix pop, hip-hop, electronic, or anything with a remix culture, stems are basically expected. Labels build entire release cycles around remix packages. A client who wants stems for that purpose is not trying to cut you out. They are doing normal music business, and being difficult about it will cost you the relationship and the referral.
So the default answer for clean, printed stems is usually yes. The real questions are what you charge, what you keep, and how you protect your name on the work.
Build Stem Pricing Into Your Quote Upfront
The cleanest way to handle delivering stems to clients is to decide the policy before the project starts, not after the request arrives.
Some engineers include a basic stem set (drums, bass, music, lead vocal, background vocals) in their standard package. Others treat stems as a separate line item billed at an hourly rate, because printing and labeling a proper stem set takes real time. Both approaches work. What does not work is having no policy and getting blindsided by the request after you have already been paid.
State it in your quote. Something like: “Final delivery includes the stereo mix, an instrumental, and an acapella. Full instrument stems are available for an additional fee.” Now the client knows the menu before they order, and you never have to have an awkward money conversation at the end.
Charge for Stems Requested After the Fact
Creating stems for a fee is completely different from being expected to produce them for free after a project is closed. If a client comes back weeks later asking for a full stem set you never quoted, you are within your rights to bill for that work.
Pulling up an archived session, checking it still opens correctly, printing each group, labeling everything, and packaging it is an hour of work minimum. That hour has value. Quote it the same way you would quote any other task. Most reasonable clients understand that asking for new work means paying for new work, especially when you frame it plainly: “Happy to put those together. Stem prep runs X, and I can have them to you by Thursday.”
When to Say No, or At Least Slow Down
Not every request deserves an instant yes. The project file is where you should hold the line.
Handing over your full DAW session means handing over your entire approach: your bus structure, your plugin chains, your settings, the thing that makes your mixes sound like yours. Once a client has that, they or another engineer can reverse-engineer your work, alter it, and still leave your name attached to the result. That is a real risk to your reputation, not just your pride.
The standard professional position is simple. You deliver printed stems. You do not deliver your master session files unless that was negotiated, priced, and agreed in writing before the project began. There is nothing precious or “holier than thou” about this. It is the same reason a developer ships the app, not their entire codebase, with every contract.
Protect Your Credit Before the Files Leave
The biggest danger in delivering stems to clients is not the stems themselves. It is what happens after, when someone else touches the work and your name still rides along.
Before stems leave your drive, get the credit terms in writing. Your original work should be credited as mixed by you. Any further changes someone makes are their work, credited separately as additional production or additional engineering. And you keep the right to remove your credit entirely if a third party remixes the stems into something you would not want your name on.
This is not paranoia. A botched remix built on your stems, released under your mix credit, can do quiet damage to how your work sounds to the next person who hears it. Spell out the terms once and you never have to chase the problem later. If you do not already have these clauses, your mixing contract is the place to add them.
The Second-Opinion Request Stings, But Handle It Anyway
One version of the stem request is harder to swallow than the rest: the client who wants your stems so a different engineer can take a pass at the mix. It feels like a rejection, and your instinct will be to dig in.
Resist that instinct. The client paid for the work, and they are allowed to seek another opinion, the same way someone can take a second look at a contractor’s estimate. Refusing makes you look insecure and burns a relationship that might still send you referrals. Hand over clean printed stems, keep your session file, lock in your credit terms, and let the work speak for itself. More often than not, the client comes back with a new appreciation for what you did once they hear someone else struggle with the same source. Professional grace in that moment is worth more than winning the argument.
What to Always Keep for Yourself
Even when you say yes to stems, there are things that stay with you.
Keep your master session file. Keep your custom chains and templates. Keep any production elements you actually created rather than mixed, like a sound design layer or a re-amped part you built from scratch. Those are yours, and clients have no automatic claim to them unless you agreed otherwise.
Also keep an archived copy of everything you deliver. The moment you hand off stems, save a dated copy of exactly what left your hands. If a dispute ever comes up about what was delivered or in what state, you want a clear record. This habit takes seconds and has saved more than one engineer from a he-said-she-said argument months down the line.
Back Up Sessions So You Can Actually Honor Requests
The flip side of keeping your work is being able to find it. Plenty of engineers say no to stem requests not on principle but because they already deleted the session and cannot face admitting it.
Keep a real backup system. Archive completed sessions to an external drive or cloud storage, organized by client and date, so that when a request comes in six months later you can actually fulfill it. Being the engineer who can recall any past project is a quiet competitive advantage. Clients remember who made their life easy.
Delivering Stems to Clients Without Looking Sloppy
Once you have decided what to send, the delivery itself is worth doing well. A sloppy handoff undercuts the professional impression you spent the whole project building.
Label every stem clearly and consistently. “SongTitle_Drums_48k24bit.wav” tells the next person exactly what they have. “audio 7 final.wav” tells them nothing and makes you look careless. Match the sample rate and bit depth of the original session, and confirm with the client what format they actually need before you export the whole set.
The way files travel also leaves an impression. Sending a chaotic zip through a random link feels different from sending an organized, clearly named set. A dedicated tool like session.trackbloom.com gives clients an upload link where files arrive grouped by instrument, and the same kind of organized structure makes your outbound deliveries look just as intentional. When the whole exchange feels tidy, clients read that as professionalism, and professionalism is what gets you rehired.
Send a Short Delivery Note With the Stems
Do not just drop a folder and disappear. Include a brief note that lists what is in the package, the format, and any usage terms you agreed on.
A simple message works: “Here are the full stems as discussed, printed at 48k/24-bit, grouped by instrument. These are mixed by me. Any further edits should be credited as additional engineering. Let me know if you need a different format.” That note sets expectations, documents the terms, and closes the loop cleanly. It also gives you a written record of exactly what you sent and on what basis.
Turn the Stem Request Into a Better Relationship
Here is the reframe most engineers miss. A stem request is not an attack on your work. It is a sign the client is doing something with the music, which is exactly what you want.
A client building a remix package, prepping for a live show, or chasing a sync placement is a client whose career is moving. When their career moves, they hire more, refer more, and remember the engineer who handled their requests like a professional instead of a gatekeeper. Saying yes the right way, with clear pricing and clean credit terms, turns a tense moment into a reason they keep coming back.
So set your policy now, before the next request lands. Decide what is included, what costs extra, what you will never hand over, and how you protect your name. Write it into your quote and your contract. Then when the email arrives asking for the stems, you will not feel that drop in your stomach. You will already know exactly what to say.