How to find missing samples in Ableton Live

When Ableton says media files are missing, it has not lost the audio, it has lost the path to it. Open Live's missing-files view (the status bar shows the count, or pick the Missing collection in the browser), click Search, and point Live at a folder the samples are likely to be in so it can relink them. Then run File → Collect All and Save, which copies every sample the set uses into the project folder, so that project can never lose them again.

Why samples go missing

Ableton doesn't copy every sample into your project by default. It references them by their location on your disk. So the moment a sample moves (and it moves whenever you reorganize a pack, empty your Downloads, uninstall a library, or open the project on a different computer), Ableton can't find it. The project itself is fine; the pointer to the audio is broken.

Find them with Ableton's own tools

When Live shows the missing-files message, you can hunt them down without leaving the app:

1. Open the missing-files view: the status bar at the bottom shows how many files are missing, or open the browser and choose the Missing collection.
2. Click Search and point Live at a folder it should look in (a good candidate is your main samples or Downloads folder). Live searches it and re-links whatever it finds.
3. Set an automatic search folder in Preferences → Library so Live checks it for missing files from now on.

This re-links what's still on your disk somewhere. If a sample was actually deleted, it's gone, which is exactly why the next step matters.

The permanent fix: Collect All and Save

Once a project's samples are found, make it self-contained so they can never go missing again: File → Collect All and Save. Live copies every sample the project uses into the project folder itself. From then on the project carries its own audio, so you can move it, back it up, or hand it to a collaborator and nothing breaks. Do this on anything you'd be upset to lose.

Spot missing samples before you open a project

The catch with all of the above is that you only discover a problem after you open the project, one at a time. If you have hundreds of projects, you have no idea which ones are time-bombs until you hit them, usually years later when the samples are long gone.

"External" and "missing" are not the same warning

This is the distinction that decides what you do next, and Live's own dialog doesn't draw it for you, because Live only complains once something is already broken. Reading the project file from outside, every sample reference sorts into one of a few buckets: living inside the project folder, sitting somewhere else on your drives, part of Ableton's factory content, or simply gone. A project then reads as collected, external, or missing.

Missing is the emergency you already know about. External is the one worth hunting, and it's invisible from inside Live: those projects open perfectly today, because the audio genuinely is on a drive somewhere, and they are exactly one folder rename, one uninstalled pack or one unplugged external disk away from becoming missing. Every project you have ever lost was external first. Finding them while the audio still exists turns a permanent loss into a two-minute Collect All and Save, and you can sort your whole library by that state rather than opening four hundred projects to ask each one. Reading the sample references is free.

Which pack did that sample come from?

Relinking is easier when you know what you're looking for, and "Vox_Chop_03.wav" tells you nothing. If you use Splice, the desktop app keeps a local index of everything you own, and Sessions reads it (read-only, from a copy, never the live file) to tell you which pack and publisher a sample came from, with a link straight to it on Splice. A sample you own but deleted locally is then a re-download rather than a loss. It matches on the filename rather than the path, which is the point: once you've run Collect All and Save, the sample sits in your project folder and its original path is long gone, so path matching would find nothing in precisely the projects you care most about. No Splice installed just means no extra information, never an error.

Splitting a shared folder without breaking the links

If your samples are "missing" because years of songs share one project folder and one Samples directory, the fix isn't relinking, it's separating. Sessions can split that pile into a folder per song and it copies each song's samples across, in the layout Live resolves, so each folder comes out genuinely self-contained rather than still tethered to the pool. Nothing is deleted: the original folder finishes the run holding every file it started with. References that point outside the pile (Splice content, factory packs, paths that were already dead) are left alone and counted, so the report can tell you "four still point at Splice, one was already missing before we started" rather than letting damage you arrived with read as damage it caused. The cleanup walkthrough covers that step in full.