Upload About How it Works Limits

How it Works

From the moment you click Upload to the moment someone loads your file - here's what happens.

1

You select a file

Your file is read locally in the browser and sent directly to the CDN API over HTTPS. It goes straight to the Cloudflare edge - no intermediate servers involved.

2

The Worker receives it

A Cloudflare Worker handles the upload at the edge. It assigns a UUID filename, detects the file type, and streams the body directly into R2 object storage - with no cold starts and near-instant response times.

3

R2 stores it permanently

The file is written to Cloudflare R2 - S3-compatible storage with zero egress fees and 11 nines of durability. Upload metadata is logged to D1 (Cloudflare's edge SQL database) to track stats.

4

You get a public URL

A permanent public-cdn.madebydanny.uk link is returned instantly. Anyone with it can access the file - served from whichever Cloudflare PoP is closest to them.

310+ Edge Locations

Files are cached and served globally - sub-50ms for most users regardless of where they are.

R2 Object Storage

Zero egress fees, no expiry. Files are stored in Cloudflare R2 with enterprise-grade durability.

Zero Cold Starts

Workers run at the edge with no spin-up delay - every upload and file request is handled immediately.