FL Studio 
If FL Studio just crashed, start by finding its backup files and copying the promising candidates into a separate recovery folder. Leave the originals where they are. On a licensed installation, compare the copies from newest to oldest. The latest timestamp doesn't prove that file holds the work you need.
Autosave is a rotating recovery system. It isn't a permanent archive. It can keep a recent project state, but an FLP doesn't carry every recording and sample on its own. Get the song back first and leave folder cleanup and deletion for later.
Using the standard time-unlimited Trial? You can preserve files, but reopening saved projects requires purchase and unlock. Image-Line's Trial explanation states that restriction plainly. If your session is still open, save what you need and export usable audio before closing it. The recovery steps below don't get around that restriction.
Recover an FL Studio autosave in seven steps
- Find the active backup location. Check Browser > Backup and Options > File settings. If project-local backup is selected, look in the project's data folder too.
- Copy the candidates. Copy several promising FLPs to a separate local recovery folder outside the rotating Backup location. Leave their originals and the existing audio/data folders alone.
- Protect useful current work. If a useful session is still open and responding, first preserve the existing candidates, then use Save as with a separate name. Manual saves can create a newer backup, so don't assume Revert still points to the earlier one.
- Compare the copies. On a licensed installation, open candidates from newest to oldest. Check the expected arrangement, recent edits, plugins and audio. A missing data-folder warning calls for a path check before you delete anything.
- Choose the newest usable state. Keep looking if a candidate repeats the bad edit or won't load. A file that opens but has lost important work isn't the recovery you wanted yet.
- Save under a new name. Use Save as to give the recovered project a recognizable name in the working location you intend to use. Check its data-folder association instead of carrying on inside Backup.
- Validate the saved copy. Play the relevant Arrangements through to their endings, save, then close and reopen the recovered copy on a licensed installation. Keep the original and the candidates until this check passes. Standard Trial users can't complete the reopening step until purchase and unlock.
Image-Line's backup recovery procedure specifically tells you to copy files out before you try them. That stops normal backup rotation from replacing your candidates while you investigate. It doesn't copy the external audio those FLPs reference.
Understand what FL Studio autosave actually does
Backup (Autosave) lives in File settings. The mode controls when copies are made, Location controls where they go, and Maximum controls how many are kept. Depending on the operation, the backup system also covers overwritten supported files such as FLP, FST and ZIP. For song recovery, pick out the project's FLP candidates instead of treating everything in Backup as a complete song.
Autosave doesn't record every edit as you make it. A new copy may already contain the mistake you want to undo. A version you choose to keep is a separate decision; use the project-organization workflow for meaningful milestones and names.
The project-format reference keeps project state and sample data apart. An FLP references external samples. A zipped loop package gathers Sampler Channel and Audio Clip samples, but it leaves out arbitrary third-party sample libraries unless the plugin embeds the content. So a perfectly healthy FLP can still need missing recordings, samples or plugins.
Choose an autosave mode by behavior, not only the number
Open Options > File settings, or press F10 and select File. The current File Settings manual lists six modes:
| Mode | When copies are made | What to account for |
|---|---|---|
| Never | No backup files; a Hint Bar reminder after ten minutes without a manual save | A reminder is not a recovery copy. |
| Rarely | Manual saves and a 15-minute interval | Timed saves wait until playback stops. |
| Occasionally | Manual saves and a 10-minute interval | Timed saves wait until playback stops. |
| Regularly | Manual saves and a 5-minute interval | Timed saves wait until playback stops. |
| Frequently | Manual saves, critical operations and a 5-minute interval; also before adding plugins | Can save during playback. |
| Very frequently | A 1-minute interval and before risky operations | Can save during playback; the interval is not a guarantee that only one minute of work can be lost. |
Copying more often comes with a cost. Image-Line's performance guidance warns that Frequently and Very frequently can cause underruns while playing, especially in larger projects. If you hear glitches at save times, try a mode that waits for playback to stop and make deliberate manual saves at sensible pauses. Switching to Never means you no longer have automatic recovery at all.
Try a mode on a throwaway test project before trusting it with an important session. Make a recognizable change, let the selected trigger happen, and look at the resulting file and where it landed. On a licensed installation, open a copied backup to confirm what it kept. In the standard Trial you can confirm the saved file exists, but that isn't a reopening test.
Why a five-minute backup may be older than expected
Regularly and Frequently both mention five minutes, yet they behave differently. Regularly holds off a timed copy while playback continues, so a long loop can leave you with an older backup until you stop. Rarely and Occasionally follow the same playback rule.
Frequently can write during playback and before risky operations. Very frequently shortens the interval to one minute. Neither setting proves a useful copy exists, so check the destination, any write errors and what the candidate actually contains. A pile of timestamps is no substitute for a verified recovery.
Find the global or project-local backup folder
Start with the location selected in File settings instead of a path copied from an old video. The two choices are Always save to the global folder and Save to the project data folder if there is one.
For global backups, take the configured User data folder and look under FL Studio/Projects/Backup. With the standard Documents location, the path ends in Documents/Image-Line/FL Studio/Projects/Backup on Windows and macOS. Your account name, drive and any custom User data location decide the full path. The current file-location reference documents the Windows/macOS structure.
For project-local backups, the Project Settings documentation names a Backups subfolder next to the project data. If no Project Folder is set, the backup-location option falls back to global storage. Finding that folder beside one song doesn't mean another song uses it.
Different Image-Line references show both Backup and Backups. The current global File Settings path uses singular Backup; Project Settings uses plural Backups for project data. Look at the folder actually selected and created on your machine, and don't rename one to match a guide.
If the User data location changed, check both the current destination and the old one. FL Studio may offer to copy or migrate data when that setting changes, so don't assume everything stayed behind or that every copy moved cleanly. The project-folder migration guide handles deliberate moves. Recovery is the wrong moment to experiment with resetting paths.
Keep the active User data folder on suitable local storage. File Settings warns against putting it in iCloud, OneDrive and similar synchronized locations, because files can be locked, moved or written late. Keeping a separate backup of finished copies is fine; making a live sync folder your working User data location is a different thing.
Use Revert only when the latest backup is the right candidate
File > Revert to last backup loads the last backup, as the current File menu reference labels it. File Settings also calls that recovery point the last autosave. It takes you straight back to one copy and doesn't let you browse several possible versions.
Copy the existing candidates before you manually save a valuable state that's on screen right now. Several autosave modes also create a backup on manual save, so Save as can change which copy counts as the last backup. Keep useful current work under a separate name, then open the earlier candidate from your copied files instead of assuming Revert still points to it. The standard Trial restriction still applies: Revert does not unlock saved projects.
Browser > Backup is where recovery starts, and the FL Studio Browser guide explains the wider navigation tools. Make sure you're looking in the active global or project-local location, and not just the last folder you remember opening.
Compare older backups without disturbing their source data
Turn to older candidates when the latest one contains the bad edit, loads the failing plugin state or is missing the work you expected. Compare filenames and modified times. File size can flag something odd, but there's no universal minimum size for a valid project.
- Copy several candidates outside the rotating location, keeping the originals.
- Leave the existing project data folder, recordings and sample library untouched.
- On a licensed installation, open the copies from newest to oldest.
- If a copied FLP reports an invalid data folder, inspect the stored path before treating the project as corrupt.
- Choose the newest candidate that contains the needed work and behaves correctly.
- Use Save as with a new recovery name in the intended working location, then validate that saved file.
Copying an FLP to another directory can reveal a mismatch with a relative or specified data folder. Image-Line's invalid project data folder guidance explains the difference. Keep the original folder association and look at Options > Project general settings. Don't delete the data or clear its connection just to make a warning go away. Protect the required external audio separately before any later move.
Maximum limits how many automatic saves are kept. At the limit, older files are replaced one after another; the manual describes this retention for projects you have been working on. In the shared global location, work on other songs can replace an older candidate. Treat it as a rolling window, not an unlimited history, and don't assume each song gets a fixed quota of its own.
A deliberate Save new version creates a separately numbered FLP that stays outside that automatic rotation when you save in your normal working location. It still references audio: keeping Song_2.flp won't protect a recording you delete later. Raising Maximum also won't bring back files that have already rotated out.
Check a missing backup without making recovery harder
Leave the existing folders in place while you work through these possibilities:
- Mode: Never creates no backup files. Turning autosave on now can't rebuild a session that was never saved.
- Active location: check File settings and whether this project uses the project-local option.
- Previous location: inspect the old User data or project folder after a path change.
- Playback: Rarely, Occasionally and Regularly can postpone a timed save until playback stops.
- Retention: an older candidate may have been replaced after Maximum was reached.
- Write conditions: check error messages, free space, access to the destination and whether sync software moved or locked the files. Don't switch off system protections across the board.
An empty folder doesn't mean a recoverable project must be hiding somewhere else. A zero-byte candidate has no project payload, while a merely small file may still be valid. Preserve candidates instead of modifying them, check any separate copies you really made, and be ready for the possibility that no usable recovery state exists.
For a song you never manually named, look through autosaved candidates around the session time as well. Recovery only works if a usable copy was written and kept, and the same standard Trial opening restriction applies.
Separate missing dependencies, Trial restrictions and corruption
A missing sample or plugin message doesn't on its own prove the FLP is corrupt. The missing-files guidance points to data locations, search paths and installed plugins. An unlicensed trial plugin can also turn into a placeholder on reopening, which is a different issue from a missing installation or a corrupt project.
If copied candidates keep freezing at the same plugin or fail before opening, use the crash and corrupt-project workflow. It covers plugin isolation and Diagnostics on protected copies. Image-Line's corrupt-project instructions try an available backup before diagnostic repair and state that Diagnostics and project loading are unavailable in the Trial. Neither tool guarantees that missing data comes back.
Validate the recovered file before cleaning anything
Check the song length, the relevant Arrangements, the recent edit, recorded material and important plugins. Listen through to the endings, not only the first bar, and watch for missing-data warnings. After Save as to the chosen recovery name, save any corrections, then close and reopen that saved copy on a licensed installation.
Keep the damaged original, the copied candidates and their source data until the recovered file passes that check. In the standard Trial, preserve files and note the checks you ran in the open session, but don't record them as a successful reopen. Once recovery is stable, go back to the Workflow hub for organization and handoff.
Use three different kinds of protection
- Autosave: recent rotating copies for a crash or mistaken edit.
- Save new version: deliberate project-state checkpoints before structural changes.
- Separate backup: an independent copy of the project and required assets, with a restore check, for loss of the working location.
Two folders on the same failed drive don't give you two independent recovery options. Put recordings and externally referenced samples in the separate backup plan, and account for plugin libraries and licenses. Don't assume FLP versions or a ZIP include every dependency.
FL Cloud project backup is a separate save-triggered system with its own packaging and restore behavior. It doesn't upload every unsaved edit as you go. Keep that workflow apart from local autosave and from operating-system folder sync.
FL Studio autosave checklist
- The selected mode and its playback behavior are understood.
- The active global or project-local location is known.
- Maximum is treated as rotation, not permanent history.
- Candidates were copied before opening; originals and source data remain intact.
- A chosen recovered state has a distinct Save as name and correct data association.
- Dependencies and trial-plugin restrictions were distinguished from corruption.
- A licensed saved-file reopen check is complete, or the Trial reopening limit is noted.
- Deliberate versions and independently backed-up assets remain separate protections.
If recovery turns up a loading fault or plugin problem, follow the troubleshooting routes before you change any more files.
Frequently asked questions
Where does FL Studio save autosave backups?
The global option uses FL Studio/Projects/Backup under the configured User data folder. The project-local option uses the project's Backups subfolder when a Project Folder exists and otherwise falls back to global storage. Check File settings and the real project location instead of assuming an old default path.
How do I recover the last autosave in FL Studio?
On a licensed installation, File > Revert to last backup loads the latest copy. Preserve the existing candidates before you manually save useful current work, because a manual save can create a newer backup. To compare earlier points, open your copied candidates instead. Keep the original data intact; standard Trial reopening requires purchase and unlock.
Does FL Studio autosave during playback?
Rarely, Occasionally and Regularly hold timed backups until playback stops. Frequently and Very frequently can save while playing. Image-Line warns this can cause underruns in larger projects, so compare how your own session behaves instead of assuming the shortest interval is always best.
Why did an older backup disappear?
Once the Maximum retention limit is reached, older automatic saves get replaced. Other songs can use up the shared global pool too. Copy important candidates out of the rotation and keep deliberate FLP versions in your normal working location. Raising Maximum won't recreate files that were already replaced.
Can I recover a project I never manually saved?
Possibly, if autosave wrote a usable candidate and it's still kept. Look in the configured backup locations around the session time. A copy isn't guaranteed, and the standard Trial cannot reopen saved projects until purchase and unlock.
Does autosave back up all my samples?
No. An FLP doesn't include all external audio on its own. A zipped loop package gathers Sampler Channel and Audio Clip samples, with limits for third-party libraries unless the plugin embeds them. Keep required assets in a separate backup and check that they restore.
Does autosave replace Save new version or FL Cloud backup?
No. Local autosave rotates recovery states, Save new version keeps deliberate numbered FLPs, and FL Cloud backup is a separate save-triggered upload. Don't mistake any of them for a verified independent copy of every required asset.
