Collaborate on music online — files, feedback, and splits in one place

What online music collaboration actually requires

Sending files back and forth is the easy part. What gets complicated is everything around the file: knowing which version is current, collecting feedback that's actually useful, keeping collaborators aligned on who owns what percentage, and making sure the right person has access to the right files without handing over everything.

Most musicians stitch this together from tools that weren't built for it. Dropbox for storage. WhatsApp or email for feedback. A Google Doc for the split sheet. Maybe a Notion page for project notes. None of these talk to each other. When a new version appears, you're back to manually notifying everyone, hoping they find the right file, and chasing responses.

The version problem

The most common point of failure in any remote collaboration is version control. You upload a mix. Your producer tweaks the low end and sends back "v2". You adjust the vocals and bounce "v3". Three weeks later, someone submits the track — and it's the wrong one. This isn't carelessness; it's what happens when versions live in a shared folder without any structure.

The feedback problem

Audio feedback sent over text is hard to act on. "The chorus feels a bit flat around two minutes" is a guess. "The snare is too loud" describes an opinion without pinpointing where. Feedback that lives in a separate thread from the file it refers to gets lost — or remembered differently by different people.

The split problem

The split conversation tends to happen at the worst possible time — after the track is finished, when everyone has opinions and leverage. Starting that conversation before the session, and keeping a record of what was agreed, changes the dynamic entirely.

How TYFRA Vault handles online collaboration

Vault gives every collaboration a single location: files, versions, feedback, and split documentation all in one project. You invite collaborators with specific roles and permissions. Everyone works from the same source of truth.

Upload your files once

Add your tracks, stems, or reference files to a Vault Project. Files are stored in their original format — WAV, FLAC, AIFF, or MP3, up to 150MB each — with no re-encoding. Metadata (BPM, key, ISRC, moods, instruments) is stored alongside the file and doesn't need to be re-entered elsewhere.

Add collaborators with role-based access

Invite producers, songwriters, engineers, vocalists — any collaborator — with specific roles. Permissions are set per collaborator per track: you control who can download, who can comment, and who can see split details for each track they can access. Share links can use their own rules for listen-only or download when you send audio outside the project.

Leave feedback directly on the audio

Collaborators can leave timestamped comments at specific points in a track — "the reverb tail on the snare at 1:42 is too long", rather than "something around the chorus". Comments can be tied to a specific revision, marked as resolved when addressed, or flagged for follow-up. They're visible to everyone with access to the project, not buried in a message thread.

Track every version

Vault uses two version systems. Track Revisions cover production iterations — when you bounce a new mix, it becomes v2 of the same track, and v1 is still accessible. Track Versions cover distinct variants: the instrumental, the radio edit, the remix. Every version is labelled and retrievable. When you share something, you share a specific revision — there's no ambiguity about which file your collaborator received.

Document splits before you release

Vault's split management handles publishing and mechanical royalties separately — because the person who produced the track and the person who wrote the lyrics often have different ownership structures. You set the percentages, send a proposal, and all collaborators receive a notification to accept or reject. Nothing is finalised until everyone has agreed. Every decision is logged in an audit trail.

Working across time zones

Remote collaboration often means asynchronous work — you're in London, your producer is in Los Angeles, your mix engineer is in Berlin. Vault's project structure is designed for this. You upload a new revision and leave a comment. Your collaborators log in when they wake up, see the update, listen in context, and respond. Nobody needs to be on a call for the project to move forward.

What happens after the collaboration is finished

When the track is done, everything in Vault stays: the files, the version history, the feedback thread, the split documentation. If a dispute ever arises — about which version was approved, what was agreed on splits, who delivered what — the record is there. The track also flows directly into the rest of TYFRA without re-uploading: it can be sent to DJs via Promo, attached to a contract in Contracts, or tracked in Finance.

Who it works for

Vault's collaboration tools suit any situation where more than one person is working on a track remotely:

Artists working with remote producers — share vocals or stems, receive a mixed version back, give feedback without a studio session.

Producers collaborating with vocalists or songwriters — keep the project files organised, track what's been delivered, document who contributed what.

Songwriters pitching to labels — share demos with clear version labels, collect feedback from A&R without losing the context.

Small labels managing multiple artists — give each artist access to their own material while keeping roster-level oversight.

Related on TYFRA