CDN - Transformation - Pricing
We have signed up for the Transformation for our images. If we set a size for an image and post this CDN link vis GitHub and other people fork this repository, will the forks eat up the 2K transformation allotment?
8 Replies
Because it's in the readme.md and being loaded? Or, what am I missing?
The new way Image Transformations are billed is by unique transformations, so if it's the same size/settings it's the same cost for 1 vs 1 million transforms. So even if it's in the readme.md or embedded in the app deployed or something, it'd be more requests but not necessarily same cost if same settings
Hello! Yes, it would be in the readme.md. And the size would be the same. And do you mean if people take our repostory, fork it, the cost will stay the same and we will be charged once or do we get charged for ever fork?
You're only billed per unique transformation per month on the latest plan like I said, so if they're forking it and using the same resizing link with the same settings, it'd still be just one unique transformation regardless of request count
So caching wont matter in this case?
Correct, caching will happen with image resizing but it's separate from billing
Perfect! I do have one more question, but not sure if this needs it's own sperate post, but how do we avoid people abusing our links and changing the sizes?
it's fine to have it in here.
There's a few options, one is using Cloudflare Workers with resizing to force your resizing params (but need to pay for each cf worker request still)
or you can use the Cloudflare WAF/Custom Rules optionally with Transform Rules to have special paths like this: https://developers.cloudflare.com/images/transform-images/serve-images-custom-paths/
Cloudflare Docs
Serve images from custom paths · Cloudflare Image Optimization docs
You can use Transform Rules to rewrite URLs for every image that you transform through Images.
Perfect! I will look this over. Thank you for all of your help. 🙂