Image CDN or Self-Hosting for a Large Product Catalogue? A Costed Comparison
Short Answer
For thousands of product photos, the choice depends on how many size variants you need, how often images change and who controls the originals. Count variants first, then price both options on real traffic.
A UAE store with 5,000 products rarely has only 5,000 images. With four photos per product and four display sizes each, it actually has 80,000 image files to create, compress, store and deliver. That number, not the product count, decides whether a dedicated image CDN pays for itself. Most comparisons skip it entirely, and that is where budgets go wrong.
This guide compares two workable approaches for large UAE catalogues. An image CDN transforms and caches pictures on request, while self-hosting generates sizes on your own server and caches them. We use Cloudflare Images' published pricing as a worked example because its rates are public. The same questions apply to any other provider you shortlist, including your platform's built-in tools.
How many image files does a catalogue really need?
Multiply products by photos per product, then by the number of sizes and formats you serve. A product page might need a large zoom image, a gallery size, a thumbnail and a listing card. Serving WebP or AVIF files alongside JPEG multiplies the total once again.
Google's web.dev image course recommends responsive images, so each device downloads a size close to what it displays. That is good for Largest Contentful Paint on mobile, but it creates many variants. Write your real count on paper before comparing any supplier's pricing page.
Quick Answer
A 5,000-product catalogue with four photos and four sizes needs around 80,000 separate image variants. Count products, photos, sizes and file formats carefully before comparing image CDN and self-hosting costs.
What does an image CDN cost for a large catalogue?
Image CDN pricing usually combines three parts: storage, delivery and transformations of each picture. Cloudflare Images' paid plan lists USD 5 per 100,000 images stored and USD 1 per 100,000 images delivered each month. Transformations beyond the first 5,000 unique ones cost USD 0.50 per 1,000.
For 20,000 original photos stored, storage would be about USD 1 a month at those rates. Delivering 500,000 images would add about USD 5. Transformation charges depend on how many unique size and format combinations you request, so estimate them from your variant count.
Quick Answer
Cloudflare Images charges USD 5 per 100,000 images stored, USD 1 per 100,000 delivered and USD 0.50 per 1,000 extra transformations. Model your own catalogue traffic before choosing a plan.
When does self-hosting product images make sense?
Self-hosting works well when your catalogue changes slowly and your team can manage an image pipeline. The server creates every size when a photo is uploaded, and a general CDN caches the files. You pay mainly for storage, bandwidth and developer time.
The hidden cost is ongoing maintenance by a developer. Someone must update compression settings, add new formats and regenerate thousands of files when the design changes size. If your platform already generates responsive images reliably, self-hosting may need nothing extra beyond good caching and a sensible storage plan.
Quick Answer
Self-hosting product images suits slowly changing catalogues where your own server generates image sizes on upload. Budget for storage, bandwidth and developer time to regenerate variants whenever the design changes.
How do image replacements reach shoppers quickly?
Use versioned file names or URLs, so a replaced photo always gets a new address. Caches then fetch the new file immediately instead of serving an old one until expiry. Purging caches manually for every single update is slow, error-prone and easy to forget.
This matters for fashion and electronics stores that swap product photos often. A shopper who sees the wrong colour in a thumbnail may order the wrong item and return it. Ask any supplier to demonstrate how a replaced image appears across listing, product and cart pages.
Quick Answer
Use versioned image URLs so replaced product photos appear immediately without manual cache purges. Test replacements across listing, product and cart pages before committing to any new image delivery option.
How do you avoid lock-in with an image CDN?
Keep your original, full-resolution photos in storage your business controls, not only inside the CDN. If you leave the provider, you can regenerate every variant elsewhere. Also check whether the image URLs stored in your product data depend on the provider's own domain.
Run a small pilot before migrating the whole catalogue to any provider. Move one category, measure page speed on real phones and compare monthly costs for several weeks. Our guide on whether UAE websites need a CDN explains the general caching choices that sit alongside this decision.
Quick Answer
Keep original product photos in storage your business controls, and avoid hard-coding a provider's domain everywhere. Pilot one product category first and compare speed and monthly cost before migrating everything.
Main Takeaways
Count image variants, not products, before choosing between an image CDN and self-hosting. Cloudflare Images lists USD 5 per 100,000 stored and USD 1 per 100,000 delivered, plus extra transformation fees. Self-hosting suits slowly changing catalogues with a reliable, well-maintained image pipeline. Keep originals in storage you control, use versioned URLs for replacements and pilot one category before migrating everything.
Deciding for your catalogue
Start with a simple spreadsheet: products, photos per product, sizes, formats and monthly page views. Price the CDN option from its published rates, then carefully estimate self-hosting storage, bandwidth and developer hours. Compare both options over a full year, not a single month. The cheaper option on paper can become the expensive one once maintenance and developer time are counted.
Our SEO and performance team audits product image delivery and Core Web Vitals for UAE online stores. If your catalogue changes every day, read our comparison of headless versus monolith platforms. Slow loading on mobile phones is covered in why your website is slow on mobile. Send us one product category, and we will measure both options on real phones.
Sources & References
FAQs
Questions readers usually ask next
These FAQs are written to match the topic of this post and to help readers move from understanding to action.
Does a 5,000-product catalogue automatically need an image CDN?
No, the decision depends on variants, traffic and how often product photos change. A well-configured platform with good caching can serve large catalogues without any dedicated image service at all.
Which image formats should an online store serve?
Modern formats such as WebP and AVIF are usually smaller than JPEG at similar quality. Serve them to supporting browsers, and keep a JPEG fallback where your platform needs it.
Can we keep original photos while using an image CDN?
Yes, and you should keep them. Store full-resolution originals in your own storage or backup, so you can regenerate variants or change providers without reshooting products or losing any history.
Should every product photo use the same compression setting?
Not always, since detailed products such as jewellery or fabric may need gentler compression than plain packaging. Test a sample of each product type on phones before applying one setting.
How do product images affect Core Web Vitals?
The main product image is often the Largest Contentful Paint element. Google's web.dev guidance targets 2.5 seconds or less, so correctly sized, compressed images directly affect that score on mobile.
Who should own the image CDN account?
Your business should own the account, billing and storage, with the developer given user access only. That way images keep working if your agency or developer changes in the future.
Should customer uploads use the same image system?
Keep private customer uploads, such as prescriptions or identity documents, separate from public catalogue images. They need access controls that public product delivery systems are simply not designed to provide.
Can we migrate product images gradually?
Yes, move one category at a time, keeping the old URLs working with redirects where needed. That limits risk and lets you compare speed and cost before committing any further.
What should an image optimisation supplier prove?
Ask for before and after file sizes, mobile page speed results and a monthly cost estimate. They should also show how replaced images update and how you would leave later.
How often should image settings be reviewed?
Review them after redesigns, platform upgrades, new product ranges or major catalogue growth. A yearly check of formats, sizes and monthly costs catches waste before it becomes an expensive habit.
Related Resources
Need help deciding whether to keep a platform or go custom?
We help UAE businesses scope the checkout, data model, and integrations before they commit to a stack that is too heavy or too limited.
Built for stores where pricing, inventory, or delivery rules need more control than a default template gives.
