Causes of Corrupt or Locked Audacity AUP3 Files

Audacity's transition to the .aup3 format introduced a unified SQLite database structure designed to store entire audio projects within a single file. While this modern format eliminated the common missing-file issues of older Audacity versions, users still frequently encounter errors where projects become corrupted or stuck in a locked state. This article outlines the primary causes behind these issues, detailing how database locking mechanisms, improper shutdowns, storage conflicts, and background software can compromise .aup3 project files.

1. Lingering SQLite Lock and Temporary Files

Audacity relies on SQLite's Write-Ahead Logging (WAL) mechanism to manage data safely during an active session. When you open a project, Audacity generates two temporary companion files in the same directory: project.aup3-wal and project.aup3-shm. These files temporarily store writes and index state information. If Audacity does not close properly, these companion files are not cleanly merged and deleted. As a result, SQLite retains an active lock on the main database, prompting a "project is locked" or read-only error upon subsequent launch attempts.

2. Cloud Storage and Network Drive Syncing

Saving, opening, or editing .aup3 files directly on cloud-synced folders (such as Google Drive, OneDrive, or Dropbox) or Network Attached Storage (NAS) is a leading cause of file corruption. SQLite requires rapid, low-latency disk writes with precise file-locking capabilities. Cloud synchronization clients frequently attempt to upload the .aup3, -wal, and -shm files mid-write, creating a file lock race condition that leads to interrupted database transactions and data corruption.

3. Abrupt System Crashes and Forced Terminations

If your computer loses power, your operating system crashes, or Audacity is forcefully terminated (via Task Manager or Force Quit) while performing a write operation, the open database transaction is interrupted. While SQLite has built-in recovery protocols, sudden write failures during intensive tasks—such as applying complex effects, exporting, or massive undo/redo history updates—can corrupt the database header or leave orphaned pointers, rendering the file unreadable.

4. Premature Disconnection of External Storage

Working directly from external hard drives, USB thumb drives, or SD cards poses a significant risk to project integrity. If the physical storage device is unplugged before Audacity has completely finalized its writes, or if the drive's power-saving mode puts it into a suspended state during processing, the database write stream breaks instantly. This leaves the file header damaged and flags the project as corrupt.

5. Antivirus and Real-Time Security Scanning

Antivirus software or endpoint protection utilities with aggressive real-time scanning can lock files as soon as they are modified on the disk. Because Audacity continuously updates the .aup3 database and its associated temporary files, a background security scan can temporarily hijack file access privileges. If Audacity is denied access to its own project file during an essential write routine, it may fail silently or corrupt the file structure.

6. Drive Exhaustion and Bad Sectors

When a storage volume runs out of free disk space during recording or editing, Audacity cannot complete the temporary buffer writes required to maintain the database structure. This sudden out-of-space condition can break the index of the .aup3 file. Similarly, underlying hardware defects—such as bad sectors on a traditional hard drive or failing flash memory cells—can physically alter bits in the database, resulting in irreversible corruption.