In this article, I want to cover everything there is to know in regards to best practices of how to back up songs in FL Studio. Also, I’ll explain my personal music production folder structure to keep you organized for your life as a musician.
FL Studio really does make backing up easy!
But there’s a few gotchas to know in order to make file organization and backups run smoothly.
If you choose to use FL Studio’s User Data Folder, it’s a full-proof way of making sure your project saves all of its files, recordings, project bones, and such. But, you still have to be careful when working with plugins like Edison and Slicex, as your loop is not saved; you have to manually save it!
In my opinion, as useful as the User Data Folder is, it contains too many unnecessary files for the average producer. (I explain how I work later in this article.)
Now, I know the topic of backing up your music is boring to most people, but it’s crucial that you take an hour of your time to figure out a backup solution. Once your FL Studio backup system is established, maintaining it should only take about 10 minutes a month. (Making sure your backups are actually working and everything is proper.)
Here’s what we’re covering about backing up your FL Studio Projects and files:
User Data Folder vs. Custom FL Studio Folder
FL Studio has a feature called your User Data Folder.
The default location for your FL Studio User Data Folder on Windows 10 is:
This is where you can manage all of your music production projects etc, but if you have third-party sounds that you’ve purchased or downloaded over the years, you’ll have to include those manually. (Covered in the Browser Extra Search Folders section.)
Here’s what the default folder structure looks like – you’ll spend most of your time in the FL Studio folder:
You can also to select a custom location for this User Data Folder. (Using a service like Dropbox would be smart here, as you can keep multiple computers in sync with your music production; plus, it’s a form of backup!)
To set a custom location, press F10 to open Settings, and select File:
Under User data folder, Left Click the folder or directory path to select your own folder.
If you choose a custom path for your FL Studio User Data Folder, it will ask you to close and restart FL Studio.
In addition, if you’ve used this User Data Folder over the years, you’ll have to manually copy files from the default User Data Folder to your new location.
I think I’d use this User Data Folder if it didn’t contain all of these extra files like FL Studio’s native VST presets. (As most producers use third-party plugins.)
As an idea: Image-Line should use this User Data Folder as a child to their parent folders already within the FL Studio installation. That way, we could create a custom folder if we end up using one of these native FL Studio plugins to create own custom presets, which would be added after their default files.
The Custom Folder Approach
The reason I like a custom folder is it allows me to set up my folder how I like.
It’s important that you establish a Music Production Folder early on in your producing career.
My music production folder contains everything to do with my music. I store all my sounds, VSTs, projects, and even any stuff I do with clients. (VST3 plugins have to be installed in Windows’ Common Files folder – kind of annoying because everything can’t be all contained inside this single music folder.)
I find this the easiest way to stay organized, keep things minimal, and back-up.
Here’s the process of creating your own custom music production folder:
- Create a main Music Production Folder to nest all things music.
- Create Sub-Folders: Albums, Beat Tapes, Sounds, Sound Design, Clients, etc.
- Create a new folder for each project.
- Assign each song’s Project Data Folder inside Settings -> Project.
- A step-by-step walk through is inside my music folder course.
Note – I have created a course to make sure you create a proper music production folder to enjoy your career as a music producer.
When creating your own custom folder, you’re taking things into your own hands, so to speak.
So when you back up your files, you have to make sure that EVERYTHING is included that you need for that song at a later date.
The process to backup in FL Studio comes later in this article, but it’s important I add this info here, too:
Whenever you start a new project in FL Studio, take advantage of their Project -> Data folder (This is different from the User Data Folder discussed earlier – I know, it can get confusing, lol.)
This folder essentially takes precedence over the User Data Folder.
Why setting up this Project -> Data folder is important is because it improves workflow.
Any audio recordings you do, if you use Slicex/Edison and drag and drop audio from within their editors, it saves that slice to this folder.
But when backing up, this is where things get a tricky; for both the User Data Folder + your own custom folder.
FL Studio has the options Zipped loop package and Project data files. (Explained with pictures later.)
These will backup the individual sounds within your project.
So that should be all you need, right? Well, not if you’ve used Edison or Slicex and want to save the loops within them.
How to Backup Slicex
By default, when you save your .flp (FL Studio project), it will save all your VSTs settings, so no need to worry about that.
When you back up the individual sounds with the features above (Zipped/Project data files), this should cover your basis, too; it backs up all individual sounds of the song.
But, you’ll still have to manually save a loop within Slicex like so:
It’s just one of those little gotchas to protect yourself for safe backups.
Let’s quickly cover the hardware and software you’ll need for a proper back up solution. We’ll then get into how FL Studio backs up your music, the features available, and best practices.
Hardware and Software Needed for Proper FL Studio Backups
In the backup world, an important term is redundancy.
This means to have duplicates of your duplicates, so to speak.
Back up extremists even take this as far as making sure you store back ups on different forms of media; USB, CD, HDD, and Cloud for example.
My suggestion would be:
- External Hard Drive
- Cloud Backup (Dropbox or something similar)
- The Current Computer You Work On
I actually have two external hard drives. One where I’ve stored my files and is in a fire box, then one that’s always connected to my computer for new changes.
I think that’s a really simple approach, and secures you pretty well.
As popular as cloud back up is, I feel it’s still extremely important to have your own local copy of your music data.
To do that, you’ll need an external hard drive and backup software.
Hard Drive Suggestions:
- USB powered (doesn’t need an AC adapter)
- Double the size of your current hard drive (prevents software saying full!)
- 3.0 USB is pretty standard now, but make sure it’s not 2.0!
We want your backup system so it’s literally set it, and forget it!
Backup Hardware + Software Products
In regards to using your backup software, I like using Incremental Backups.
The idea works like this:
You make one full backup, then additional backups save only the files you’ve changed, added, or removed.
Full backups take a long time, and consume a lot of CPU; so this is a great approach to back yourself up, and not have your computer bogged down by a backup.
I usually set this full backup to happen once a week, then my incremental backups are the other 6 days of the week.
I will usually keep about 3-4 full backups, and select the option in the backup software to remove the oldest full backup. This way my external hard drive doesn’t get full, and it’s set on auto-pilot!
Pretty simple, hey!
Options to Back Up a Song in FL Studio
The best approach to stay organized with your FL Studio projects is to create a new folder for each project.
Within FL Studio, you’ll then assign its Project Data Folder under:
Settings -> Project -> Data folder
A convenient feature Image-Line has added is the Auto button; it automatically selects the path from where you’ve opened the .flp (FL Studio Project) !
I personally create this folder in my own custom folder, but if you use the User Data Folder, you can save it in your Projects folder.
This ensures any files you’ve dragged into FL Studio from Edison / Slicex, or audio recorded through the mixer are automatically saved inside this project’s folder.
If you do not assign a project folder, these recordings and dragged files will save to your default User Data Folder location. (Unless you manually select a save location through Save as.)
When you set a project folder, it becomes the main folder. It essentially takes precedence over the general User Data Folder for most things, such as the project file, individual files, dragged files, and recorded audio.
But your User Data Folder is still used for Project bones, templates, and other things.
Let’s cover how FL Studio allows us to back up our song and save in a couple different ways:
- Zipped loop package
- Project data files
- Exporting Stems
- Project bones
Zipped Loop Package
Zipped loop package is contained under:
File -> Export -> Zipped loop package
FL Studio’s zipped loop package is your all-in-one solution to backup your song.
It creates a .zip file which stores:
- The FL Studio Project (.flp)
- All Sounds Used in the Project
Again, Zipped loop package does not include Slicex or Edison files!
Why this is important to back up manually is because right now, you’re on the same computer with this User Data Folder.
If you end up reformatting, or purchasing a new computer, but forget to transfer over this User Data Folder, these Edison and Slicex instances have missing files.
And I know for me, If I use Slicex, I many times move my slice markers to fine-tune my chops.
Or for Edison, I use it to record SFX or various other creative uses, and rely on Edison to hold that information as a backup, hoping it stays there with the project.
Project Data Files
Project Data Files are contained under
File -> Export -> Project Data Files
Using FL Studio’s Project Data Files is very similar to the Zipped Loop Package, except it doesn’t create a .zip file, and does not save a copy of the .flp.
It simply backs up the individual files (one-shot samples, recordings, Direct Wave files, etc.)
I personally use Project Data Files because, as I mentioned, I create a new folder for each project I work on. This folder already contains my .flp (FL Studio project), I just need to back up the sounds.
So within this folder, I actually create a new folder, label it with the acronym of the song name, then -sounds.
For example; let’s say the song title is Never Going to Give Up:
I’d create a folder called ngtgu-sounds within that project folder.
This keeps my folder clean. I have the .flp and the sounds for archive purposes.
Stems have many uses as a producer:
- Collaborating with Other Producers
- Sending Your Song Out to Mix in Another DAW
- Stem Mastering (More Control Over the Master)
- Archiving/Backup Purposes
I personally don’t use stems to backup, as I think having the .flp and your sounds should be good enough. My main reason is just hard drive space.
But this is taking a risk; what if in 10 years you can’t open up the project because the new version of FL Studio isn’t backwards compatible. And what if the new version of Windows can’t open an old version of FL Studio?
So, if you are extremely serious about your backups and want no risks, then in addition to the .flp and sounds, I’d backup the stems too. (Some people even back up stems with and without effects. I’d say just one version with your effects is safe.)
Here’s how to export stems in FL Studio:
FL Studio will export a .WAV file for sounds that have been assigned a mixer track.
If you’ve added effects on this mixer insert, it will be applied to that .WAV file.
This includes the MASTER as well as the individual instruments; you’ll have a .WAV trackout for each.
Here’s some pictures of what stems look like:
This project example had 40 files @ 1.36 GB (The track is called Ambition, off my BEAT TAPES By GratuiTous Vol. 8!)
So if I were to export about a 3 minute and 30 second song @ 16-Bit .WAV, it would be about 40 MB.
But when exporting stems, you are literally creating this file multiplied by however many mixer inserts you have. Compare this to just the .flp and individual sounds backed up at probably 20 MB haha!
To export stems, you all your sounds must be assigned to mixer tracks to have full control, otherwise they’ll just be summed into the MASTER file; this would give no control over mixing.
Next, you export the song as you normally would, except with one difference.
Select File -> Export -> Wave file:
On your export settings, enable Split Mixer Tracks:
Again, you’ll notice your file size increases drastically, just so you’re aware.
I’d personally export these to a new folder to keep your project organized.
Just click Start to proceed with rendering!
And that’s how stems work in FL Studio, some uses of them, and what to be aware of.
I personally don’t use Project bones too often, but it’s important to know what FL Studio Project bones do.
Project bones are located under File -> Export -> Project bones:
The default export folder for Project bones is actually located in your User Data Folder, not your Project Data Folder.
This is so you can drag and drop different elements between songs.
Upon export of Project bones, the following folder looks like this:
As you can see, Project bones stores information like:
- MIDI Notes / Step Sequencer Sound Information
- Mixer Inserts
- Plugin Effect States
If you’ve used the same sound twice within your project, FL Studio will even label this as Pattern 1 – Kick and Pattern 2 – Kick so you keep each pattern unique. (Genius!)
Now the only reason you’d really need to export Project bones is if you want to transfer multiple elements from one song into another song.
You can simply just drag and drop previous MIDI notes:
Other than that, it’d be just like duplicating the .flp (FL Studio project).
Project bones just makes it super easy to pull certain elements out of your song to be re-used in another project.
Including Custom Folders with Extra Search Folders
Browser Extra Search Folders are how FL Studio finds your own sounds.
Since I use my own custom music production folder, FL Studio has no idea of its location, so we have to help guide FL Studio on where to search.
FL Studio suggests not including your whole hard drive! – Just where your sounds are located!
So within my music production folder, I have a folder called Sounds.
Inside of Sounds, it also holds two other folders: VSTs and Drum Kits.
I would make sure to include Drum Kits as an Extra Search Folder inside of FL Studio.
Extra Search Folders are located at:
Settings (F10) -> File -> Browser extra search folders
If you’d like to rename this folder, you can do so with the Browser Name column!
FL Studio allows you to manually select your custom folder, or you can simply drag and drop folders right into the browser, and it will be there for you to use.
This benefits me in two ways:
- FL Studio searches this folder upon startup, finding all my third-party sounds.
- I can access this folder straight from within the browser to listen to sounds and drag and drop them for use in my projects.
I really do recommend using a service like Dropbox for your Drum Kits. It not only backs up your files, but is easy to keep multiple computers in sync with your sounds.
And if you want to remove your custom folders from the browser, within settings you have to double click the path to highlight it, press Backspace and then Enter.
Once you close the settings, you’ll see the folder is removed. (Tricky to figure out when new to FL Studio!)
To include your VSTs, that’s located in:
Settings -> File -> Plugins -> Manage Plugins
FL Studio Auto Save Folder Location and How it Works
FL Studio really does try to help you out in every way possible.
I really like this company for how they listen to their users. (It’d be hard to find a similar company, which also offers lifetime free updates!)
FL Studio auto backs up to your User Data Folder.
The default FL Studio auto save location is:
C:\Users\[Your Username]\Documents\Image-Line\FL Studio\Projects\Backup
Select any of these files to revert to an autosave of your FL Studio project.
This auto save/auto backup option allows you to select how frequently FL Studio will save your work.
But you have to be careful on what option you select. (Which is why you read the help manual, right!)
For example, some autosave options only save when you manually save, and don’t save if FL Studio is playing! (That’s dangerous! – Most times if FL Studio is going to crash, it’s typically while FL Studio is playing!)
The safest approach here would be to select:
Frequently (every 5 minutes & before risky operations)
In addition, FL Studio only backs up 20 versions of your song. The whole idea is to be used in case of emergencies, because your own backups should help you to never lose a project; since these autosaves happen very quick (every 5 minutes), it can help you to lose any quick and fresh changes you’ve made.)
As a bonus tip, which the manual tells us, if you want to create permanent sequential backups, you would have to use Save as and store the song under a new name. (Eg. Song_Name-1)
This allows you to go back at any time of your project, as FL Studio only backs up the last 20 versions of your auto save.
Yes, this is getting quite meticulous, but for those who work this way, the option is there.
It’s important to understand these features and take advantage of them if they pertain to your workflow.
Commonly Asked FL Studio Backup Questions
Over my years, and through some Google research, I’ve noticed there’s a few common questions out there in regards to backing up with FL Studio.
I’ll cover these questions in this section.
How to Fix “Some Data Files Could Not Be Located” in FL Studio (Missing Files)
Experiencing missing files within FL Studio is probably the worst experience you can have as a producer.
Such as the FL Studio error: Studio some data files could not be located.
Over my years, I’ve discovered the best way to prevent missing files.
The way how FL Studio works is it will search all files within the folders you’ve included. (Browser Extra Search Folders)
If you’re always working from the same computer, you’ll never know the experience of missing files until you either start moving folders around, reformat, or purchase a new computer. It totally dampens your creative vibe, and slows you down by having to filter through your files to find the proper files.
As an example:
FL Studio will remember the path of where you’ve dragged in files, while working on the same computer with no folders moved etc.
Let’s say you’re working on two songs that have vocals. If you label song one’s first verse Verse 1, then also label song two’s first verse Verse 1, FL Studio will actually know which is which, if you haven’t moved files around.
But if you have moved folders around after you have saved, when you reopen that project, you can either experience:
- The wrong Verse 1 is loaded into your song
- You get a missing files error in FL Studio
This is why I include the acronym before my sounds folder within my project, and also include this acronym before verse one.
Again, if my song name is Never Give Up, I’d label my Verse 1 as ngu-verse-1.
This keeps your file unique so that FL Studio will not pull in the wrong file. And if FL Studio does pop up an error with missing files, you’ll know exactly where to find it. (Then you can set your Project data folder accordingly, or just drop the .flp in the same folder as the song’s sounds, and reopen the project.)
In addition, if you’re wondering how to make FL search again for missing files, you simply just have to reload the project.
If FL Studio pulls up the error of missing files, the WORST thing you can do is save.
If you save, you’re literally telling FL Studio, “Oh, that’s okay I have missing files, I want my project like this.”
So if you open a project, and it has missing files, DO NOT SAVE.
Figure out what the error is, and fix it!
In this case of missing files, you may just have drag and drop the .flp into the same folder as the sounds, and reopen the project. You can then set your project’s Data Folder within Settings -> Project -> Data Folder and you should be good to go.
That’s how FL projects find audio files which have been moved.
This has been my solution to prevent missing files in FL Studio.
How to Recover Crashed Projects in FL Studio
In all my years, FL Studio has been very reliable to me, barely ever crashing.
This could be because I have a solid computer, but if your FL Studio has crashed, and you’ve lost your project, here’s where to find it.
FL Studio has an auto save folder inside your User Data Folder:
C:\Users\[Your Username]\Documents\Image-Line\FL Studio\Projects\Backup
Make sure you set your auto back ups to 5 minutes + risky operations under:
Settings (F10) -> File -> Backup
This will allow you to retain changes before a crash in FL Studio!
Error: Could Not Save to FL Studio File
I’ve experienced this too. It’s only happened to me in recent versions of FL Studio, though.
How I fix this is simply trying to save again. Sometimes it just works!
If it’s being really difficult, I’ll actually create another copy through Save as with a unique name. (I’ll then delete the old, and change the new file back to the original song name.)
After some research, it seems as though it could be a file/folder permissions issue as discussed on this Image-Line forum thread.
Wrapping Up FL Studio Back Ups
So that’s my in-depth guide on how to properly back up songs in FL Studio.
If you have any questions, you can always send me an email and I can add to these commonly asked questions list.
I hope my experiences and guide helps you to focus more on your music and less on your backups.
Don’t be silly. Take out an hour, get your backup gear, and set it on auto-pilot.
You’d be foolish not to.