Storage

Openinary writes to local disk by default. Set these five variables and it writes to your bucket instead.

STORAGE_REGION=us-east-1
STORAGE_ACCESS_KEY_ID=AKIAIOSFODNN7EXAMPLE
STORAGE_SECRET_ACCESS_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
STORAGE_BUCKET_NAME=my-openinary-bucket
STORAGE_PUBLIC_URL=https://my-openinary-bucket.s3.us-east-1.amazonaws.com

The provider is detected from STORAGE_ENDPOINT: set it for anything that is not AWS S3, leave it unset for AWS. Only these exact names are read, there is no fallback to S3_-prefixed ones.

The bundled Docker Compose file does not pass these through. Its services declare no STORAGE_* entries and no env_file, so putting them in the root .env does nothing and the container silently falls back to local disk. Add them to the service’s environment: block yourself:

services:
  openinary:
    environment:
      - STORAGE_REGION=${STORAGE_REGION}
      - STORAGE_ACCESS_KEY_ID=${STORAGE_ACCESS_KEY_ID}
      - STORAGE_SECRET_ACCESS_KEY=${STORAGE_SECRET_ACCESS_KEY}
      - STORAGE_BUCKET_NAME=${STORAGE_BUCKET_NAME}
      - STORAGE_PUBLIC_URL=${STORAGE_PUBLIC_URL}

Platforms that inject environment variables directly (Railway, Coolify, Dokploy) need nothing extra. From source, they are read from apps/api/.env.

Variables

Variable	Default	Description
`STORAGE_ACCESS_KEY_ID`		Access key ID. Never commit it
`STORAGE_SECRET_ACCESS_KEY`		Secret access key. Keep it out of logs and client code
`STORAGE_BUCKET_NAME`		Bucket files are stored in
`STORAGE_REGION`	`auto`	Region identifier. `auto` is what R2 expects, so AWS and other region-bound providers must set it explicitly
`STORAGE_ENDPOINT`		Endpoint for non-AWS providers. Omit for AWS S3
`STORAGE_PUBLIC_URL`		Base URL used to build file URLs. Point it at your CDN or custom domain to avoid exposing raw S3 URLs
`STORAGE_MAX_SOCKETS`	`50`	Simultaneous connections to the provider. Raise it if you hit connection pool exhaustion
`STORAGE_CONNECTION_TIMEOUT`	`0`	Connection timeout in ms. `0` means no timeout
`STORAGE_REQUEST_TIMEOUT`	`0`	Request timeout in ms. Use `300000` or more for large uploads
`STORAGE_SOCKET_TIMEOUT`	`0`	TCP socket timeout in ms

Endpoints by provider

Provider	`STORAGE_ENDPOINT`	`STORAGE_REGION`
AWS S3	omit	your region, e.g. `us-east-1`
Cloudflare R2	`https://<account-id>.r2.cloudflarestorage.com`	`auto`
MinIO	`http://minio.example.com:9000`	`us-east-1`
DigitalOcean Spaces	`https://nyc3.digitaloceanspaces.com`	region of the space
Wasabi	`https://s3.wasabisys.com`	your region

Backblaze B2 and other S3-compatible services work the same way: set their endpoint and a region.

Production timeouts

Defaults leave every timeout off, which is fine on a fast link and unhelpful when the provider stalls. A reasonable production set:

STORAGE_MAX_SOCKETS=100
STORAGE_CONNECTION_TIMEOUT=5000
STORAGE_REQUEST_TIMEOUT=30000
STORAGE_SOCKET_TIMEOUT=60000

Raise STORAGE_REQUEST_TIMEOUT well past 30000 if you accept large video uploads.

Quick Start

Run Openinary with local or S3 storage.

Upload & Cache Warming

Upload files and prewarm the transformation cache.

Get started

Transformations

Upload & storage

Cloud

Self-hosting

Resources

Variables

Endpoints by provider

Production timeouts

Quick Start

Upload & Cache Warming

​Variables

​Endpoints by provider

​Production timeouts

​Related

Quick Start

Upload & Cache Warming

Variables

Endpoints by provider

Production timeouts

Related