Corrupt .flp / Project

Please report Windows related issues here

Return to “Technical Support (Windows)”

Forum rules

ALL posts made in this forum are 'Private' so that only you and staff can see them. This allows sharing of personal data, projects and other information. Posts are generally made public after they are marked 'Solved' AND there was no personal data contained in them. If you don't want your post made public let the team know.

We know it's frustrating when things don't work. However, please help us to help you by following these suggestions:

  1. Update - Before trying anything else. Download and install the latest version of FL Studio from here. Your bug may be fixed already!
  2. Update plugins - If you are using 3rd party plugins. Look at crash logs for their names. Install the latest version for any you spot. See also Plugins Behaving Badly
  3. Simple clear explanation - Explain what you are doing, or trying to do, and exactly what is happening.
  4. Specific information - a) FL Studio version & build number, b) what you are doing and what happens exactly, c) step-by-step instructions how reproduce the problem.
  5. Screenshots - Another great way to demonstrate issues. Get a free screenshot app here. Include images using the 'Attachments' tab, at the bottom of the post edit window.
  6. A video - The best way of demonstrating many issues. Windows 10 includes an integrated screen recorder, see here OR get a free free recorder here. Include mp4 videos to your post from the 'Attachments' tab, at the bottom of the post edit window.
  7. Use English - Google Translate your post. Short simple sentences in your original language translate best. We are happy to work this way, no need to worry.

NOTE: Technical Support is ONLY available Monday - Friday (9 am to 5 pm Central European Time), it can take a few days to get a response depending on the level of demand. Thank you for your patience.
[You can only see part of this thread as you are not logged in to the forums]
Site Admin
Tue Jan 15, 2008 3:50 am


Corrupt .flp / Project

Projects usually become corrupted if a plugin (3rd party of course) crashes while FL Studio is saving.


If this is a recent project, you may have a working backup of the project available. Backups can be accessed from the FL Studio Browser in the 'Backup' folder. The last 20 autosaves will be available in this location.

If there aren't any available backups or the backup isn't recent enough you can try the following to confirm whether or not the project is recoverable.

1. Navigate to the general installation location(s) of your vst plugins.
2. Temporarily move the plugins folder(s) to another location.
3. Load the project.

Follow the above steps carefully to ensure that FL Studio is unable to load any third party plugins contained in the project. If the project loads after relocating your plugins folder(s) that would indicate the issue is plugin related. If the project fails to load and continues to display a corrupt project error it's likely corrupt.


If you were able to load the project you must identify the problematic plugin. There isn't a simple way to identify the problematic plugin, so it can be tedious depending on how many plugins you have in the project.

1. Keep note of the third party plugins used in the project.
2. Move your plugins folder(s) to their original locations.
3. Relocate each plugin .dll, one at a time, and load the project.

Continue step '3' until the project loads and you've pinpointed the problematic plugin, which you can then delete from the project.

FL Studio 11 and under: (FL Studio 12+ diagnostic does not currently have this facility).

There is a recovery function in the tech-support diagnostic program.
You should systematically remove each plugin in the .flp until you find the one that was causing the problem. Once the offending plugin has been deleted the .flp should load.

The FL Studio support team.

Return to “Technical Support (Windows)”