Cheapest CDN as delivery bandwidth grows
Transformations, storage and billing term held at your current inputs β only monthly delivery bandwidth changes per row. Watch ImageKit stay cheap at low volume (transformations are free), imgix win the middle and high end on cheap overage, and Cloudinary get pushed to an Enterprise quote past 600 combined credits.
| Bandwidth GB/mo | Cloudinary | imgix | ImageKit | Cheapest |
|---|
Why shared-credit-pool, credit+overage and bandwidth-only billing shapes matter
Cloudinary, imgix and ImageKit don't compete on a single sticker price β each meters image delivery along a different dimension. Cloudinary pools bandwidth, storage and transformations into one credit: 1 credit = 1,000 transformations, 1GB of storage or 1GB of image bandwidth. Its self-serve tiers are Free (25 credits, $0), Plus (225 credits, $99/mo or $89/mo annual) and Advanced (600 credits, $249/mo or $224/mo annual) β and crucially, none of the self-serve plans bill metered overage; exceed your tier's credits and Cloudinary pushes you to upgrade, or past 600 credits/month into a custom-quoted Enterprise plan. imgix uses the same kind of shared credit β its published tiers show a consistent 1 credit β 1GB of delivery bandwidth (Starter's 100 credits caps at exactly 100GB bandwidth, Basic's 375 at 375GB, and so on) β but unlike Cloudinary it sells metered overage on every tier, from $0.25/credit (Starter, monthly) down to $0.12/credit (Growth Plus, monthly), cheaper still on annual billing. ImageKit is structured differently again: its core plans β Free (20GB bandwidth, 3GB DAM storage), Lite ($9/mo, 40GB bandwidth then $0.50/GB, 10GB storage then $0.10/GB) and Pro ($89/mo, 225GB bandwidth then $0.45/GB, 225GB storage then $0.09/GB) β don't meter real-time image transformations (resize, crop, format conversion) at all; those ride along inside your bandwidth allowance for free.
That means the "cheapest" CDN flips hard depending on your bandwidth-to-transformation ratio. A site doing lots of transformations but modest bandwidth β say, generating many thumbnail sizes for a small catalog β tends to favor ImageKit, since Cloudinary and imgix would burn through shared credits on the transformations alone while ImageKit charges nothing extra for them. A site with heavy, steady bandwidth and comparatively few transformations tends to favor imgix, since its overage rate keeps shrinking at scale and it never forces a plan-tier jump or a sales call the way Cloudinary's credit ceiling does. Cloudinary's flat, overage-free tiers suit teams who want a predictable worst-case bill and don't mind upgrading (or negotiating Enterprise pricing) once they outgrow 600 combined credits a month. Run your own bandwidth, transformation and storage numbers above instead of comparing sticker prices.
How this calculator works
The Cloudinary vs imgix vs ImageKit Cost Calculator compares three image-CDN pricing shapes β Cloudinary (shared credit pool, tiered, no metered overage), imgix (shared credit pool with metered overage) and ImageKit (bandwidth/storage-only, unmetered transformations) β at your monthly delivery bandwidth, transformation count and stored image volume. Cloudinary's credits needed is bandwidthGB + storageGB + transformationsK (1 credit = 1,000 transformations = 1GB storage = 1GB image bandwidth); the calculator picks the cheapest tier β Free (25 credits, $0), Plus (225 credits, $89-99/mo) or Advanced (600 credits, $224-249/mo) β that covers that total, or flags "Enterprise (contact sales)" past 600. imgix's credits are modeled 1:1 against delivery bandwidth (matching the ratio published across every imgix tier), with cost planRate + max(0, bandwidthGB β includedCredits) Γ overageRate computed for each of imgix's five tiers (Starter through Growth Plus) and the cheapest one selected automatically. ImageKit's cost is base + max(0, bandwidthGB β includedBandwidth) Γ bandwidthOverageRate + max(0, storageGB β includedStorage) Γ storageOverageRate across Free/Lite/Pro, with transformations excluded entirely since ImageKit's real-time transformation API isn't separately metered on these plans.
These are representative pricing shapes based on each vendor's most recently published rates as of August 2026 (Cloudinary's Free/Plus/Advanced credit tiers and per-credit definition from cloudinary.com/pricing, with overage behavior on self-serve plans cross-checked against third-party pricing trackers since Cloudinary does not publish overage rates for Plus/Advanced; imgix's Starter through Growth Plus tiers, credit allocations and monthly/annual overage rates from imgix.com/pricing; ImageKit's Free/Lite/Pro bandwidth, DAM storage and overage rates from imagekit.io/plans), not live vendor quotes. Cloudinary's exact overage behavior past a tier's credit ceiling and imgix's precise split between bandwidth, storage and transformation credit consumption aren't fully published β treat this as directionally accurate, and always confirm current pricing directly with the vendor before budgeting.
Frequently asked questions
Is Cloudinary or imgix cheaper for a high-traffic site?
imgix is usually cheaper at high, steady bandwidth because its overage rate drops as low as $0.12-0.21 per extra credit (roughly per extra GB) on its top tiers, and you only pay for what you use above your plan. Cloudinary bundles bandwidth, storage and transformations into one shared credit pool with hard tier boundaries β Free (25 credits), Plus (225 credits, $89-99/mo) and Advanced (600 credits, $224-249/mo) β and does not sell metered overage on those self-serve plans, so once you cross 600 combined credits/month you're pushed into a custom Enterprise quote regardless of how far over you are. For a site doing 2,000GB/month of image bandwidth plus 500,000 transformations, imgix's Growth plan lands around $266-320/month while Cloudinary requires an Enterprise conversation.
Why doesn't ImageKit charge for image transformations?
ImageKit bills almost entirely on delivery bandwidth (and DAM storage), not on the number of resize/crop/format-convert operations you run through its URL-based transformation API β those are unlimited as long as the resulting images fit inside your bandwidth allowance. That's a fundamentally different shape from Cloudinary and imgix, which both draw every transformation, GB of storage and GB of bandwidth from the same shared credit pool. For transformation-heavy, bandwidth-light workloads β like generating dozens of thumbnail variants for a small product catalog β ImageKit's Lite plan ($9/mo, 40GB bandwidth included) can undercut both competitors, because Cloudinary and imgix would burn through their credit allowance on the transformations alone.
What happens when I exceed Cloudinary's credit limit?
On Cloudinary's self-serve Free, Plus and Advanced plans, exceeding your monthly credit allowance does not trigger a metered overage bill the way imgix or ImageKit does. Cloudinary instead warns you as you approach the limit and can restrict or disable delivery once you're substantially over, pushing you to upgrade to the next tier (or, past 600 credits/month, into a custom-quoted Enterprise plan). That makes Cloudinary's self-serve pricing predictable β you always know your worst-case bill in advance β but it also means a traffic spike can interrupt image delivery rather than just adding a line item to your invoice, unlike imgix and ImageKit which keep serving and simply bill the overage.
Which image CDN is cheapest: a small blog or an online store?
For a small blog doing roughly 50GB/month of image bandwidth, 10,000 transformations and 5GB of storage, ImageKit's Lite plan is cheapest at about $14/month versus imgix Starter at $25/month and Cloudinary Plus at $99/month (Cloudinary's Free tier's 25-credit cap is too small once transformations are added in). For a larger online store at 2,000GB/month bandwidth, 500,000 transformations and 100GB storage, the ranking flips β imgix's Growth plan (~$266-320/month) beats ImageKit Pro's bandwidth overage (~$888/month) and comfortably beats a Cloudinary Enterprise quote. Run your own numbers above since the crossover point depends heavily on your bandwidth-to-transformation ratio.