Upload once, request any size from a template

ImageWorks is the image processing engine inside Total CMS. You upload one original, and every size and format a template needs is produced from it on request by passing a parameter array to cms.media.imagePath(), cms.media.galleryPath() or cms.render.image(). Transformed images are cached on disk, and when the source image changes the cached versions regenerate on the next request.

Resizing takes w, h, dpr and a fit mode. contain fits inside the box, max does the same without upscaling, fill fills and crops as needed, stretch distorts to exact dimensions, and crop crops to them. crop-{position} anchors the crop to one of nine positions, and crop-focalpoint crops around the focal point an editor set on that image in the admin — which is how a portrait survives being cropped into a wide banner.

Format and quality are fm and q: JPEG, PNG, GIF, WebP or AVIF, at whatever quality you name. Alongside them sit effects and adjustments — blur, sharpen, pixelate, a greyscale or sepia filter, brightness, contrast and gamma — plus borders, flipping and orientation. Every image also carries an automatically extracted palette of up to five colours, referenced as palette0 through palette4 in the border and bg parameters, so a letterboxed image can sit on its own dominant colour.

Repetition belongs in configuration rather than in your templates. imageworks.defaults in tcms.php applies parameters to every transformation on the site — set the format to WebP and the quality to 85 once, and everything is served that way, with anything passed in a template still winning. imageworks.presets names reusable parameter sets, called with {p: 'thumbnail'} and overridable inline, and a preset whose fit is crop-focalpoint uses each image's own focal point automatically.

In practice a card grid asks for {p: 'thumbnail'}, the article header asks for a 1600-pixel WebP, and the social share image asks for a hard 1200 by 630 crop — all three from the same upload, each one cached after its first request. They are served from the public /imageworks/ endpoint, though you rarely need to build one of those URLs by hand.