WebP and AVIF at the edge: image optimization without a batch job

Convert images to WebP or AVIF and resize at Cloud CDN from one source file, with up to 85% smaller payloads at a given quality.

Most teams still generate derivatives at upload, then ship an overweight original to a phone anyway. Keep one source image. Let Cloud CDN convert, crop and resize at delivery time, then cache each variant at the edge.

One file, many layouts

Product cards, heroes and Open Graph images need different geometry. Query-string resize and crop beat a folder of hand-made widths that lags every new template.

Conversion to WebP or AVIF can save up to 85% at a given quality. Browsers that cannot use AVIF still get a compatible format.

Cache the variant, purge the source

Each derived URL is a cache object on 210+ PoPs. When editors replace the original, purge that source URL so variants rebuild.

Versioned filenames skip purge entirely.

WordPress, Magento and DAM tools

The CMS or DAM remains the source of rights and originals. Cloud CDN is the output layer. You do not need to store WebP next to JPEG unless you already do.

LCP images first

Start with the LCP image on landing pages. A 4000 px JPEG as a 420 px hero is still the common failure, CDN or not.

Frequently Asked Questions

No. Keep a high-quality source. Conversion is a delivery-time choice.

No. A DAM stores rights and originals. Cloud CDN delivers and transforms.

Yes. Balance fidelity against weight per layout instead of one global derivative.

Put this on Cloud CDN.

Get started with our Management Console in less than 2 minutes, or connect with an expert to supercharge your business today.