A feature rich, scalable and well priced alternative to most image CDN's
December 17, 2021

A feature rich, scalable and well priced alternative to most image CDN's

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Cloudimage

We were using another image CDN provider (not European) and really did not find a compelling offer from them after their huge price hike. Trying to go with a fast but European based provider, we found Cloudimage (French) to be very professional, with good onboarding, [and] plenty of precise settings to bend their solution to our exact needs. Cloudimage is very fast, pricing is based on real metrics, not arbitrary amounts. Support is reactive and friendly. Upgrades are detailed in blog posts every month.
  • Great world-wide CDN
  • Excellent image quality with extensive processing options
  • Competitive pricing with progressive tiers
  • Good defaults but well organized interface to configure everything precisely
  • Having tiers based either more on source cache / CDN bandwidth (for some persons)
  • Images can come from any source, and this source is always hidden
  • Processing scales very well (you can reset cache and have images regenerated quickly)
  • Processing, watermarking, protecting, is precise and fast
  • Same or lower cost as before and more possibilities than before
  • Using a GDPR respecting, European (French) based company
  • Using more features like watermarking, fallback image, precise 404 handling
We don't like the new pricing scheme for imgix at all. We could have gone from 100 USD / month to 500 USD / month because they price based on source image (we had 50, 000). With Cloudimage, the pricing is based on source image cache (gigabytes) and CDN bandwidth (gigabytes).

Do you think Cloudimage delivers good value for the price?


Are you happy with Cloudimage's feature set?


Did Cloudimage live up to sales and marketing promises?


Did implementation of Cloudimage go as expected?


Would you buy Cloudimage again?


Use it if you have a ton of source images and need many transformations.

Don't use it if you only want to serve a few image[s] to a very very large number of users (CDN bandwidth costs)