Where FL Studio saves projects and backups on Windows and Mac

In FL Studio, open Options → File settings and check the User data folder. Start there rather than assuming your computer uses the default path. Documents may have been redirected, or you may have selected another drive.

For a standard setup, these are common project locations:

• Windows: C:\Users\<your-user>\Documents\Image-Line\FL Studio\Projects
• macOS: /Users/<your-user>/Documents/Image-Line/FL Studio/Projects

The global autosave folder is normally Backup under Projects. Depending on your current FL Studio backup settings, autosaves can instead be saved inside a project data folder. The location displayed in your installation is the source of truth.

Projects you saved elsewhere remain elsewhere: the default directory is not a complete inventory of every .flp on your computer.

Use FL Studio’s Browser Backup entry to inspect autosaves. Copy the candidate files to a separate folder before testing them, so ongoing autosaves cannot replace the copies you are comparing. Open a candidate, check the arrangement, and save a recovered working version with a new name.

If you are unsure which copy to use, compare both its date and its contents. “Newest” does not necessarily mean “the arrangement I wanted.” Listen through the sections that changed and confirm the samples are present.

Keep the damaged or unwanted original until you are satisfied with the recovery. Do not run a bulk cleanup while you are still searching. Image-Line’s recovery instructions explain the autosave recovery route.

These solve different problems:

1. Autosave helps when a session crashes or a recent edit goes wrong.
2. Named project versions let you return to a creative decision, such as the arrangement before a new chorus.
3. A separate backup protects against losing the working storage itself.

A copy on the same failing disk will not help if that disk becomes unreadable. A folder full of .flp versions also does not prove that the samples and other dependencies are included. Choose a separate backup destination and periodically verify a restore rather than relying only on a “completed” notification.

Before reorganizing a library or moving computers, prepare a tested project archive. The sharing guide explains how to include samples and what remains dependent on plugins.

SpendLess gives your managed FL Studio projects a local library with categories, covers and attached audio previews. This helps you choose a project without hunting through anonymous filenames. It is not a cloud backup service and does not recover files that have already disappeared.

For a project in its library, SpendLess can export a .zip or .spend archive. Keep a copy in your chosen backup destination, and test an import or opening on a copy before removing anything from the working library. The app’s managed samples folder needs to contain the audio you expect to preserve.

An attached audio preview is useful for recognizing an older track, but it is not an editable project backup. Keep both the creative source and a listening reference when possible. Follow the organization guide if identifying the correct project is the part that takes the most time.

Pick one completed track and one current work in progress. Copy their backups to a separate test folder and open those copies. Check the beginning, middle and end of each arrangement, then save a new test version. Keep this test separate from your active library.

If a sample is missing, investigate before trusting the same backup method for hundreds of tracks. If a plugin is unavailable, note its name and version alongside the project. A written dependency note is especially useful when returning to a session after changing computers.

Repeat the check after changing your storage layout or backup method. The goal is a process you can repeat calmly: know where the original lives, know where the separate copy lives, and know how to open that copy.