Collaborate remotely on tracks: file sharing, session formats, stems and splits agreed up front

You met a vocalist on a forum, a drummer sent you a loop from another time zone, and now there is a half-finished track with three people's fingerprints on it. Remote collaboration is normal now, and most of the ways it goes wrong are boring: missing files, a session nobody else can open, stems that don't line up, and a conversation about money that happens after the song is already doing well.

This guide puts those four things in order. It is a practical walkthrough, not legal advice, and the law quoted is American; check your own country's rules, and everything is as we read it on 24 Oct 2026.

Step 1: agree the basics before anyone opens a DAW

Before the first file moves, settle three things in a short message thread everyone can scroll back to:

• Tempo, key and sample rate. Pick one sample rate and bit depth for the project and say it out loud. It saves converting files later.
• Who holds the master session. One person should own the "real" project. Everyone else sends parts into it. Two people editing two copies of the same session is how you lose a week.
• A naming rule. Something like songname_part_initials_v03.wav. Boring, and it saves hours.

Then talk about splits, which gets its own step below. Do it now, while the song is worth nothing and nobody's feelings are on the line.

Step 2: choose how files move

There is no single right tool. What matters is that everyone knows where the current version lives.

Shared cloud folders suit ongoing projects: one folder, everyone syncs, the folder is the source of truth. The risk is sync conflicts when two people save the same file at once, which is another reason one person holds the master session.

Transfer links suit one-off handoffs, but check the limits before you rely on one. WeTransfer's plan limits page, for example, says its free plan allows up to 10 transfers in a rolling 30-day window, with 3 GB of data in that window. A full multitrack at 24-bit can eat that quickly, and a link that has expired is not an archive.

Whatever you use, keep your own copy. A shared folder someone else owns can disappear when they stop paying for it. Our guide to backing up your music projects covers a 3-2-1 routine that works for collaborative sessions too.

Step 3: if you share a session, make it self-contained

If everyone uses the same DAW, sending the project itself is tempting, and it can work, but only if the project carries its audio with it.

Most DAW projects don't store audio inside the project file; they point to files on disk. Ableton's Live 12 manual explains that a Set references external files, and that Collect All and Save copies those files into the Project folder, so the Set no longer depends on a file's original path. Skip that step and your collaborator opens a session full of missing samples. Other DAWs have their own version of this (often called "consolidate", "save as with media" or similar); find it and use it every time.

Two more things sharing a session doesn't solve:

• Plug-ins. If your collaborator doesn't own the same instruments and effects, those tracks open silent or dry. Print (render) anything that depends on a third-party plug-in to audio before sending, and keep the MIDI alongside it.
• Versions. A project saved in a newer version of a DAW may not open in an older one. Agree a version, or send audio.

Moving between different DAWs

AAF and OMF are interchange formats meant to carry tracks, clip positions and some automation from one DAW to another. They are useful but unreliable. The Ardour manual is blunt about it: both standards have specifications so complex or incomplete that different DAWs support them "only partially, differently, or not at all". Ardour itself says its AAF import includes fades, volume automation, pan and multichannel tracks, which tells you what a good import looks like. Treat any AAF transfer as a starting point and check it against a reference bounce.

For most indie collaborations across different DAWs, the dependable answer is plain audio: stems.

Step 4: export stems that line up

Stems (separate audio files for each track or group of tracks, such as drums, bass and vocals) are the universal language of remote work. The rule that matters most: every stem starts at the same point and runs the same length, so your collaborator can drop them at bar 1 and they line up.

Ableton's manual shows how this works in practice. In the export dialog, All Individual Tracks renders "the post-fader signal at the output of each individual track", including group tracks, return tracks and the main output, as separate files. Render Start and Render Length set where rendering begins and how long the file is, and by default cover the whole Set. Leave them covering the whole song and every stem shares a start point.

A few habits that save back-and-forth:

• Match the project's format. Live offers WAV, AIFF and FLAC, at 16, 24 or 32-bit, and lets you pick the sample rate. Export at the rate and depth agreed in Step 1. 24-bit WAV is a safe default for most handoffs.
• Turn normalising off. Ableton notes that its Normalize option raises or lowers gain so the highest peak hits maximum headroom. That is fine for one file and wrong for a set of stems, because each stem gets a different gain change and your balance is gone.
• Say whether effects are printed. Post-fader stems include your processing and fader moves. If the next person is mixing, they may want dry stems plus a reference mix. Ask.
• Include a reference bounce of the full mix at the same length, and a text file with the tempo, key, sample rate and any tempo changes.
• Leave tails. Let reverb and delay ring out past the last note so nothing is cut off.

If you are sending stems to a mixing or mastering service rather than a person, our guide to prepping stems for AI mixing and mastering goes deeper on headroom and naming.

Step 5: agree the splits up front, in writing

This is the step people skip, and it is the one that costs the most later.

Why it matters legally

US copyright law defines a joint work in 17 U.S.C. § 101 as "a work prepared by two or more authors with the intention that their contributions be merged into inseparable or interdependent parts of a unitary whole." Remote collaborators writing one song together usually look exactly like that. And the US Copyright Office's general FAQ says copyright exists "from the moment the work is created", with registration generally voluntary. In other words, ownership questions exist from the first session, whether or not anyone wrote anything down.

What the default rules give each co-author, and how money flows, depends on the country and the facts. That uncertainty is the point: a short written agreement replaces a default nobody chose.

What to write down

Keep two things separate, because they are separate copyrights:

• The song (composition): who wrote melody, lyrics and harmony, and what percentage each person gets. This is the split sheet.
• The recording (master): who paid for and owns the recorded audio, and whether any producer gets a fee or points.

For each, write names, legal names, roles, percentages that add up to 100, PRO and publisher details if they have them, the date, and everyone's sign-off. A shared document and an email "I agree" from each person is far better than nothing. Our guide to ISRCs, ISWCs and split sheets covers what goes on a split sheet and when to register the codes, and producer agreements explained covers fees and points on the master side.

Also agree what happens if someone drops out, if a part gets replaced, or if the song is pitched for sync. "We'll revisit if the track changes a lot" is a fine clause; silence is not.

What we think

Remote tools have made it easy to start a collaboration and no easier to finish one fairly. The technical problems in this guide have dull, reliable fixes: collect your files, print your plug-ins, export stems from the same start point. The human problem doesn't fix itself.

Our view: agree splits before the song exists, not after it succeeds. Equal splits by default are a reasonable starting point for a small group writing from scratch, and anyone who wants a different number should say so on day one, when the conversation is cheap. Artists-first means the session vocalist and the person who wrote the hook get named and paid as clearly as whoever owns the project file.

We'd also like DAWs to treat credits as part of the session, so that who played and who wrote what travels with the project and the stems instead of living in a chat thread someone will lose. Until then, a text file in the project folder and a signed split sheet will do the job.