FL Studio 
FL Studio colors a channel red when it can't find the sample behind it, and the fix depends on what went missing: an audio file, a folder path, a plugin or the plugin's own library. Restore the original file or add its folder in Options > File settings, then reopen a copy of the project. A missing plugin needs Manage plugins, not a sample search. I start with the red channels and the missing-data message, because they tell you which of the four cases you have.
Work in this order: protect the project, read the missing names, make the original files visible again, and replace a file only when the original is gone. Each red channel gets its own check.
Identify what is missing before changing paths
| What you see | What is missing | First check |
|---|---|---|
| Audio Clip or Sampler channel is red | A WAV, AIFF, MP3 or other audio file | The filename in the load message and the folder where that file used to live |
| A plugin instrument is replaced by an empty channel | The plugin or an incompatible plugin format | Manage plugins and the plugin search path |
| The plugin opens but its preset says content is missing | The plugin's own sample library | That vendor's library location or content manager |
| Many projects fail after a drive or computer move | A shared sample-library path or User data location | File settings, mounted drive names and copied library folders |
| Only one project fails after its folder was moved | Files stored beside or below the old project folder | The project data folder and the old folder structure |
| Sounds that shipped with FL Studio open red | A sample dropped from newer versions, or a broken audio CODEC | Image-Line's missing-sample answer, covered below |
| Recorded takes are missing after the project moved | Takes saved to the User data folder instead of a project data folder | Audio\Recorded inside the User data folder |
A missing WAV and a missing VST can throw up similar warnings, but you can't fix one with the other. Bringing back the WAV won't install the plugin that used it, and reinstalling the plugin won't recreate an external vocal take or drum sample that lived somewhere else.
Make a safe copy of the project first
Protect the project before anything else. I save a copy with File > Save new version (Ctrl+N) before any search, because it gives the project a unique name and leaves the original file and its references untouched. Leave the original .flp alone until the copy opens with no red channels.
Write down the missing filenames exactly, extensions and duplicates included. A file called Kick 01.wav tells you little on its own if you have six files by that name; the original folder, length and sound still matter. Don't accept a random replacement only because its name matches.
Restore a missing audio file or Audio Clip
Image-Line's missing-files guide says FL Studio searches its own installation folder first, then the Browser extra search folders. If you know where the file is, put it back in its old folder or add the sample-library folder above it in Options > File settings > Browser extra search folders. I add the smallest useful parent folder, because FL Studio searches every subfolder of each search folder when a project loads. A whole drive as a search folder slows every project load.
If you don't know where the file went, use the drive-root search that the Browser manual gives for files you moved somewhere and forgot about. It makes project loads very long while each drive is searched, so it stays for one load only:
- Add the root of each drive, such as C: and D:, as Browser extra search folders in Options > File settings.
- Reload the project copy and wait while FL Studio searches the whole of each drive.
- Select a channel that loaded, click the waveform display of its Audio Clip or Sampler channel and drag it onto the Browser, which opens at the folder the file loaded from.
- Move the found files to a known location, or add their folder as a Browser extra search folder.
- Remove every drive root from the search folders, because drive roots make later file searches very slow.
Once the right file is visible, reopen the project copy. I listen to each restored clip before saving, because a file with the same name can load fine and still be the wrong recording.
Check the project data folder and old folder structure
Projects saved with a data folder keep their audio in the same folder as the .flp. With Store relative to the project file, FL Studio creates a folder with the project's name that holds the .flp and three subfolders: Audio, Renders and Backups. Moving only the .flp out of that folder leaves those files behind.
Recordings follow the same setting. With the Data folder location set to "Don't use a data folder", FL Studio saves takes to the User data folder, under Documents\Image-Line\FL Studio\Audio\Recorded on Windows. With a project data folder, audio to disk recordings go into that folder. If takes from older projects vanish together, check that the User data folder path in File settings has not changed, and whether a cloud backup option in your operating system has moved the Documents folder.
If the original folder still exists, move the whole project folder back together or rebuild its old structure. For a planned move, follow the project-folder guide instead of dragging the .flp on its own. To collect a project for transfer, File > Export > Project data files saves copies of all samples, presets and other plugin data the project uses into one folder you choose, as the File menu documentation describes.
Did a sound that came with FL Studio open red? Image-Line's missing-sample guidance names two common causes: FL Studio can't find the sample data, or an audio CODEC is broken. On the first, Image-Line removes some samples from newer versions as it updates the library to newer sounds, and the same answer links to all samples and data dropped from FL Studio 1 to 12, available to FL Studio owners. Restore the named file into a separate folder, then add that folder to the search paths. A CODEC is the software that converts compressed audio, and when it is not installed correctly, Sampler channels can open with missing data; the CODEC reinstall notes are linked from the same answer. Neither route replaces third-party packs or your own recordings.
Fix a moved sample-library or Browser path
When many projects lose samples at once after a drive rename or a move to a new computer, suspect the path before the files. FL Studio searches only the locations in its own Browser when it loads a project, so a pack that sits outside them stays red. Check the User data folder and the Browser extra search folders in File settings, and on an external drive make sure it is connected and that its name or drive letter matches the path FL Studio expects.
Add the library folder once, then reopen one affected project copy. Don't list the same library through several overlapping parents, since one parent already covers every subfolder below it. I keep loose samples under one parent folder, because one Browser extra search folder then covers all of them, subfolders included. The FL Studio Browser guide covers search folders and tabs in more detail.
On a new computer, copying FL Studio and its settings is not enough. Image-Line's migration instructions say third-party sample and plugin data have to be copied by hand from the old machine, and that it does not have to go into the same folder, as long as the Custom folders settings make it visible to FL Studio. Updating on a Mac is a separate risk. I move anything stored inside FL Studio.app out before an update, because the macOS update deletes personal files such as projects and samples left in its Package Contents folder. A Windows update replaces program files only.
Separate plugin content from project audio
Kontakt, sampler instruments and other third-party plugins can open fine while their own libraries are offline. That content is handled by the plugin vendor, and FL Studio's Audio Clip search doesn't look for it. Restore the library in the vendor's manager or point the plugin at its content folder, then reopen the project copy.
Don't add a proprietary library folder to every FL Studio Browser search path unless you also use its audio files directly. The plugin expects its own database, metadata and authorization, so a visible folder doesn't mean the instrument will recognize the library.
Handle a missing plugin separately
If FL Studio can't find the plugin itself, open Options > File settings > Manage plugins. A fast scan identifies plugins only by file name, so a plugin renamed by you or its developer is not found when a project loads it; Verify plugins stores a unique ID for each plugin, which lets FL Studio load it after a rename. I run Verify plugins with Rescan previously verified plugins and Rescan plugins with errors ticked, because one pass then re-identifies renamed plugins and retries the ones that failed before.
If the scan still misses it, search your drives for the exact plugin name plus its format extension: .dll for VST2 on Windows, .vst3 for VST3, .vst or .vst3 on a Mac, and .component for AU. For a VST2 .dll found outside the scanned folders, add its folder as a VST plugins extra search folder. Image-Line's plugin installation page limits custom search paths to VST1 and VST2 plugins, so VST3 and AU plugins have to sit in the default system folders. Never install plugins to FL Studio's own Plugins\VST folder, which is reserved for legacy native FL Studio plugins. The plugin install guide covers the default folders for each format.
The plugin-not-showing guide covers scan errors, unknown entries and favorites. Keep that work separate from recovering samples. Installing another edition of the plugin can bring back the instrument shell and still leave its library or the project's external WAV files missing.
Use a Zipped loop package for a portable copy
Once everything is recovered, make a portable archive with File > Export > Zipped loop package. It saves the .flp and the samples tied to the project in one standard ZIP file. The Zipped loop package guide explains what to check before sending or archiving it.
The archive doesn't bundle third-party plugin installers, licenses or full proprietary libraries. The destination computer still needs compatible plugins and authorized content. Open the archive copy before you delete or move the original source folders.
What makes the problem worse
- Do not replace files blindly. A matching filename can still be the wrong take or sample.
- Do not leave a drive root as a search folder. Image-Line warns that drive roots make later file searches very slow.
- Do not move more folders during diagnosis. Restore one known path, reopen the project copy and check the result.
- Do not expect a backup to hold audio. Autosave backups and File > Revert to last backup restore the project file, not a deleted recording or sample; the autosave and backup guide shows where those backups live.
- Do not treat a plugin reinstall as sample recovery. The plugin binary, its library and the project audio are three separate things.
Prevent missing samples when moving a project
Project general settings are stored in each project file, so the data folder choice belongs to each project. I set Data folder location to Store relative to the project file for new projects, because Image-Line calls it the cleanest long-term solution for project management. Before any planned move, go through this list:
- Set File management to Move or Copy, so recordings, renders and sliced audio made in the project land in its folder.
- Turn on Copy used samples to the project folder, so factory and other samples the project uses get a copy there too.
- Make a Zipped loop package for handoff or archiving.
- Back up the project folder, the User data folder and your shared sample libraries separately.
- Note the plugin names, formats and library versions the project needs.
- On a Mac, keep nothing inside FL Studio.app.
- Open the collected copy before you remove the original paths.
Frequently asked questions
Why are my samples missing in FL Studio?
FL Studio can't find the files the project points to. Image-Line lists three reasons: the samples came with an older FL Studio version, you moved or removed them, or you renamed them. A broken audio CODEC can also make Sampler channels open with missing data.
Where does FL Studio look for missing samples?
In its own installation folder, then in the Browser extra search folders set in Options > File settings, subfolders included. It searches only those locations when it loads a project, so a pack stored anywhere else stays red until you add its folder.
How do you find where a sample is stored in FL Studio?
Click the waveform display of the Audio Clip or Sampler channel and drag it onto the Browser. The Browser opens at the folder the file loaded from.
Why are my recordings missing in FL Studio?
Without a project data folder, FL Studio saves recordings to the User data folder, under Audio\Recorded. If that path changed, or a cloud backup moved the Documents folder, older takes go missing. With Store relative to the project file, recordings stay in the project's own folder.
Does a Zipped loop package include plugins?
No. It saves the .flp and the samples associated with the project in one ZIP file. Plugins, their licenses and their sample libraries have to be installed on the other computer.
Can autosave bring back a deleted sample?
No. Autosave backs up the project, and File > Revert to last backup loads that backup. Neither stores the audio files, so restore the sample from its folder, a backup of your library or a Zipped loop package.
