Audacity Automatic Crash Recovery Explained

When Audacity closes unexpectedly due to a system crash, power outage, or software freeze, relaunching the application triggers an automated recovery process designed to restore your unsaved work. This article explains how Audacity detects these interrupted sessions, how it reconstructs your audio timeline using temporary autosave files, and the exact steps you should take to safeguard your recovered data.

Upon startup, Audacity checks its working directory for session files that were not closed cleanly. In modern versions using the unified .aup3 database format, the software identifies temporary write-ahead log files (.aup3-wal and .aup3-shm) or autosave records indicating that an editing session ended abruptly.

Before loading the standard interface, Audacity intercepts the startup routine and presents the Automatic Crash Recovery dialog box. This window displays a list of all recoverable projects detected on your drive, along with the date and time they were last modified.

At this prompt, you are presented with two primary actions:

Once a project is recovered and displayed on your screen, it remains in a vulnerable temporary state. Audacity does not automatically overwrite or finalize the original project file during the recovery operation.

To complete the recovery process, you must immediately save the project manually by navigating to File > Save Project > Save Project (or Save Project As). This action commits the recovered audio data to a permanent .aup3 project file and clears the temporary recovery cache, ensuring your restored work is securely preserved.