Remote collaboration succeeds or fails on decisions made before anyone records. Agree tempo, key, time signature, sample rate, and a reference track, then exchange consolidated stems from bar one with strict file naming and version numbers. Have the splits conversation at the start, while the song is still worth nothing and the discussion is easy.
- A shared file transfer method that does not re-encode audio
- An agreed DAW-neutral exchange format, which in practice means WAV stems
- A written note of the agreed technical settings
- A shared document or message thread for decisions
Write these down and send them to everyone before work starts:
| Setting | Why it matters |
|---|
| Tempo | Everything aligns to it; changing it later is expensive |
| Key | Determines what everyone plays and sings |
| Time signature | Obvious until someone assumes 4/4 |
| Sample rate | 44.1 or 48kHz — mixing rates causes pitch and sync errors |
| Bit depth | 24-bit for all exchange files |
| Reference track | Two or three songs that describe the target |
The reference track is the one people skip and the one that prevents the most disagreement. It communicates the intent in thirty seconds.
One person holds the canonical session. Everyone else contributes stems into it.
This is not a hierarchy, it is a technical necessity. Two people editing arrangements in parallel produces two divergent songs that have to be merged by hand.
If the collaboration is genuinely simultaneous, a browser-based DAW where the project lives in one place avoids the merge problem entirely. Veena, BandLab, and Soundtrap all work this way. Veena is desktop-browser only and has higher latency than a native DAW, so it suits writing and arranging together more than tracking live drums.
Every file:
- Starts at bar one, not where the part enters
- Ends at the same point as every other file
- Is 24-bit WAV at the agreed sample rate
- Has no master bus processing on it
- Is not clipping
Same length, same start point, every time. That is what makes a folder of files drag in and line up.
songname_v03_28_LeadVox_TakeA.wav
songname_v03_29_LeadVox_TakeB.wav
songname_v03_40_Gtr_Rhythm_L.wav
Include the song name, the version, a sort-order number, what the part is, and which take. No spaces. No characters beyond letters, numbers, and underscores.
The cost of a bad name is someone mixing the wrong take into the final master, which happens more often than it should.
Number every version and never reuse a number. v01, v02, v03.
Keep a short changelog in a shared document:
v03 - new bridge, vocal comp updated, bass re-recorded
v04 - dropped the second guitar, tempo unchanged
Two lines per version. It answers the question everyone asks two weeks later, which is what changed.
Never say the chorus feels off. Say:
1:14 - the second guitar is masking the vocal here
1:40 - the snare drops out for a bar, was that intentional?
2:05 - this is the best part of the song, it should happen earlier
Timestamped notes take the same time to write and are actionable. Playback services that let collaborators comment on the timeline make this easier, but a plain text list works fine.
Agree, in writing, before real work happens:
- Songwriting splits — who wrote the composition, in what percentage
- Master ownership — who owns the recording
- Production credit and any producer points
- Who can license the track, and whether one person can approve a sync alone
- What happens if someone leaves the project
This conversation takes twenty minutes and is straightforward while the song has no value. The same conversation after a sync placement is a dispute.
An email that everyone replies to confirming the terms is better than nothing. A short written agreement is better still.
Remote collaborations die from silence, not disagreement. Agree a cadence — a check-in every week, a deadline for each person's parts, and an agreed date to call the song finished.
The deadline for calling it finished matters as much as the others. Without one, remote tracks get revised indefinitely by people who are never in the same room to say it is done.
Related reading: best collaboration tools for musicians, how to prepare stems for a mix engineer, and songwriting splits explained.
Start making music in Veena
Free, browser-based, no downloads required.
Try Veena Free