Your Anycast CDN generates, caches and delivers image variants on request, while your origin keeps a single master file. Ask for a size in the URL and the edge does the rest.
Powered by the imgproxy processing server · Generated variants are cached at the edge like any other object · Engineer reply within 3 business hours
Your origin stores one file. The CDN generates, caches and delivers every variant from a query string on your own domain.
Source file, 1376 x 768
resizefit, width 800
resizefit, width 480
https://cdn.example.com/images/photo.jpg?preset=resizefill&width=1200&height=1000
Ask for a variant in the URL. The CDN generates it once, caches it at the edge and serves every later request from there.
https:///?preset=&
Your CDN domain: the deployed server, domain or IP that answers the request.
Where the original lives on your origin or bucket. The master file itself is never modified.
The preset name and its parameters, passed as query-string pairs separated by ampersands.
Example: ?preset=resizefill&width=800&height=600 returns a copy of the image that fills an exact 800 x 600 box. If the source has a different aspect ratio, it is scaled and then cropped, so the output always has the dimensions you asked for.
crop:$arg_width:$arg_height:$arg_gravity resize:$arg_type:$arg_width:$arg_height resize:fit:$arg_width:$arg_height resize:fill:$arg_width:$arg_height Image Processing is switched on for a resource location, not for the whole account, so you decide where variants are generated.
In the user panel, open the CDN resource that serves your images.
Click Image Processing to enable the parameter. The configuration page unfolds right there.
Add a preset and its parameters to any image URL on your CDN domain. The first request generates the variant, the rest are served from cache.