Back up your music projects: 3-2-1 for sessions, stems, masters and metadata

Every producer has the story, or will: the laptop that would not boot the week before a deadline, the external drive that clicked once and went quiet, the session that opened with half its samples marked missing. Hardware fails. The question is whether it costs you an afternoon or an album.

This guide applies the oldest rule in backups, 3-2-1, to a music catalogue. It covers what to save, how to make a project self-contained before you copy it, and how to archive a finished release so it still opens years from now. It is written for independent artists and small studios, and everything is as we checked it on 24 Oct 2026.

The 3-2-1 rule, in one paragraph

The US Cybersecurity and Infrastructure Security Agency (CISA) puts it plainly in its Data Backup Options paper. Keep 3 copies of any important file, one primary and two backups. Keep them on 2 different media types "to protect against different types of hazards". Store 1 copy offsite, meaning outside your home or studio.

For a musician that usually looks like this:

1. Primary: the working drive in your computer or the SSD you record to.
2. Backup one, local: an external drive at your desk that you copy to on a schedule.
3. Backup two, offsite: a cloud backup, or a second drive that lives at a friend's place, a family member's home or your rehearsal space and gets swapped regularly.

Two drives in the same bag are not two locations. A fire, a theft or a spilled coffee takes both.

Make one copy offline

CISA's #StopRansomware Guide tells organisations to "maintain offline, encrypted backups of critical data". The same logic suits a home studio. A drive that is permanently plugged in, or a folder that syncs instantly, can be encrypted, corrupted or deleted along with your working copy. A drive you plug in, update and unplug cannot.

Sync is not the same as backup

A synced folder mirrors your changes, including the bad ones. If you delete a project, the deletion syncs too. Most services keep deleted files for a while, but the window is limited and depends on the plan. Dropbox, for example, says its deleted-file recovery window is 30 days on its Basic, Plus and Family plans, 180 days on Professional, Essentials, Standard and Business, and 365 days on its top tiers. Check the window on whatever service you use, and treat a sync folder as convenience rather than as one of your three copies unless it keeps old versions for long enough to notice a mistake.

What to back up

A finished song is not one file. Think in four layers, from the most fragile to the most valuable.

1. Sessions

The DAW project is the recipe. On its own it is also the most likely thing to break, because it often points to audio and samples that live elsewhere on your drive. Ableton's manual describes what happens when those links break: clips that reference missing samples are marked "Offline" and Live plays silence in their place.

So before you back a session up, make it self-contained. In Live that is File > Collect All and Save, which copies the external files used in a Set into its Project folder so the Set uses those copies rather than their original paths. Other DAWs have their own version of this (often called consolidate, save as package or save with media); use it, then back up the whole project folder, not just the project file.

Also note, in a text file in the project folder:

• the DAW and version you used
• the third-party plug-ins on each track
• the sample rate and bit depth

Plug-ins are the part of a session that ages worst. A note listing them tells future you what to install, or what to replace.

2. Stems and printed tracks

Because plug-ins and DAWs change, the only way to guarantee you can rebuild a mix is to print audio. For each finished song, bounce:

• Multitracks: every track as a full-length audio file starting at bar one, with and without effects if you can spare the space.
• Stems: grouped submixes (drums, bass, music, lead vocal, backing vocals, effects) that sum to the mix.
• Instrumental and a cappella versions, which sync, remix and live requests ask for constantly.

Printed audio opens in any DAW, today or in a decade. It is also what collaborators, remixers and mix engineers actually need. If you plan to send stems to an AI mixing or mastering tool, our guide to preparing stems for AI mixing and mastering covers naming and format.

3. Masters

Keep the final approved master of every song, the exact files you delivered, not a re-export. The Library of Congress's Recommended Formats Statement for audio, the guide it uses for its own collections, prefers:

• the final release version, not a pre-production version
• a WAVE file with embedded metadata (Broadcast WAVE) over one without
• native resolution rather than up-sampled files
• uncompressed files rather than compressed

It lists 96 kHz/24-bit or higher PCM as high-resolution audio, and CD-quality 44.1 kHz/16-bit WAVE as acceptable. In plain terms: archive the master at the resolution you actually made it, in WAV, and keep the lossy copies (MP3, AAC) only as convenience files, never as the only copy.

4. Metadata

This is the layer people forget, and it is the one that gets you paid. The same Library of Congress statement asks for the "most complete metadata set as delivered to online distributors": titles, artist, composer, label, release date and identifiers such as ISRC and UPC.

For each release, save in the archive folder:

• the ISRC for every recording and the UPC for the release
• writer and publisher splits, with the signed split sheet
• credits for every performer, producer and engineer
• lyrics, artwork at full resolution, and any licence for samples or beats you used
• your distributor's confirmation or release summary

Our explainer on ISRC, ISWC and split sheets covers who issues each code. The point here is simpler: if your distributor shuts down, your laptop dies and your co-writer changes email address, this folder is the only proof of who did what.

Archiving a finished release

Once a release is out, freeze it. A simple structure that works:

2026 - Artist - Release Title/
  01 Sessions/        (collected project folders, one per song, plus plug-in notes)
  02 Multitracks/
  03 Stems/
  04 Mixes/           (approved mix, instrumental, a cappella)
  05 Masters/         (delivered WAV files, plus any vinyl or Atmos versions)
  06 Metadata/        (ISRC/UPC list, splits, credits, licences, lyrics)
  07 Artwork/
  README.txt          (what is where, DAW versions, release date)

Then:

1. Name files so they sort and explain themselves: song title, version and date, not "final_final_2.wav".
2. Copy the folder to all three locations and leave the archive alone. Do new work in a fresh copy.
3. Test a restore. CISA's ransomware guide advises regularly testing "the availability and integrity of backups". For you that means opening one project from the backup drive, on a different machine if you can, at least once a year.
4. Refresh old drives. Copy archives onto new media every few years rather than trusting one drive in a drawer indefinitely.

A routine you will actually keep

• Every session: save, and let your automatic local backup run.
• Every week: update the external drive, then unplug it.
• Every release: build the archive folder above and copy it to all three locations.
• Every year: test a restore and check your cloud plan still covers what you think it does.

What we think

Backups are framed as an IT chore, but for independent artists they are a rights issue. Your stems, multitracks and metadata are what make a catalogue licensable: a sync request asks for an instrumental, a remix deal asks for stems, a royalty dispute asks for the split sheet. Artists who lose those files do not only lose the past; they lose future income, and they lose leverage, because the only remaining copies may sit with a label, a mix engineer or a platform.

So we would push the rule further than 3-2-1. Own at least one complete copy of every release yourself, on media you control, regardless of what your label, distributor or collaborators keep. Ask your mix and mastering engineers to deliver multitracks, stems and session notes as part of the job, not as a favour later. And put the archive step into your release checklist, next to artwork and metadata, so it happens while everyone still remembers the details. Our release timeline checklist is a good place to add it.

None of this needs expensive gear. Two external drives and a habit beat any single clever tool.