# Create Local Storage service


## Create Using Import YAML

```yaml title="zerops-import.yaml"
services:
  - # Local Storage service
    hostname: vol
    type: local-storage:single@1
```

Import the file with the [zCLI](/references/cli):

```sh
zcli project service-import zerops-import.yaml
```

Local Storage runs in a single container mode only — there is currently no highly available mode. Read the [availability trade-offs](/local-storage/tech-details#availability-and-failure-behavior) before you store critical data on it; automated [backups](/local-storage/how-to/manage#backups) are enabled by default and strongly recommended.

To mount the volume into a runtime service, add the `volume` field to the runtime service's `zerops.yaml`. See [Mount to a service](/local-storage/how-to/connect).

## Create Using Zerops GUI

Go to your project dashboard and choose **Add new service** in the left menu in the **Services** block, then add a new **Local Storage** service.

### Set a Hostname

Enter a unique service identifier like "vol", "data" etc. Runtime services reference the volume by this hostname in their `zerops.yaml`.

- Maximum 25 characters
- Must contain only lowercase ASCII letters (a-z) or numbers (0-9)
- Must be unique within the project

:::note
The hostname is fixed after the service is created. It can't be changed later.
:::

### Set Auto Scaling Configuration

Configure vertical auto scaling parameters to control resource allocation and costs. The **maximum disk size is the capacity of the volume**: the volume can grow up to the configured disk maximum, and what you actually store is billed as the service's disk usage.