Music file sharing: how to send tracks without wrecking them
Music file sharing goes wrong for a boring reason. Audio at full quality is enormous, email was built for memos, and the gap between those two facts is where your mix ends up as a 128kbps MP3 that the mastering engineer politely calls "a bit crunchy".
The fix is not one tool. It is picking the right pipe for who is on the other end, because a collaborator who needs your stems and an A&R who needs to hear thirty seconds want completely different things from you.
Email will not carry a WAV, and the maths is not close
A CD-quality stereo WAV runs at 44.1kHz, 16-bit, two channels. That is 1,411 kilobits per second, which works out at roughly 10.1MB for every minute of audio.
So a three-and-a-half-minute track is about 35MB before you have touched it. Gmail caps personal accounts at 25MB, and Outlook.com stops at 25MB for a direct attachment too, though it will hand you a 2GB OneDrive link instead if you let it. Master at 24-bit, 96kHz, and that same track is well past 100MB.
Now send someone the full stem folder. Twelve tracks at 35MB each and you are sending 400MB of audio to a person whose inbox will not take one of them.
This is why people compress, and compression is where the damage happens. An MP3 sent for feedback is fine. An MP3 sent to someone who has to mix, master or licence it is not, because they cannot get back what you threw away.
Match the method to the person on the other end
The collaborator who needs the actual files
Say your drummer has tracked six takes and you need the raw multitrack back for the mix. That is a folder, not a file, and it needs to arrive lossless with the folder structure intact.
Cloud storage is the right answer here. Dropbox, Google Drive or OneDrive, one shared folder per project, named by song and date, with a plain text file inside listing the tempo, the key and the sample rate. Zipping first keeps the structure but stops anyone previewing what is inside, so I only zip when I know the recipient is downloading the lot anyway. If you are going the zip route, we have written up sending zip files properly.
WeTransfer works too for a one-off, and its free tier is tighter than people remember: 10 transfers or 3GB total in any rolling 30-day window. Two stem folders and you have spent most of the month.
The person who needs to give you notes
Different job entirely. A label contact, a client or a bandmate reviewing a rough mix does not want a 400MB download. They want to press play and tell you the snare is too loud at 1:42.
Private streaming links are built for exactly this. Highnote, which Dropbox backs, hosts a track in a private space and auto-timestamps every comment to the moment it was left, so feedback arrives attached to the bar it refers to rather than in a WhatsApp message saying "the bit near the end". A private SoundCloud link does a simpler version of the same thing for free.
The thing to check before you commit to one is whether it tells you the track was actually played. Sending a mix and hearing nothing for four days is a specific kind of misery, and a playback notification is the difference between chasing and knowing.
The person who just needs to hear it
A friend, or someone you met at a gig who asked what you sound like. Send a 320kbps MP3 and stop thinking about it. It fits in an email, it plays on anything, and nobody is going to master from it.
The other thing people mean by music file sharing
Search this phrase and half the results are still shaped by the Napster era, when music file sharing meant peer-to-peer networks and swapping ripped albums with strangers.
That world has mostly gone, and not because anyone won an argument about ethics. Streaming made it easier to press play than to torrent, which was always the actual battle. If you have landed here looking for a way to distribute music you do not own the rights to, I am not the person to help, and the tools above will not solve that problem either. If you own your masters, and you have cleared whatever sits underneath them, including the composition and any samples, distribution through the usual services is both simpler and legal.
When the audio is only half of what you are sending
There is a moment in this that is not about audio at all. You send the track, and alongside it goes a sync pitch, a split sheet, a licence, a one-sheet, a rate card. The music arrives fine. The document does not get read.
That is the problem I actually work on. LiveDocument attaches a recorded video walkthrough to a PDF or an image and shares the whole thing as a single link with page-level analytics, so a licence or a pitch doc arrives with your voice on it instead of arriving silent. It does not host audio, so it is no use for the music itself, and for anything where the file is the deliverable you want the storage and streaming options above.
I mention it because the split trips people up. Music has decent tooling for this now, and the paperwork that travels alongside it mostly does not.
Common questions
Should I send WAV or MP3?
WAV if anyone downstream is going to mix, master or licence the track. MP3 at 320kbps if they are just listening or giving notes. Sending a lossy file to a mastering engineer wastes both your time.
Can I tell if someone listened to a track I sent?
Only if the platform reports it. A file link in an email tells you nothing. Private streaming platforms often include playback notifications, which is worth checking before you pick one.
If the thing you keep sending into silence is a document rather than a track, that is what I built LiveDocument for.
About the Author
Cameron JamesCameron is the founder of LiveDocument. He writes about sharing documents, PDFs, decks and contracts, and why pairing a video walkthrough with a document beats sending it cold.