Measured in your browserWe advise on speed. We practice it.Loaded just now · real numbers from this visit, not a lab score.
Page loaded
First byte
DOM ready
First paint
Largest paint
DNS lookup
TLS handshake
Transferred
Saved by compression
Requests

Cloudinary, imgix, ImageKit and the CDN-native optimizers, run through the four questions that decide image platform bills: meter, catalogue, workflow, exit.

The verdict, up front

Winner depends on your workload.

Winner depends on: which meter your catalogue trips. Bandwidth-metered (ImageKit) suits big catalogues with concentrated traffic; credit-blended (Cloudinary from $89 Plus, imgix from $25) buys platform breadth at opaque unit costs; per-transform (Cloudflare Images) rewards small catalogues; flat-fee CDN-native (Bunny Optimizer, $9.50/zone) wins wherever it covers the requirement.

Four meters, one catalogue

Dedicated image platforms all resize, crop, and convert to WebP/AVIF competently; the four-way divergence is what they count. ImageKit meters bandwidth — origin-image count and transformations are free variables, delivered gigabytes are the bill, from a free 20 GB/month tier through paid plans starting in single digits. Cloudinary meters a blended credit (storage, transformations and bandwidth draw from one pool — 25 free credits, then the Plus plan at $89/month for 225), which buys the deepest platform in the field at the least predictable unit cost. imgix meters credits too, weighted toward origin images and usage, with the cheapest paid entry (~$25/month) and a model that consumes credits even on large, quiet libraries. And the CDN-native tier — the products we broke down in the image add-ons matrix — meters per unique transform (Cloudflare Images) or not at all (Bunny Optimizer's flat $9.50 per zone).

PlatformMeterWhere the bill bends
CloudinaryBlended credits (storage + transforms + bandwidth); Plus $89/mo, next tier a steep step upCatalogue growth consumes storage credits even without traffic; the pool obscures which dimension is eating the plan
imgixCredits weighted to origin images and access; paid from ~$25/mo, free tier of 1,000 origin imagesLarge libraries with light traffic still burn credits; heavy users climb tiers quickly
ImageKitBandwidth; free 20 GB/mo, paid from $9/mo, unlimited transforms, published overage ratesTraffic spikes are the whole bill; free tier hard-stops delivery when exceeded mid-month
Cloudflare ImagesPer unique transform (5,000 free, then $0.50/1,000) plus hosted storage/delivery metersResponsive-variant explosion on big catalogues; hard 9422 failures at the free ceiling
Bunny OptimizerFlat $9.50/month per pull zone, unlimited transforms; delivery at normal CDN ratesPer-site linearity for agencies; feature surface is optimizer, not DAM

The workflow question is the real differentiator

Meters decide the bill; workflow decides who should be on the shortlist at all. Cloudinary is a media platform — upload APIs, a genuine DAM layer, video processing, AI tagging — and teams that use that breadth get value the per-image math misses. ImageKit sits in the developer middle: upload APIs, a media library, URL transforms, without the full DAM ambition. imgix is a delivery-and-transform engine that expects your storage to exist already. The CDN-native optimizers assume the simplest workflow of all: images live at your origin, URLs stay the same, the edge just makes them smaller. Buy the workflow you will actually operate; every unused platform layer is margin you are donating.

Run the four-way test

Take your real numbers — distinct originals, variants per original, monthly delivered GB, traffic concentration — and price all four meters. The pattern that emerges in nearly every audit: bandwidth meters win when traffic concentrates on few images; per-transform meters win when catalogues are small; credit platforms win only when the platform features are genuinely in use; flat-fee wins everywhere it covers the requirement, which is more often than the feature-checklist suggests — the conclusion our specialist head-to-head reached from the other direction. Then check the exit: URL schemes and named transforms are the lock-in layer, so prefer platforms whose transformation URLs you could re-implement on a programmable edge in a sprint. Facts and prices verified against provider documentation, July 2026.

Want all four meters priced on your actual catalogue and traffic shape before you commit? That's the assessment.

Get the free assessmentMore analysis