Image transforms
w, h, fit, q, fm, auto=format and dpr are served. Hotspot rectangles, blur, sharpen, rect, palette and LQIP are not — and are ignored rather than approximated.
Images are served from your own deployment and transformed through the platform's image optimisation.
/images/default/production/<asset>.png?w=800&fit=max&auto=formatSupported
| Parameter | Meaning |
|---|---|
w, h | Target width and height |
fit | How the image fills the box |
q | Quality |
fm, auto=format | Output format, or negotiate one |
dpr | Device pixel ratio |
Not supported
Hotspot and crop rectangles, blur, sharpen, flip, rect, palette extraction and LQIP. They are ignored, not approximated, and this page exists so that is documented rather than discovered.
Hotspot data is still stored on the image field, so a frontend can use it for CSS object-position — the platform simply does not crop server-side from it.
Responsive images without double-billing
Build a srcset from the width ladder and let the browser choose:
<img
src={url(asset, { w: 1200 })}
srcSet={ladder.map((w) => `${url(asset, { w })} ${w}w`).join(', ')}
sizes="(min-width: 60rem) 56rem, 100vw"
alt={alt}
/>Do not wrap these URLs in a framework image component as well. The route already redirects into image optimisation, so wrapping it optimises an already-optimised source — two billed transformations per image, for no gain.