On this page
In short
- Match the format to the moment: MP3 for reviewing revisions, WAV for approval and mastering.
- Name files with song, type, version and date, never "final".
- One address per song that stays valid for the whole project, plus a message that says what changed.
The DAW is half the job. The other half is getting the mix to the client so they listen right away, without asking you which one is the latest.
A badly delivered mix creates revisions on old files. A well delivered one gets approved sooner.
Keep transfer links for one-off sends
Transfer services are fine for a single package. For ongoing client work they have three practical limits.
- Links expire. On free plans a transfer stays up for a few days, and a client who opens the email late finds a dead link.
- Usage is capped. WeTransfer's free plan allows up to 10 transfers or 3 GB every 30 days, according to its plan limits page.
- No player, no history. The client downloads, unzips and plays it on laptop speakers. By the third revision nobody knows which one was approved.
Match the format to the moment
Separate listening from technical delivery. WAV matters when the decision is technical.
| Moment | Format | Why |
|---|---|---|
| Review | MP3 320 kbps or AAC 256 | Opens anywhere, streams on mobile |
| Approval | Session WAV (24-bit, 48 kHz) | The client hears what goes to mastering |
| Mastering | WAV, no limiter, with headroom | The mastering engineer has room |
| Release | Master WAV, instrumental, a cappella | Needed for sync, live shows, remixes |
Name files so they make sense unopened
The name states song, artist, type, version and date, always in the same order.
TidesSong_MayaLinArtist_MixType_v03Version_260927Date YYMMDD.wavThe full scheme is in our guide on organizing song versions.
Use an address that stays valid for the whole project
The file lives somewhere stable for the whole project, with one address per song. If every revision gets a new link, the nearly identical files come back.
backstg.io/l/8Kd2fQCopyActive for one year · listen only
Write a short, complete delivery message
The message matters as much as the file. In a few lines the client knows what changed, how to listen, when notes are due and how many revisions are left.
Hi Mark, here is v3 of "Tides". Compared to v2: vocal up in the chorus, less reverb on the snare, intro two bars shorter. Please listen on headphones and in the car, then send notes by Friday with timestamps (e.g. 1:12, guitar covers the vocal). Two revisions are included: this is the second.
Always ask for minute, second and a concrete verb: raise, lower, remove. More in giving and getting mix feedback.
Record what was approved
Approval is written down and tied to a specific version. "Sounds good" in a voice note isn't enough when, two months later, the distributor asks for the file.
FAQ
Should I send a mix as WAV or MP3?
For revisions a 320 kbps MP3 is enough and opens anywhere. Use WAV for final approval and for mastering.
What's the best way to send large audio files for free?
A shared cloud folder has no link expiry and is free within the base storage. For revisions, a built-in player saves the client from downloading anything.
How many mix revisions should I include?
It depends on your rates: state it before you start and repeat it with each delivery. Two or three rounds is common; see online mixing and mastering.