There are several different things that can cause project corruption in Adobe Captivate. Some of these include:

  • Saving to a network drive
  • Low memory when saving
  • Large project

Saving Adobe Captivate projects to a network drive

All Adobe Captivate projects should be saved and worked on from a local drive. Saving projects and working on projects can cause issues, due to network latency. Adobe Captivate could send a command to save the project, then close the file; however, due to network latency, the file could get closed before all the bits to save are transmitted across to the file. This will cause a failure in the continuity of the data, thus causing a corrupt file.

Low memory when saving

Computers have a finite amount of resources that they can use to run all applications, including the OS. If for some reason, the computer Adobe Captivate is being used on has a low amount of resources available, due to other programs running, this can cause a shortage of resources on the system. By having a low amount of resources on the system, this can inhibit Adobe Captivate from being able to save the file correctly and increasing the chance of project corruption. To prevent this, make sure that all unnecessary applications are closed down on the system. As well as closing down all unnecessary applications, it is also strongly suggested that the machine be checked for any spyware or possible viruses.

Large projects

Large projects also have a greater chance of being corrupted due to the amount of data. It is strongly suggested, for file manageability as well as user experience, that Adobe Captivate projects remain at a reasonable size. This will greatly reduce the chance for project corruption and increase the user's experience.


This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy