FL Studio 
If FL Studio just crashed, start by finding its backup files and copying the promising candidates to a separate recovery folder. Leave the originals in place. On a licensed installation, compare the copies from newest to oldest: the latest timestamp is not proof that the file contains the work you need.
Autosave is a rotating recovery system, not a permanent archive. It can preserve a recent project state, but an FLP does not independently contain every recording and sample. Recover the song first; 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 makes that restriction explicit. If your session is still open, save what you need and export usable audio before closing it. The recovery-opening steps below are not a way around that restriction.
Recover an FL Studio autosave in seven steps
- Find the active backup location. Check Browser > Backup and Options > File settings. With project-local backup selected, inspect the project's data folder too.
- Copy the candidates. Copy several promising FLPs to a separate local recovery folder outside the rotating Backup location. Keep their originals and the existing audio/data folders untouched.
- Protect useful current work. If a useful session is still open and responsive, use Save as with a separate name after preserving the existing candidates. Manual saves can create a newer backup, so do not assume Revert will still target 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 needs a path check, not immediate deletion.
- Choose the newest usable state. Keep looking if a candidate repeats the bad edit or fails to load. A file that opens but has lost important work is not yet the recovery you wanted.
- Save under a new name. Use Save as to give the recovered project a recognizable name in the intended working location. Verify its data-folder association rather than continuing inside Backup.
- Validate the saved copy. Play the relevant Arrangements through their endings, save, then close and reopen the recovered copy on a licensed installation. Keep the original and candidates until this check succeeds; standard Trial users cannot complete the reopening step until purchase and unlock.
Image-Line's backup recovery procedure specifically tells you to copy files out before trying them. It prevents normal backup rotation from replacing your candidates while you investigate. It does not copy the external audio referenced by those FLPs.
Understand what FL Studio autosave actually does
Backup (Autosave) is in File settings. Its mode controls when copies are made, Location controls where they go, and Maximum controls retention. Depending on the operation, the backup system also covers overwritten supported files such as FLP, FST and ZIP. For song recovery, identify the project's FLP candidates rather than treating every item in Backup as a complete song.
Autosave is not a continuous recording of every edit. A new copy may already contain the mistake you want to undo. A version you deliberately keep is a different decision; use the project-organization workflow for meaningful milestones and names.
The project-format reference separates project state from sample data. An FLP references external samples. A zipped loop package gathers Sampler Channel and Audio Clip samples, but not arbitrary third-party sample libraries unless the plugin embeds the content. A healthy FLP can therefore 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. |
More frequent copying has a tradeoff. Image-Line's performance guidance warns that Frequently and Very frequently can cause underruns while playing, especially in larger projects. If glitches appear at save times, compare a mode that waits for playback to stop and make deliberate manual saves at suitable pauses. Do not switch to Never and assume you still have automatic recovery.
Choose a mode on a disposable test project before trusting it with an important session. Make a recognizable change, allow the selected trigger to occur, and inspect the resulting file and its location. On a licensed installation, open a copied backup to confirm what it preserved. In the standard Trial, you can inspect the saved file's existence, but that is not a reopening test.
Why a five-minute backup may be older than expected
Regularly and Frequently both mention five minutes, but they are not interchangeable. Regularly postpones a timed copy while playback continues. A long loop can therefore leave you with an older backup until you stop. Rarely and Occasionally have the same playback condition.
Frequently can write during playback and before risky operations. Very frequently shortens the interval to one minute. Neither setting proves that a useful copy exists: check the destination, write errors and the candidate's contents. More timestamps are not a substitute for a verified recovery.
Find the global or project-local backup folder
Start with the location selected in File settings, not 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 beneath 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 determine 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 alongside project data. If no Project Folder is set, the backup-location option falls back to global storage. A folder existing beside one song does not prove another song uses it.
You may see Backup and Backups in different Image-Line references. The current global File Settings path uses singular Backup; Project Settings uses plural Backups for project data. Check the folder actually selected and created on your machine rather than renaming one to match a guide.
If the User data location changed, inspect both the current destination and the previous one. FL Studio may offer to copy or migrate data when that setting changes; do not assume either that everything stayed behind or that every copy moved successfully. The project-folder migration guide handles deliberate moves. Recovery is not the time to reset paths experimentally.
Keep the active User data folder on suitable local storage. File Settings warns against using iCloud, OneDrive and similar synchronized locations for it because files can be locked, moved or written late. A separate backup of completed copies is different from making a live sync folder the working User data location.
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. This is a direct return to one copy, not a browser for several possible versions.
Copy the existing candidates before manually saving a valuable state currently on screen. Several autosave modes also create a backup on manual save, so Save as can change which copy is now the last backup. Preserve 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 the recovery entry point; the FL Studio Browser guide explains the wider navigation tools. Make sure you are looking in the active global or project-local location, not merely the last folder you remember opening.
Compare older backups without disturbing their source data
Use older candidates when the latest one contains the bad edit, loads the failing plugin state or does not contain the expected work. Compare filenames and modified times; file size can flag something unusual, but there is 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 expose a relative or specified data-folder mismatch. Image-Line's invalid project data folder guidance explains the distinction. Preserve the original folder association and inspect Options > Project general settings; do not delete the data or clear its connection merely to dismiss a warning. Keep required external audio separately protected before any later move.
Maximum limits retained automatic saves. At the limit, older files are successively replaced; the manual describes this retention for projects you have been working on. In the shared global location, work on other songs can therefore replace an older candidate. Do not treat it as an unlimited history or assume a fixed quota is reserved for each song.
A deliberate Save new version creates a separately numbered FLP, outside that automatic rotation when you save in your normal working location. It still references audio; keeping Song_2.flp does not protect a recording you later delete. A higher Maximum also does not restore files that have already rotated out.
Check a missing backup without making recovery harder
Keep existing folders in place while you work through these possibilities:
- Mode: Never creates no backup files. Enabling autosave now cannot reconstruct 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 it. Do not disable system protections indiscriminately.
An empty folder is not evidence that there must be a hidden recoverable project elsewhere. A zero-byte candidate contains no project payload, while a merely small file may still be valid. Preserve candidates rather than modifying them, check any separate copies you actually made, and be prepared for the possibility that no suitable recovery state exists.
For a song you never manually named, inspect available autosaved candidates around the session time too. Recovery is possible only if a usable copy was written and retained; the same standard Trial opening restriction applies.
Separate missing dependencies, Trial restrictions and corruption
A missing sample or plugin message does not by itself prove the FLP is corrupt. The missing-files guidance points to data locations, search paths and installed plugins. An unlicensed trial plugin can also become a placeholder on reopening; that is different from a missing installation or a corrupt project.
If copied candidates repeatedly freeze 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 recovery of missing data.
Validate the recovered file before cleaning anything
Check song length, relevant Arrangements, the recent edit, recorded material and important plugins. Listen through the endings, not just the first bar. 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, copied candidates and their source data until the recovered file passes that check. In the standard Trial, preserve files and document any open-session checks without claiming successful reopening. Only after recovery is stable should you return 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 are not two independent recovery options. Include recordings and externally referenced samples in the separate backup plan, and account for plugin libraries and licenses. Do not 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 does not continuously upload every unsaved edit. Keep that workflow distinct from local autosave and from operating-system folder synchronization.
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 Trial limitations are recorded honestly.
- Deliberate versions and independently backed-up assets remain separate protections.
If recovery exposes a loading fault or plugin problem, follow the troubleshooting routes before changing more files.
Frequently asked questions
Where does FL Studio save autosave backups?
The global option uses FL Studio/Projects/Backup beneath the configured User data folder. The project-local option uses the project's Backups subfolder when a Project Folder exists; otherwise it falls back to global storage. Check File settings and the actual 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 existing candidates before manually saving useful current work, because a manual save can create a newer backup. To compare earlier points, open your copied candidates instead. Keep original data intact; standard Trial reopening requires purchase and unlock.
Does FL Studio autosave during playback?
Rarely, Occasionally and Regularly postpone timed backups until playback stops. Frequently and Very frequently can save while playing. Image-Line warns that this can cause underruns in larger projects, so compare behavior on your own session rather than assuming the shortest interval is always best.
Why did an older backup disappear?
At the Maximum retention limit, older automatic saves are replaced. Other songs can consume the shared global pool too. Copy important candidates outside rotation and keep deliberate FLP versions in the normal working location. Raising Maximum does not recreate files already replaced.
Can I recover a project I never manually saved?
Possibly, if autosave wrote a usable candidate and it is still retained. Inspect the configured backup locations around the session time. There is no guarantee of a copy, and the standard Trial cannot reopen saved projects until purchase and unlock.
Does autosave back up all my samples?
No. An FLP does not independently include all external audio. 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 verify restoration.
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. None should be mistaken for a verified independent copy of every required asset.
