:::meta author=Docs-Team updated=2026-09-03 tags=volumes,storage,quota
:::
:::breadcrumb Docs > User Guide > Volumes
:::
:::reading-time
:::
Volumes are the persistent storage of the platform: named Docker volumes that survive restarts and redeploys, each attached to at most one service. The Volumes page manages them account-wide — creation, editing, file browsing, and archives — while attachment happens from the service side. This page explains the model, the page itself, and the rules that keep your data consistent.
:::toc
:::
The volume model
Every volume has a name (unique, up to 32 characters), a size in megabytes, a default bind path, and an access mode. The exclusivity rule is strict: a volume belongs to at most one service — attach attempts against a volume owned by another service are rejected with a clear message. The account-level quota is per service: the sum of its volumes' sizes cannot exceed the service plan's storage (plan GB × 1024 MB).
| Mode | Meaning |
| --- | --- |
| rw — Read / Write | The service can read and modify the volume's files |
| ro — Read Only | The service can read files but every write fails |
:::tip
Choose ro for reference data you want a service to consume but never mutate — a dataset, a certificate bundle, a shared config. Choose rw for everything the application owns: databases, uploads, caches.
:::
The Volumes page
The page lists your volumes in a table with a header row offering Refresh and Create volume, plus dismissible result alerts ("Volume created.", "Volume updated.", and their failure counterparts).
| Column | Contents |
| --- | --- |
| Name | The volume's unique name |
| Bind path | The default mount path inside the container, e.g. /data |
| Mode | A rw or ro chip |
| Size | The volume's size in MB |
| Status | Unused (outlined) when no service owns it, or the attached service name / count (filled) |
| Actions | Files, Download, Edit, Delete |
The actions per row:
• Files opens the Files — {volume} dialog listing the volume's contents with path, type, and size per entry.
• Download fetches the whole volume as a {name}.tar.gz archive.
• Edit opens the dialog pre-filled — name disabled with the helper "Name cannot be changed".
• Delete asks Delete volume "name"? This cannot be undone. and removes it permanently.
Creating and editing a volume
The Create volume dialog collects the four fields; edit mode changes only the submit button and locks the name:
| Field | Rules |
| --- | --- |
| Name | Required, unique, up to 32 characters, immutable after creation |
| Bind directory | An absolute container path such as /data or /var/lib/mysql |
| Size (MB) | A number, minimum 1, defaulting to 1024 |
| Access mode | Read / Write (rw) or Read Only (ro) |
Validation messages name the exact problem — "Bind path must be an absolute container path (e.g. /data)." — and the empty state "No volumes yet." invites you with a Create your first volume button.