Edge Storage

Edge Storage is NVMe-backed object storage that sits behind the CDN. You create a storage zone, upload objects into it, and they are served from a CDN hostname worldwide.

Storage zones

A storage zone is the unit of storage, and it doubles as your bucket name when you use the S3 API. Create one from Storage → Add storage zone in the dashboard. You will pick:

A name. This becomes your bucket name and S3 access key, so it has to be unique.
A main region. Where the authoritative copy lives.
Replication regions (optional). Additional regions that hold a synchronised copy, billed per replicated region.

Every zone is created with a pull zone attached, which is what serves its contents publicly. You do not need to configure an origin — the storage zone is the origin.

Regions

Region	Code	S3 access
Frankfurt, DE	`DE`	Yes
London, UK	`UK`	Yes
Stockholm, SE	`SE`	Yes
New York, US	`NY`	Yes
Los Angeles, US	`LA`	Yes
Singapore, SG	`SG`	Yes
Sydney, AU	`SYD`	Yes
São Paulo, BR	`BR`	No
Johannesburg, ZA	`JH`	Yes

Region matters for more than latency: it determines your hostnames. A zone in Frankfurt is not reachable at a New York endpoint.

Getting files in

There are four ways to upload, and they all write to the same objects:

The dashboard. Drag and drop into the file browser on the zone's page — fine for one-off files.
S3 SDKs and tools. The usual choice for programmatic use. See the S3-compatible API.
The native Storage API. A simple HTTP API. See Storage API & FTP.
FTP. Useful with existing clients and legacy tooling.

Getting files out

Objects are served over your zone's CDN hostname, which appears on the zone page in the dashboard. The path maps directly: an object stored at media/video.mp4 is served at https://your-cdn-hostname/media/video.mp4.

Do not serve public traffic from the storage or S3 endpoints. Those are management interfaces, they require credentials, and they are not distributed to the edge.

Storage is not video encoding

Uploading an MP4 to a storage zone stores an MP4. It is not transcoded, no bitrate ladder is produced, and it does not appear in your video library. If you want adaptive bitrate streaming, that is Video CDN.

Storage zones

A storage zone is the unit of storage, and it doubles as your bucket name when you use the S3 API. Create one from Storage → Add storage zone in the dashboard. You will pick:

A name. This becomes your bucket name and S3 access key, so it has to be unique.

A main region. Where the authoritative copy lives.

Replication regions (optional). Additional regions that hold a synchronised copy, billed per replicated region.

Every zone is created with a pull zone attached, which is what serves its contents publicly. You do not need to configure an origin — the storage zone is the origin.

Regions

Region	Code	S3 access
Frankfurt, DE	`DE`	Yes
London, UK	`UK`	Yes
Stockholm, SE	`SE`	Yes
New York, US	`NY`	Yes
Los Angeles, US	`LA`	Yes
Singapore, SG	`SG`	Yes
Sydney, AU	`SYD`	Yes
São Paulo, BR	`BR`	No
Johannesburg, ZA	`JH`	Yes

Region matters for more than latency: it determines your hostnames. A zone in Frankfurt is not reachable at a New York endpoint.

Getting files in

There are four ways to upload, and they all write to the same objects:

The dashboard. Drag and drop into the file browser on the zone's page — fine for one-off files.

S3 SDKs and tools. The usual choice for programmatic use. See the S3-compatible API.

The native Storage API. A simple HTTP API. See Storage API & FTP.

FTP. Useful with existing clients and legacy tooling.

Getting files out

Do not serve public traffic from the storage or S3 endpoints. Those are management interfaces, they require credentials, and they are not distributed to the edge.