CDN & Caching

Your documentation needs to load fast. Reshot delivers assets through a high-performance global network.

Coverage baselines — On Team+, every approved baseline in Coverage has a stable pointer — approving a newer capture makes the same URL serve it, with no code change.

Immutable per-version URLs are available on every plan. The always-fresh pointer that follows the latest approved baseline is a Team, Scale, and Enterprise feature.

Architecture

Edge Caching

Requests hit our edge network first. If the image is cached, it's served in milliseconds.

Smart Routing

If the cache is stale (you just approved a new version), we route through our high-speed Redis layer to find the new image path immediately.

Instant Invalidation

On Team+, when you click "Approve" in the dashboard, we invalidate the old approved-baseline pointer. Immutable per-version URLs never change.

Global Coverage

Assets are served from edge locations worldwide:

Region	Locations
North America	US East, US West, Canada
Europe	UK, Germany, France, Netherlands
Asia Pacific	Singapore, Tokyo, Sydney, Seoul
South America	São Paulo

Performance

Metric	Target
Cache Hit Latency	< 50ms
Cache Miss Latency	< 200ms
Invalidation Time	< 1 second
Uptime	99.9%

Cache Behavior

Default Cache

Assets are cached at the edge for 24 hours by default.

On approval (Team+ pointers)

When you approve a new version:

CDN cache is purged globally (< 1 second)
Next request fetches the new image
New image is cached at all edges

Cache Headers

Assets are served with appropriate headers:

Text

Cache-Control: public, max-age=86400
ETag: "abc123..."

Using with Your Own CDN

If you're using BYOS with S3 or R2, you can put your own CDN (Cloudflare, CloudFront) in front:

JSON

{
  "storage": {
    "type": "s3",
    "bucket": "my-assets",
    "publicDomain": "https://cdn.mycompany.com"
  }
}