# Connect an S3-compatible storage (Custom)

> Set the storage type to Custom to use Cloudflare R2, DigitalOcean Spaces, Wasabi, Backblaze B2 or MinIO, with settings per provider.

Source: https://n1ed.com/docs/cloud-storage/s3-compatible  
Section: File manager > Cloud storage > S3-compatible (Custom)  
Updated: 2026-09-26  
Every page of n1ed.com has a Markdown copy at its URL + `.md` (`index.md` after a URL that ends in `/`); all of them are in one file: https://n1ed.com/llms-full.txt

> This article is for N1ED Premium users who purchased the additional option to support cloud storage.

Besides [Amazon S3](https://n1ed.com/docs/cloud-storage/amazon-s3), Flmngr works with **any S3-compatible storage** — Cloudflare R2, DigitalOcean Spaces, Wasabi, Backblaze B2, a self-hosted MinIO or rclone server, and more. You configure it in the same **Cloud storages** dialog of your dashboard: pick the storage, open **Edit credentials**, and switch the storage type from **Amazon S3** to **Custom**.

## The Custom form

- **Endpoint URL** — the S3 API URL of your storage, e.g. `https://<account>.r2.cloudflarestorage.com`. Buckets are accessed in path style (`endpoint/bucket/object`), which every S3-compatible server supports.
- **Bucket** — the bucket (or container/space) name. Create it on the provider side first.
- **Key / Secret** — the access key id and secret. Most providers have a dedicated screen to create an S3 access key pair (e.g. R2 "API tokens", DigitalOcean "Spaces keys", Google "HMAC keys").
- **Server has no per-object ACL or folder markers** — a checkbox for compatibility. Some servers do not implement per-object ACLs or empty-folder marker objects; without this box ticked, copy / move / rename and creating empty folders fail on them. Turn it **on** only for such servers (see the table).

## Settings per provider

| Provider | Endpoint URL | "No per-object ACL / folder markers" | Notes |
|---|---|---|---|
| **MinIO** (self-hosted) | `https://minio.example.com` | Off | Full S3 server. Create the bucket first. |
| **rclone serve s3** (self-hosted) | `https://your-host` | **On** | Serves a plain directory as S3; no ACLs / markers. |
| **Cloudflare R2** | `https://<account>.r2.cloudflarestorage.com` | **On** | Create an R2 API token for the key/secret. |
| **DigitalOcean Spaces** | `https://<region>.digitaloceanspaces.com` | Off | e.g. `sgp1`, `nyc3`. Use a Spaces key pair. |
| **Wasabi** | `https://s3.<region>.wasabisys.com` | Off | Full S3 compatibility. |
| **Backblaze B2** | `https://s3.<region>.backblazeb2.com` | Off | Use the S3-compatible application key. |
| **Google Cloud Storage** | `https://storage.googleapis.com` | Off | Needs HMAC interoperability keys. Note: deleting a folder is not supported over the S3 API — for full GCS support ask us about the native Google option. |

## Public file URLs

To display and download uploaded files, the storage must serve them publicly (like a public bucket), and your Flmngr configuration's `urlFiles` must point at that public base URL — usually `<endpoint>/<bucket>/`. This is the same `urlFiles` rule as for [Amazon S3](https://n1ed.com/docs/cloud-storage/amazon-s3), and CORS still needs to allow your editor's origin so the image editor can read images.
