C
if in the next month I add only 10,000 images in the server and request another 10,000 unique resize, the bill will add the 1,000,000 done in the previous month or just the 10,000?The blog post details that:
With the new Cloudflare Images, you will be billed only once per 30 days for each unique request to transform an image stored outside of Cloudflare, whether or not the transformation is cached. Customers will be billed $0.50 per 1,000 unique transformations per month.The unique transforms is per month. If you do 1 mil unique transforms per month, you'd get billed each month for one mil unique resizing. Regardless if each month those were the same unique transforms or different.
And also there are costs for traffic/requests for each imageNo additional cost from Image Resizing, but you may be charged extra by your real storage provider. For example, the unique transform doesn't mean your origin will only get pulled once per month. Uncached requests will still cause an origin fetch to transform the image again. So if your origin was R2 for example, you'd see some amount more R2 GetObjects with more requests, but Image Resizing would still just be per unique transformations
Last thing if I decide to move the images to Cloudflare storage, the bill come with 50 dollars extra each month for storageImages has its own pricing
Sources: https://developers.cloudflare.com/images/faq/
- $5 per month per 100k images stored
- $1 per month per 100k images delivered
Cloudflare Images - Cloudflare charges by images served (regardless of them being cached or not), and images stored.
https://developers.cloudflare.com/images/pricing/
Below you will find answers to our most commonly asked questions regarding Cloudflare Image Optimization, namely the differences between Cloudflare …
For more information on how you can save costs by increasing caching in browsers, refer to Browser TTL.
CSure, yea that's a lot of images to transform every month. An alterative may be to resize them yourself (or via Image Resizing, once) and shove the resized version into R2, and serve from via an R2 Custom Domain. Less dynamic options/more initial work on upload, but less costly over time
CR2 is Cloudflare's S3-Compatiable Object Storage
The main benefit of it is no egress costs
https://developers.cloudflare.com/r2/pricing/
$0.015 / GB-month and $0.36 / million requests per class B Operations (10 mil included, GetObjects are Class Bs)
The main benefit of it is no egress costs
https://developers.cloudflare.com/r2/pricing/
$0.015 / GB-month and $0.36 / million requests per class B Operations (10 mil included, GetObjects are Class Bs)
R2 charges based on the total volume of data stored, along with two classes of operations on that data:
C500 GB would be like 0.015 * 500 = $7.5/month. That's just storage, not including the Class Bs for serving the images. If it was a 100 mil images served a month, minus the 10 mil included for free, you'd be looking at 0.36 * 90 = ~32.4/month
CThere's a few calculators out there as well;
https://r2-calculator.cloudflare.com/
https://pricing.ceru.dev/r2
https://r2-calculator.cloudflare.com/
https://pricing.ceru.dev/r2
CIt might be a bit cheaper then that in Class Bs, if you use an R2 Custom Domain you can use the CDN Cache, and any cache hits isn't a Class B Cost, but that's much harder to predict as you only get the per cloudflare location cache (and CF has some 350+), and it depends on how frequently the image is accessed/how long it stays in cache, etc.
Ironically that's the same reason why they said the new Image Resizing pricing is better -- don't have to worry about if something will be cached or not. In this situation though I would just plan for every hit to be uncached in initial pricing and as you go see how many hit cache
Ironically that's the same reason why they said the new Image Resizing pricing is better -- don't have to worry about if something will be cached or not. In this situation though I would just plan for every hit to be uncached in initial pricing and as you go see how many hit cache
CSure, worth keeping in mind too with R2 you pay for uploading images/objects, those are Class As. You get a million included though per month
it doesn't make a lot of sense to rebill the same resized image each monteh, from CF's point of view, they aren't infinitely storing the resized image like you would with R2, they resize it every time cache expires, charging once and doing the same operation potentially millions of times for free forever doesn't sound like a good business idea lol. Monthly is already an interesting change to prevent people from needing to put images into R2, but doing it yourself with R2 will still be cheaper
CCouldn't Cache Reserve help with expiry prevention, though, if that was enabled?
