Opaque Cloudfare Image Resizing Billing

Developers Images
1

We recently switched from imgIX to Cloudflare Image Resize.

We are using the /cdn-cgi/image/… implementation and it was quick to update all our URLs.

Since Day 1 though, our Billing usage has been going through the roof!
Cloudflare is charging us 17x more Image Resizing Requests compared to imgIX.

  • We don’t have more images than before
  • We are using the same image sizes as before
  • Our traffic is the same as before
  • We checked our Origin cache and it’s properly configured

Unfortunately, it seems there is no way to access the log of recently resized images, which would help to understand on which basis Cloudflare is determining this usage.

Any advice on how to investigate/resolve this? Thanks!

2

I believe, but can’t find any info in the docs, Image Resizing charges per each image served, while ImgIX might not.

You might need to open a ticket with Billing, as we can’t see any info regarding your account.

3

I did but unfortunately I only received a generic answer.

According to the FAQ, you are charged for each “Uncached” Resized Image.

However, what’s not clear is the Caching policy behavior (both at the Origin and by Cloudflare) as well as the Cache re-Validations. And it looks like even though the Origin Image has not changed (nor the resized one), you will constantly be charged again and again.

Without logs (or API access), it’s just pure guess at this point.

4

I bet the caching policy is similar to normal cache, it’s per colo and it doesn’t guarantee forever storage.

One solution would be to manually handle it, putting a Worker saving to R2 and/or the Cache API in front of it. Not the best, but can’t offer more…

5

This topic was automatically closed after 15 days. New replies are no longer allowed.