Skip to content
CDN

Edge Cache

Pin it once. Serve it even when your origin can't.

Edge Cache stores your most important files permanently at all 988 locations. They never expire, never get evicted, and keep serving if your origin goes dark.
Start freeHow it works

Included with every CDN plan at no extra cost.

Hit rate on pinned files
100%
Origin requests for them
0
Locations holding a copy
988
Extra cost
$0

How it works

Three steps, then nothing to maintain

A normal cache is a guess about what visitors will ask for next. Edge Cache is a promise: these files are always there.
  1. 01

    Upload once

    Push static assets from the dashboard or the API. Versioned filenames work best.
  2. 02

    Replicate everywhere

    Each file is stored at all 988 locations, not fetched on demand the first time someone asks.
  3. 03

    Serve from the edge, always

    Requests are answered at the nearest location, whether your origin is healthy, slow or offline.

Why pin instead of cache

No expiry, no eviction, no cold misses

Standard caches drop objects when a TTL runs out or a node needs the space, and the next visitor waits for your origin. Pinned files skip that cycle entirely.
  • Every request for a pinned file is a hit
  • Your origin is never asked for it again
  • No limit on how much you pin

Configuration

Pair it with long TTLs and versioned names

Give everything else sensible cache rules too. Long-lived, fingerprinted assets get a year; HTML stays fresh; APIs pass straight through. When a file changes, ship a new name and purge the old one.
Caching docs
deployment config · caching
{
  "caching": {
    "defaultTtl": 86400,
    "respectOriginHeaders": true,
    "rules": [
      { "path": "/static/**", "ttl": 31536000 },
      { "path": "/*.html",    "ttl": 300 },
      { "path": "/api/**",    "bypassCache": true }
    ]
  }
}

Perfect for

Files that shouldn't depend on a server

If losing it for five minutes would break something, pin it.

  • Static websites

    Marketing sites and landing pages that stay up through origin maintenance.

  • JavaScript libraries

    Bundles and vendor chunks that every page depends on.

  • CSS frameworks

    Stylesheets that should never flash unstyled.

  • Media assets

    Hero images, product shots and video posters.

  • Software downloads

    Installers and release binaries on launch day.

  • Game assets

    Patches and asset packs pulled by thousands of clients at once.

  • Documentation

    Docs that must load while you're fixing the incident they describe.

  • Fonts & icons

    Small, shared, requested on every page view.

FAQ

Edge Cache, explained

How is this different from a long cache TTL?
A TTL is a maximum, not a guarantee. Nodes still evict cold objects to make room, and each location fills its cache on the first request. Edge Cache stores the file at every location up front and never evicts it.
What happens if my origin goes down?
Pinned files keep serving from the edge as normal. Anything that isn't pinned or cached falls back to your origin as usual, so pin the files your pages can't render without.
How do I update a pinned file?
Upload the new version under a new, versioned filename and update your references. That gives you instant rollback, too. You can also purge a path when you need to remove something.
Is there a storage limit?
No. There's no cap on how much you pin, and no extra charge for it. Edge Cache is included with every CDN plan.
Can I pin dynamic content?
Edge Cache is for static files. Personalised pages and API responses should use normal cache rules or bypass the cache.

Make your origin optional

Pin the files your site can't live without and let the edge carry them, on the free tier and every plan above it.

Start freeAll CDN features

Free tier: 3 deployments and 500k requests a month, hard-capped. Bandwidth is always $0.