Store music projects online — one permanent home for every track, stem, and session
Store music projects online with permanent cloud storage built for music — versions, metadata, collaborators, and workflow integration all in one place. Not a folder. A system.
Every music project produces more files than expected. The session starts with a reference track and an initial loop. By the time the track is finished, there are stems, multiple mix revisions, a master, an instrumental, artwork files, a press release, and a split document. That is a significant amount of material for a single track — multiply it across an EP, an album, a year of releases, and the storage and organisation problem becomes substantial.
Storing music projects online — in a cloud system rather than on a local hard drive — solves a specific set of problems: backup without manual action, access from any device, sharing with collaborators without copying files to multiple locations, and a single source of truth that persists regardless of which machine was last used in the session.
This page covers what good online music project storage looks like, what distinguishes a music-specific system from generic cloud storage, and how TYFRA Vault structures project storage across a growing catalog. Companion reads: managing music projects, organising music files, and the Vault hub.
What "storing a music project" actually means
When a musician says they want to store a music project online, they are usually describing several different storage needs at once:
Active session backup. The DAW session and its associated files — samples, plugin states, audio recordings — backed up continuously during production so that a hard drive failure does not lose the session. This is handled by DAW-level backup tools (Logic's auto-save, Ableton's crash recovery) and general backup services (Time Machine, external drive backup).
Audio file storage. The audio exports from the session — stems, bounces, mix exports, masters — stored permanently with version tracking and accessible to collaborators. This is where a music-specific cloud storage system is most useful. Individual exports typically fit Vault's per-file limit (e.g. 150MB); full DAW project bundles often do not — use Vault for audio assets and stems, not necessarily entire session archives.
Project documentation. Split agreements, creative briefs, feedback notes, task records, contracts. The paper trail that makes a project intelligible to anyone who comes back to it later.
Release assets. Artwork, press release, distributor metadata sheet, streaming platform links. The material associated with the release of the finished track.
Most online storage tools handle the first category (session backup) adequately. Fewer handle audio file storage with version tracking and metadata. Almost none handle project documentation and release assets in the same place as the audio.
The problem with local project storage
Local project storage — a folder on a hard drive or SSD — has three structural vulnerabilities that become increasingly significant as a catalog grows.
Hardware failure. Hard drives fail at a rate of approximately 1–5% per year. An SSD is more reliable but not immune. An unbackedup project on a single drive is one hardware event from being lost. The emotional and commercial cost of losing a finished mix, an approved master, or a catalog of unreleased material is significant and entirely preventable.
Collaboration friction. Sharing files from a local drive requires copying them to a shared location — Dropbox, WeTransfer, email. Every copy creates a divergence point where the shared copy and the local copy can become different versions. Collaborators who make changes to the shared copy create a version that does not exist on the local drive without manual reconciliation.
Access constraints. A project on a studio computer is not accessible from a laptop when travelling, from a home setup when working remotely, or from a phone when you want to reference something quickly. Cloud storage removes this constraint entirely.
What online music project storage needs to do
Beyond simple file hosting, music project storage has specific requirements that generic cloud tools do not address.
Permanent, lossless storage. Audio files must be stored at original quality with no re-encoding. A 24-bit/48kHz WAV must arrive as a 24-bit/48kHz WAV. Any quality degradation on upload or storage makes the stored file commercially unusable as a master or deliverable.
Version management. Multiple revisions of the same mix must be trackable — which is the approved version, which was the rough, which was the one sent to the mastering engineer. Without version management, the storage becomes a pile of files with ambiguous names. See track versions of songs for how Vault models this.
Metadata preservation. The commercial information attached to a track — ISRC, key, BPM, genre, moods, credits — must travel with the file. A stored audio file that has lost its metadata must be re-tagged before it can be used commercially.
Collaborator access. Project files must be shareable with specific collaborators with specific permissions — without making everything visible to everyone or requiring manual file copying.
Reliability and speed. Project files are large. Access needs to be fast regardless of the collaborator's location. Content delivery via a global CDN, rather than a single-region server, is the difference between usable and frustrating for international collaborations.
How TYFRA Vault stores music projects
Projects — the online project container
A Project in Vault is an online container for everything associated with an active track or session. Audio files (WAV, FLAC, AIFF, MP3 — up to 150MB each), stored at original quality with no re-encoding. Version tracking via Track Revisions (v1/v2/v3) for production iterations and Track Versions for functional variants (Instrumental, Radio Edit, Extended). Color-coded folders within the project for stems, mixes, references, and documentation. Task lists with assignments, due dates, and status.
Files in a Project are stored permanently until you delete them — not for 30 days, not until an expiry date, permanently. BunnyCDN global delivery means access and sharing are fast regardless of where collaborators are located.
Products — the release asset store
When a track is finished, it moves from a Project to a Product. A Product is the permanent home for a finished release — the approved master, artwork, complete metadata, streaming links, and distributor-ready export. Products are organised as Singles, EPs, or Albums with track ordering and release management.
The metadata that lived in the Project carries over to the Product automatically. The approved master from the Project is the file in the Product. There is no re-entry, no re-upload, no reconciliation between different copies of the same release.
Metadata storage — the commercial layer
Every file in Vault stores its full metadata: ISRC, ISWC, BPM, key, genre, moods, instruments, tags, lyrics, recording date, copyright information, and credits. Audio analysis automatically detects BPM and key on upload. This metadata makes the stored project commercially ready at any point — a sync opportunity, a distributor upload, or a Promo campaign can use the stored files without a metadata completion task first.
Global delivery
Files are served via BunnyCDN — a global content delivery network with edge servers across multiple regions. Download and streaming speed from a Vault share link is equivalent to major streaming platforms regardless of where the recipient is located. For international collaborations, this removes the "the file is taking ages to download" variable from the workflow.
Migrating existing projects to online storage
The practical challenge of moving to online project storage is the existing back catalog on local drives. A systematic approach works better than trying to migrate everything at once.
Start with active projects. Any project currently in production or scheduled for release should be migrated first — these are the files with the highest risk of loss and the most immediate need for collaborator access.
Next, released catalog. Tracks that are live on streaming platforms should have their masters and metadata stored in Vault — these are the files most likely to receive commercial requests (sync, remixing, re-releases) that require fast retrieval.
Finally, archive material. Demos, unfinished projects, and reference material can be migrated when convenient or left on local drives if they have no commercial application.
A partially migrated catalog with the commercially important material in Vault is more useful than a deferred migration waiting for a perfect moment that never arrives. For release workflow context see release planning.
How TYFRA fits
- Projects: permanent online containers for audio files, versions, metadata, tasks, splits
- Products: release containers for finished masters with distributor-ready export
- WAV/FLAC/AIFF/MP3, 150MB/file, lossless — no re-encoding on upload or storage
- BunnyCDN global delivery — fast access regardless of collaborator location
- Track Revisions + Track Versions: version management built into storage
- Complete metadata per file: ISRC/ISWC/BPM/key/moods/credits
- Audio analysis: BPM/key auto-detect
- Color-coded folders + smart tagging: project-level organisation
- Permanent storage — no expiry unless you delete
- Flows into Promo, Contracts, Finance without re-upload
- £9.99/mo · free tier available
Related on TYFRA
Common questions
Your data flows with you across TYFRA
These aren't separate apps. Your tracks, metadata, splits, contacts, and conversations stay connected—so every tool in the TYFRA suite can work from the same source of truth.