How to deliver masters, instrumentals and stems to clients

An artist opens the delivery and sees three files called “final”. One is the master, one is an earlier revision and one is the instrumental. You know the difference because you exported them. The person preparing the release may not, especially after the files are forwarded to a label or saved into another folder.

A useful audio handoff identifies the version, purpose and technical details of each export. Put the release files beside a short set of notes, then check the downloads before sending the link. This guide uses a fictional track called Loose Ends. Follow the agreed delivery specification for your actual project rather than treating its example package as a technical standard.

Confirm the release package before exporting

List what the artist or label requested: master, instrumental, any alternate versions, stems and notes. Confirm the required format, sample rate, bit depth and naming convention with the recipient. A neatly presented delivery cannot resolve a mismatch in those requirements after the exports have already been made.

Decide which session material belongs in the handoff. Stems, a full session export and editable project files are different deliverables. Include only what you agreed to supply, and document dependencies when another engineer is expected to open a session. Keep your own project archive and revision history separately from the files intended for release.

Use names that identify purpose and version

Choose one pattern and apply it across the package. A fictional delivery might contain loose-ends-master-v2.wav, loose-ends-instrumental-v2.wav, loose-ends-stems-v2.zip and loose-ends-session-notes.pdf. The version marker ties the master and instrumental to the same approved revision.

If the recipient needs two versions, make the distinction visible in the filenames and notes. If only one is approved for use, remove superseded exports from the delivery. A name like “latest” becomes ambiguous after the next revision; a version number remains useful when the recipient compares files already on their computer.

Check the stems archive and write the notes

Open your prepared ZIP and check its contents before attaching it. Confirm that the files match the agreed export specification and that the naming and grouping make sense to the next engineer. Check the exported files in your usual audio tools. Keep any instructions needed to use them in a readme inside the archive or in the attached notes.

• Identify the approved revision and the purpose of each export.
• Record sample rate, bit depth and other agreed technical details.
• List the stems included and explain any deliberate exclusions.
• Give a contact for questions and state the download window.

The delivery message can stay short: “Release files for Loose Ends v2. The master and instrumental match this revision; the ZIP contains the agreed stems. Start with the session notes for export details and save the originals before the link expires.” Put the detailed record in the notes so it travels with the downloaded package.

Combine exports from their existing locations

In SentIt, upload the WAVs from your computer, attach a stems ZIP from Dropbox and add an exported notes PDF from Google Drive. Connected files do not use SentIt storage; provider availability and daily transfer allowances still apply. Computer uploads can be up to 1 GB each on Free or 5 GB on Premium, within your available storage allowance.

One delivery can hold up to 100 files. A prepared stems ZIP keeps a related collection together as one attachment. For multiple files, Download all offers a single ZIP up to 4 GB, subject to daily ZIP request and transfer limits. Beyond those limits, use individual downloads or the file list. Keep the notes easy to find alongside the audio and archives.

Explain browser listening and original downloads

Clients can open Preview and listen to compatible audio using browser controls when JavaScript is enabled. Supported file types include WAV, MP3 and FLAC, but whether a particular file plays depends on its encoding and the recipient’s browser. If playback fails, they can download the original and open it in suitable software.

Previewing an attached WAV does not open the stems inside a ZIP. Clients download that archive to use its contents. SentIt does not provide time-coded comments, automatic version history or mix comparison. Use your usual conversation for feedback, and identify the relevant filename and revision in that conversation so everyone knows which export is being discussed.

Deliver under your studio’s domain

Premium supports one verified custom subdomain for your delivery links. Connect a subdomain you own in Settings and follow the DNS instructions before sending links under the studio’s domain. The original SentIt address stays usable. This gives the release package a familiar address alongside your logo and accent colour; normal access and delivery limits continue to apply.

Keep revisions and the download window clear

When a correction is ready, add the revised export and remove the one clients should stop using. Attachments change the live delivery immediately; save title and message changes to apply them. The active URL stays the same. Changed Drive or Dropbox sources may need refreshing or reattaching because the delivery does not automatically sync your working folder. Update the stems archive if the revision affects its contents.

Tell the recipient what changed and which saved files to replace. Free links last up to 7 days from first publication. Premium offers a future date or no scheduled expiry while your Premium subscription continues, plus your studio logo, accent colour and automatic, light or dark delivery pages. Keep backups and ask clients to save their own copies. Anyone with the active link can access the delivery, without a recipient account.

See the fictional release package on our delivery page for mix and audio engineers. Check current plans and limits, then use the guide to updating shared files when a last revision arrives after the handoff.