Your projects
Save projects and keep your audio available
A local copy, a cloud project and a downloaded WAV serve different purposes. Check what has actually been saved before closing your work or changing devices.
AI history belongs to the current project. A local project keeps requests and results in the browser; a cloud project keeps them with the account and stores result files in object storage. Signing in does not transfer an empty project: synchronization starts after the first meaningful change. Confirmed chat clearing removes unused results while preserving audio already referenced by the project.
Local, cloud or downloaded?
| Location | What to know |
|---|---|
| On this device | The project lives in this browser's site data. Another browser or device does not automatically see it. |
| Cloud | The project synchronises with your account. Wait for both changes and audio uploads to finish. |
| Downloaded file | A separate copy on disk. WAV contains sound; project export contains editable state. |
Guest mode is not a substitute for a backup. Clearing site data, using a private window or running out of storage can affect local availability. Keep important material outside the browser before clearing it.
Complete a save
- Press Save after an important change.
- Read the status bar. “Saved locally” does not mean the cloud has received the update.
- For a local project, use Move to cloud in Library when you need it on other devices.
- Wait for synchronisation confirmation. If it fails, check the connection and save again.
- For important work, also export the project and required audio. Check that the downloaded files actually open.
Do not close the browser immediately after adding a large WAV. Uploading the audio and saving the project structure may finish at different times.
Keep separated stems
Add the selected stems from the task to its original project and wait for saving to complete. Used audio files are linked to the saved project. Merely previewing a task does not establish that lasting connection.
Unused results have a retention period shown in the task. Deleting a task-history entry and removing a track from a project are different operations. Files needed by a saved project are protected independently of the task-history entry.
If cloud saving fails after you add stems, press Save again. Temporary draft protection should not be treated as a long-term archive.
Return to an earlier version
Open the project in Library and view its Version history. Load the list, choose the intended revision and restore it. The restored version opens for review first. Listen and save it to make it current.
Before a major experiment, make a project copy or named version. Avoid restoring an arbitrary revision over unsaved work until you decide which changes to keep.
Delete carefully
Muting with M does not remove material and is useful for experiments. Deleting a clip changes the arrangement; deleting a project removes the work described in the confirmation. Moving a cloud project onto the device can also remove the cloud copy and history, so read the warning before confirming.
Physical cleanup of unused audio happens separately and accounts for references from saved projects and supported revisions. Space may therefore not be released immediately. Do not rely on a file possibly remaining in storage as a way to recover deleted work.