AIO
Format delivery
Optimized delivery goes through a dedicated endpoint that reads the request's Accept header and re-encodes the image on the fly, so the same source image can serve AVIF, WebP, or the original format depending on the browser.
How it works
- Width (w), format, and quality (q) are passed as query parameters on the optimized-image URL
- The response honors the request's Accept header to choose the best supported format
- Responses are sent with TTL headers tuned for caching, and an authenticated request also records a cache record
Good to know
- Rewriting into the optimized-image URL only happens for images matched by the domain's deployed preset
- This runs through the backend's image pipeline — the frontend never performs image processing itself