# Manage Docker files and volumes

> Understand persistent volumes, container filesystems, archive downloads, replacements, and safe file changes.

Docker apps expose two different file views. Choosing the wrong one can cause a change to disappear.

## Volume Files

**Volume Files** contains persistent app volume data. Use it for uploads, databases or media stored on a mounted volume, and other data intended to survive restarts and redeploys.

The file manager can browse, create, edit, upload, download, rename, copy, move, delete, archive, and extract entries. The volume backup/download action prepares an archive. Keep the tab open while large transfers run.

Replacing a whole volume archive overwrites persistent content. Download the current volume first, verify the replacement archive locally, and do not interrupt the upload.

## Container Filesystem

**Container Filesystem** shows live files inside a running container. Changes here can disappear when the app restarts or redeploys because containers are replaceable.

Use it for inspection or emergency diagnosis. Put permanent application changes in the source repository or image. Put durable runtime data on a declared persistent volume.

## Before changing data

1. Identify which container and volume the application actually uses.
2. Stop writes or place the app in maintenance mode for consistency-sensitive data.
3. Download a current copy or create a [service backup](/docker/backups/).
4. Make one change.
5. Start or resume the app and test it.

Avoid copying a live database's raw files unless that database's own documentation says the method is safe. Prefer an application-level or database-native export.

## Storage limits

Open **Usage** to check storage consumption. Deleting files inside a container may not reduce image or build-cache use, and deleting files from a volume is permanent. If usage remains unexpected after cleanup, collect the app name, volume name, and displayed usage for support.