This is how auto-WebP feature works at Statically (multi-CDN edition)

This aims to provide insights into how the WebP conversion feature works at Statically:

  • Fastly: will send WebP if accept: image/webp header present no matter what, even if the image gets large (yes, converting JPG to WebP can result in a large file size)
  • BunnyCDN: same as Fastly
  • Cloudflare: will check the WebP file size is larger than the original image, if not, then send

I personally prefer the approach applied in Cloudflare, because it’s faster, therefore a larger portion of the traffic is currently going to Cloudflare, they also provide more PoPs for Statically. You can check the DNS resolutions for from around the world at and see what you got.

WebP is great, but the web is getting modern, modern solutions have to be made, edge logic is getting more advanced and static asset delivery has to be smarter. Serve WebP only when it is useful to serve.

Again, this is a challenge running the auto-WebP service with a multi-CDN and this is what we can make.

I hope this can answers when you are wondering why the WebP versions of the images are not presented.

Looking forward for the AVIF image type support too in the future.

1 Like

Yeah, I just read about AVIF on some blog today.

Does anybody have an AVIF image dataset that I can test?