Features

CDN Delivery

Every file you upload is instantly cached at 200+ edge locations worldwide.

⚡

Sub-50ms

Global latency

200+ edge locations across 6 continents

🛡️

10+ Tbps

DDoS protection

Edge-level scrubbing, always on

📡

99.99%

Uptime SLA

Multi-region redundancy with auto-failover

🔄

<300ms

Global cache purge

Invalidations propagate worldwide instantly

How CDN delivery works

When you upload a file to CDNZero, it is stored in a redundant multi-cloud object store and automatically replicated to the nearest edge caches. The first request for a file from a given region is served from origin; all subsequent requests hit the edge cache — typically within 30–50ms of the user.

Public files

Files in a Public collection are accessible via a direct CDN URL — no authentication required. Share the URL anywhere: in an <img> tag, CSS background, video player, or download link.

html

<img src="https://cdn.cdnzero.com/my-org/hero-image.png" alt="Hero" />

Private files & Signed URLs

Files in a Private collection require a time-limited signed URL. You generate this server-side using your Secret Key — the client never sees your API credentials.

CDNZero Playground showing files — Playground — private files (lock icon) and public files (globe icon) side by side

Generate a signed URL

curl -X POST https://api.cdnzero.com/collections/create-link \
  -H "Authorization: Bearer YOUR_ACCESS_KEY" \
  -d '{"file_id":"file_xyz","file_type":"image","expiry":3600}'
# Returns: { "presigned_url": "https://cdn.cdnzero.com/...?sig=..." }

Cache purging

When you update or delete a file in the Playground or via API, CDNZero automatically issues a cache purge that propagates to all edge locations in under 300ms. You don't need to manage cache invalidations manually.

For immutable assets (versioned JS/CSS bundles, generated images), use Public visibility with long cache TTLs. For user-specific or frequently-updated content, use Private with signed URLs.