Detach or delete an App Storage volume
What detaching does
Detach and keep files switches the app back to its original local files. It does not copy changes from the attached volume back to local storage. The remote volume retains those changes.
If you have used the attached volume for new uploads or database writes, the original local files may be older. Plan how to transfer the current data before returning an app to local storage. For a database, use the database's export/import workflow or arrange an assisted migration with support.
Example: changes made after attachment
Your local volume contains files A and B when you attach storage. The panel copies A and B to App Storage. You then add file C through the app, so App Storage contains A, B and C while the retained local volume still contains A and B.
After detaching, the app sees A and B again. C has not been deleted: it remains on the detached App Storage volume. To keep using C locally, its data must be transferred back through a planned migration. The same principle applies to database records written after attachment.
Do not restart against the older local copy expecting it to contain the latest changes. Arrange the data transfer first; contact support if you need help returning the app to local storage.
Detach a volume
- Stop the app and confirm it is Stopped.
- Open Storage → App Storage and find the volume assigned to the intended app and path.
- Select Detach and keep files.
- Wait for detachment to finish. Do not start the app while storage or SFTP recovery is pending.
- Confirm the app will use the local data you expect before starting it again.
The detached volume still consumes pool capacity. Its contents remain there until you explicitly delete it. Do not assume a data-bearing detached volume can be reassigned to any arbitrary app without review; contact support if you need to reuse or migrate it.
Delete a volume
Deletion is for an unattached volume whose contents you no longer need. Select Delete volume, read the confirmation, and enter the requested confirmation value. Capacity remains reserved until the storage node acknowledges deletion.
Deleting files, deleting a volume and cancelling billing are different actions. To retire a pool, handle every attached app first, delete unwanted volumes, then close the empty pool when Close empty pool becomes available. Paid pools may need billing cancellation completed before closure.