Skip to main content
Image Optimizer transforms images on the fly at the edge: resize, format conversion (WebP / AVIF), quality, crop, and more. You ship one master file to your origin and the CDN serves the perfect variant per device.

​
How it works

The query string is part of the cache key, so each variant is cached independently after the first miss.

​
Enable Image Optimizer

Image Optimizer

Turn on Image Optimizer

Click Turn on Image Optimizer. Once active:
Image Optimizer Active

Image Optimizer in Action

The status flips to Image Optimizer is Active. Transforms work immediately on any image path on this distribution.

​
URL-based transforms

Append query parameters to any image URL. Combine freely:
format=auto picks WebP / AVIF based on Accept header; falls back to the original.

​
Recipes

​
Responsive image

​
Avatar thumbnail

​
High-DPI screen

​
Verify a transform

Expected:

​
Framework integration

Drop straight into your front-end framework. Per-framework guides:

​
Turn off

Image Optimizer Off

Turn off Image Optimizer

Click Turn Off. The CDN stops transforming and serves the master file as-is. Cached variants stay until they expire — purge /photos/* to flush them immediately.

​
Operational tips

  • Master in a high-quality format — JPEG quality 90 or PNG. Let the optimizer downscale; never upscale.
  • format=auto everywhere — covers AVIF-capable Chrome, WebP for everything else, JPEG for old Safari.
  • Cap width — limit the transform to widths you actually use (sizes attribute). Otherwise attackers can hammer the edge with ?width=N for every N.
  • Watch the cache. Each (width, height, format, quality, dpr, fit) tuple is a separate object. Define a small set in your component layer.
  • Pair with cache rules — long TTLs on /photos/* since transforms are deterministic per query.