Transformation credits are over plan
Every URL variant is a new derived asset, and a design update that shifted sizes created an entire new set of transformations across the catalog overnight.
Transformation strategy consolidated
Running on Cloudinary?
Cloudinary quietly turns from a convenience into a cost center the moment a transformation chain is applied to every request, a signed upload gets replaced with an unsigned preset, or a bot discovers that your image URLs are a free compute endpoint. We go through the transformations, the presets and the CDN settings until the right picture ships at the right price.
What it is
Cloudinary is a cloud-based media platform founded in 2012. It stores images, video, documents and 3D models, applies transformations on-the-fly through its URL API, and delivers the output through its own CDN. Teams typically adopt it so marketing can crop and resize without a deploy, and engineers can forget about ImageMagick entirely.
Pricing combines storage, bandwidth, and 'transformations' (any derived asset the service builds on-demand). The URL API is both its strength and its danger: a crop added to the URL by a developer becomes a billable derived asset, and every client that caches that URL variant adds to the transformation count until the CDN edge decides to serve it from cache.
The honest version
No technology is all upside. This is where Cloudinary earns its place and where it tends to cause trouble.
Sound familiar?
The Cloudinary problems that bring people to us, and what you have once each one is fixed.
Every URL variant is a new derived asset, and a design update that shifted sizes created an entire new set of transformations across the catalog overnight.
Transformation strategy consolidated
A preset originally built for a demo environment that has been serving public uploads from the production site, letting anyone put content into your account.
Presets signed and scoped per use
A client computing the signature over different parameters than the server, usually after a parameter was added on one side and not the other, so every upload 401s.
Signature inputs matched on both sides
A product photographer uploading 40-megapixel originals, and Cloudinary refusing to run a complex transformation chain on a source past its memory ceiling.
Sources preprocessed to usable sizes
f_auto and q_auto never enabled, oversize images shipped to mobile, and the CDN cache not configured aggressively enough for immutable derived URLs.
Auto format and cache headers in place
A migration script importing a million assets in parallel threads, hitting the account's write rate limit, and partially populating folders while the script logs success.
Uploads paced, retries idempotent
Years of accumulated overlays, crops and effects on a single URL, slowing first-render and nudging close to the API's practical limit.
Chains simplified and baked into base variants
User uploads with content types that lie about the real file, or EXIF headers that confuse the decoder, so the asset lands in storage but never renders.
Validation on the client and server
What we do
Hire us for one failing preset, or let us run the entire media stack.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Usually a combination of too many URL variants, no q_auto or f_auto in the delivery URLs, and CDN caches that cannot keep up with how many derived assets exist. We audit the transformation and bandwidth lines separately, identify the two or three worst offenders, and cut them back without changing the on-screen result.
Almost always an unsigned upload preset that was built for a demo and left live in production. Rotate the preset, make it signed, require authentication for the signature endpoint on your server, and set a folder and tag restriction on the preset so even a replay cannot drop assets anywhere interesting.
Cloudinary is the broadest product (DAM, video, transformations, delivery) and the most expensive. Imgix is a tighter transformation and delivery layer and tends to be cheaper for pure image delivery. Self-hosting with imgproxy on a CDN is the cheapest and most work. We help model the real cost including engineering time before picking a direction.
Reduce the number of URL variants the site generates, name the ones you keep so they share the same derived asset across pages, use eager transformations for the shapes every page needs, and add aggressive CDN caching with far-future immutable URLs. Those four together usually cut the on-the-fly count by a large fraction.
Yes. The move is more than a bulk upload: we audit the current transformations, map them to Cloudinary equivalents, build a URL rewriter for existing references, and run both sources in parallel until the Cloudinary origin matches what the old pipeline produced. For large libraries we also parallelize the upload with proper rate limits.
The estimate is free. Tell us how the account is set up and what is misbehaving and we come back with a price before any work starts.
Free estimate
Tell us how the account is wired up and what is going wrong and we come back with a plan and a price.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: