# How to Avoid Missing Files When Archiving a Music Project

> Gather your session files, preserve the sound of your plugins, and check a restored copy before deleting the originals.

Author: Roye
URL: https://wuse.works/en/blog/archive-music-projects-without-missing-files/

## Start by gathering, copying, and checking

To avoid missing files, gather the media inside the project, save audio of sounds that depend on plugins, and check a copy before deleting the originals. If you work with wuse, add a note to your versions and deliveries identifying which session you're archiving. Keep separate copies too: saving the session is just the beginning.

I recommend wrapping up the archive with one specific question: could I pick this song back up without looking for anything in my Downloads folder, on another drive, or in old messages? The goal is to keep what you need to open it, listen to it, and understand what was approved.

## Why a saved session can still be incomplete

In Ableton Live, saving a Set keeps references to the files you've used. That means a session can open perfectly on your computer while still depending on an audio file outside its folder. When you switch computers or disconnect that drive, the problem shows up.

For example: you received a vocal, downloaded it, and dragged it into the arrangement. Before archiving, check that the recording has been collected into the project. Seeing it on screen doesn't confirm that it's already included in the folder.

Extra work can start with something small: figuring out which of three vocals was the right one, asking for a file again, or finding out which version your collaborator received. To avoid that search, decide now what you want to keep: the approved mix, the editable session, and any alternatives that are still worth keeping.

It also helps to separate two checks. One is locating the media; the other is reproducing the sound. Having all the audio files together doesn't install the plugins you used. We'll deal with that second part later by saving audio from the tracks that need them.

## Gather the assets from your DAW

In Ableton Live, save the Set in its own project folder. Then go to File > Collect All and Save, select the locations you need, and confirm. Include Files from Factory Packs if the destination won't have the same Packs. To move it, copy the entire folder with its files and subfolders; don't look for a new single file containing everything.

In Logic Pro, use File > Project Management > Consolidate. Select the types of assets you need to copy into the project. This function covers audio, Sampler, Alchemy, and Ultrabeat data, Space Designer impulse responses, video, and sound library content. It also collects assets used by project alternatives.

Don't assume that selection takes care of every third-party library. Make a note of the additional instruments your song uses and check their dependencies when you restore it. What a particular command covers isn't a guarantee that it handles everything installed on your computer.

My advice is to work with a copy intended for the archive and give it a recognizable name, like Bruma_archivo_v07. Before continuing, confirm that it's the version you want to keep. A complete collection of the wrong session doesn't solve the delivery either.

## Decide what to keep before reducing the size

In Cubase Artist 15, open File > Back up Project and review the options before confirming. Minimize Audio Files keeps only the portions you've used: the excluded parts will no longer be available for further editing from that copy. Remove Unused Files leaves out files that aren't being used.

Also check Do Not Back up Video and Do Not Back up Mixdown Folder. If you need that content, don't exclude it. A smaller backup can work for a specific task, but you need to know what's in it.

For example: the song ends up using one phrase from a long guitar take. If you want to keep the option of choosing another phrase later, I recommend keeping a complete copy before minimizing the audio. Use the same judgment with vocal doubles, improvisations, and discarded arrangements: decide what's worth keeping before cleaning up.

For naming and separating the versions you do want to keep, you can use the guide on [how to organize versions and stems in a music project](/en/blog/organize-music-project-versions-and-stems/). Here, the priority is checking that the archive includes everything you've chosen.

## Keep a reference of the sound and the editable session

Collect All and Save doesn't copy plugins. To preserve audio processed by them when transferring a Live project, you can use Freeze and Flatten in Live 11 or Bounce in Live 12 when the destination doesn't have the same plugins. Do this on a copy if you also want to keep your original session editable.

For an archive, I'd save a reference mix and audio from the tracks whose sound depends on those instruments or effects. Choose names that explain what you're listening to: Bruma_bajo_procesado_v07 is more useful than Audio_28.

For example: you want to preserve a synth sound and still have the option to change its notes. Keep the original project and also prepare an audio version of that sound. In the archive note, say which one serves each purpose. That makes it clear what you can listen to directly and what requires restoring the working setup.

If someone else will pick up the song in a different program, also check [how to collaborate when each producer uses a different DAW](/en/blog/collaborating-across-daws/). Agreeing on what they need to receive is part of wrapping up.

## Leave a note that makes it easy to pick the song back up

Add a text file with a short description of the contents. To make it useful when working with other musicians, I'd include the DAW version, the required plugins and libraries, the tempo, and the exact name of the approved mix. Check the project as you fill in those details.

You can copy this template and replace the fields in brackets. You don't need to write a report: just give another musician enough information to find what they need without guessing.

- Identification: song [name], archived version [version], date [date], and person responsible for preparing the copy [name].
- Contents: session [exact name], reference mix [file], and description of the additional audio files [contents].
- Setup: DAW and version [details], required plugins and libraries [details], tempo or tempo changes [details].
- Check: copy opened from [location], review date [date], unresolved issues [details], and approved decisions [details].

## Test the restore before removing the originals

Keep at least two copies on separate storage media in physically different locations. Check that you can read the files at least once a year. That check should be part of maintaining the archive.

For a music session, I suggest taking that check further: copy the backup to another location and open it from there. If you can, use another computer without access to the original media folders. This test is meant to uncover dependencies that your usual computer can still resolve.

Listen to the song and compare it with the reference mix. Check any warnings and pay attention to tracks that depend on instruments or effects. Write down exactly what's missing before trying to fix it; changing several things at once makes the problem harder to identify.

If a collaborator receives the archive, ask for specific confirmation: which session they opened, what they heard, and what issue they found. A message like “downloaded” only confirms receipt. I'd keep the working copy until this review is finished and the outstanding issues are resolved.

## Mistakes to check for before calling it done

Don't delete a large folder just because its name looks generic. First, identify what's inside and decide whether it's part of what you need to keep. Cleanup should follow a decision about the project.

Don't label a version approved based on a hunch, either. If there's any doubt, write “approval pending” and keep the original delivery names. It's better to record a pending decision than make the next musician piece it together.

Before wrapping up, go through these four points. If any one of them fails, leave the archive marked as pending and fix that point.

- The archived session matches the chosen version, and its required assets have been gathered.
- Anything excluded from the copy is consistent with what you decided to keep.
- The reference audio and notes make the expected result clear.
- The copy has been opened and checked; any issues are resolved or clearly documented.

## How wuse fits into wrapping up the project

wuse lets you work with music projects, audio versions, stems, files, collaborators, and comments, as well as share deliveries. You can use that space to keep the context of the collaboration alongside the material: which version was reviewed and which decision is still pending.

I recommend leaving a specific closing comment. For example: “The reference is Bruma_mezcla_v07. The session file matches that version. The check that it opens is still pending.” Update that note when you finish checking.

Gathering assets and testing that the session opens are still steps in your archiving workflow. wuse doesn't automatically convert sessions between DAWs; keep your separate copies and prepare the right material for whoever will pick it back up.

Start with a finished song: gather its assets, prepare the reference, fill in the note, and test the restore. Then open the project in wuse and clearly identify the delivery that matches that archive.

## Frequently asked questions

### Does saving the session also save all the audio files?

Don't assume it does. In Live, the Set saves references to the files. Run the media collection command and keep the entire project folder. Then check the copy you're going to archive.

### Where is the file that Collect All and Save creates?

The collected media stays inside the project folder; it doesn't create a single file that replaces that whole structure. Copy the entire folder.

### Does consolidating in Logic include project alternatives?

Yes, it covers assets used by alternatives in the current project. Select the asset types you need when consolidating, and check dependencies for third-party instruments separately.

### Can I delete takes that aren't in the final mix?

First, decide whether you want to keep them for future edits. My advice is to keep a complete copy before preparing a smaller one. In Cubase, excluding unused files or minimizing audio can leave that material out of the backup.

### What should I do if the session opens but a plugin is missing?

Check the setup you documented and whether you can install the relevant plugin. To prepare the archive now, also keep processed audio from the tracks that need it, and keep the session editable.

### When can I delete the working folder?

I'd wait until you've tested the restore, reviewed the contents you chose to keep, and confirmed that separate copies exist. If someone else is receiving the project, include their check that it opens and plays back before removing your working copy.

## About Roye

Roye writes wuse's guides on music production and collaboration. Under the name Dibo Roye, he has public production credits for ALE ALAS and songwriting credits for Tillaz.