# Storage drivers

> Storage backends for the self-hosted GitHub Actions cache server: local filesystem, S3 (AWS, RustFS, MinIO, Cloudflare R2), Google Cloud Storage and Azure Blob Storage.

Source: https://gha-cache-server.falcondev.io/storage-drivers

The storage driver holds the cache payloads. Pick it with [`STORAGE_DRIVER`](https://gha-cache-server.falcondev.io/configuration.md#storage_driver).

| Driver | `STORAGE_DRIVER` | Direct downloads | Best for |
| --- | --- | --- | --- |
| [File system](https://gha-cache-server.falcondev.io/storage-drivers/file-system.md) | `filesystem` (default) | No | One host with local NVMe, the fastest setup |
| [S3, RustFS, MinIO, R2](https://gha-cache-server.falcondev.io/storage-drivers/s3.md) | `s3` | Yes | Several replicas, any S3 compatible store |
| [Google Cloud Storage](https://gha-cache-server.falcondev.io/storage-drivers/google-cloud-storage.md) | `gcs` | Yes | Runners on GCP |
| [Azure Blob Storage](https://gha-cache-server.falcondev.io/storage-drivers/azure-blob-storage.md) | `azblob` | Yes | Runners on Azure |

## Object storage

On S3, GCS and Azure Blob Storage, parts are uploaded through presigned URLs, so the credentials must be able to sign. Without that, uploads fall back to multipart.

The server trusts an object it has seen to exist for a minute instead of checking storage on every cache hit. Data deleted behind the server's back (another replica, a bucket lifecycle rule) can still be promised to a runner for up to a minute.