Where are LastCUE backups stored, and can I move them?
Updated October 9, 2026
LastCUE saves backups locally. The default backup directory is ~/LastCUE/backups, where ~ means your operating-system user folder. You can choose another location in Settings.
The path currently displayed in the app is the one to use. If you changed it earlier, your backups may be in that custom folder rather than the default directory.
How do I find the backup folder?
Open Settings and check Custom backup directory. You can also select a saved version in backup history and use the folder-opening action to locate that version.
Typical default paths are:
| Platform | Default path example |
|---|---|
| Windows | C:\Users\YourName\LastCUE\backups |
| macOS | /Users/YourName/LastCUE/backups |
Your user-folder name or location can differ. A backup stored on an external disk also requires that disk to be connected.
Does changing the folder move existing backups?
Choosing another backup directory changes the location used for future backups and lets LastCUE read an existing backup library there. It is not an automatic copy of every previous backup folder.
Keep the original files until you have copied the complete library and confirmed that LastCUE can find the intended versions at the new location. Selecting the new folder in Settings can load the backup history available for the current account or guest identity.
Can I copy a backup to another disk or computer?
Yes, but the files required depend on the backup format. Older standalone backups can contain their own payload. Newer shared-object backups store version manifests and file contents separately.
For a complete copy of a newer backup library, preserve the library root and its contents, including:
snapshots, which contains the saved version manifests;
objects, which contains the backed-up file contents;
.lastcue, which contains repository information.
Pause backup, restore, and deletion work before copying. Copy the entire library to the new location, then select that library folder in LastCUE and check the relevant history. Keep using the account that owns those versions where applicable.
Why is copying one .lcue file not always enough?
In a shared-object backup, the .lcue file describes the version and references content in the repository. It is not necessarily a standalone archive containing the music and every other file.
If you copy only that manifest, LastCUE may be unable to read or restore the referenced contents. This also applies to Full backups that include music.
How should I delete versions or protect against disk failure?
Use LastCUE's backup-history delete action so shared contents still required by retained versions remain available. Avoid manually removing files from the objects directory.
A local backup on the same physical disk as its source remains vulnerable to that disk failing. Keep a complete additional copy on another disk when you need protection against that failure. LastCUE does not automatically provide an online backup copy.