Cloudflare Images
Cloudflare Images
Role
First link in the family's 3-tier image-CDN fallback chain. Every
<Image> rendered through @chirag127/oriz-kit first attempts to
resolve through Cloudflare Images — co-located with our Pages
deployments, served from the same edge as the originating site, no
extra DNS hop. On 5xx (or transformation error) the kit's wrapper
falls through to wsrv.nl, then to
ImageKit. See
decisions/architecture/image-cdn-fallback-chain.md.
Free tier
- Bundled with the Cloudflare Pages free plan
- Image Resizing + Polish + WebP/AVIF auto-conversion at the edge
- Per-Pages-project quota — no separate billing surface
- All variants reachable at
/cdn-cgi/image/<opts>/<src>URLs
Card / subscription required?
NO. Cloudflare Images on the free Pages plan does not require a
billing method. The paid Cloudflare Images product (the standalone
SKU at imagedelivery.net) is a separate add-on and is not what
we use — we use the Pages-bundled transform endpoint only.
Alternatives
- wsrv.nl — fallback 1 (URL-transform proxy, no auth)
- ImageKit — fallback 2 (20 GB/mo, DAM features)
- Cloudinary — already documented under tooling/cloudinary.md
Swap cost
Low — the Astro <Image> wrapper in @chirag127/oriz-kit owns the
URL composition. Changing primary means swapping one helper.
Why this is our pick
Same edge as our Pages sites, no separate signup, no card. First-link latency is best-in-class because the request never leaves the Cloudflare edge.