Running on Cloudinary?

Cloudinary transforms misbehaving or bill climbing? We bring it back.

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.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

cloudinary-upload.log

still broken

What it is

Cloudinary at a glance

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.

Type
Media management, transformation, and delivery platform
First released
2012
License
Proprietary SaaS, credit-based pricing
Maintained by
Cloudinary, Ltd.
Typically used for
Product images, hero images, user-generated uploads, video delivery, DAM

The honest version

Cloudinary pros and cons

No technology is all upside. This is where Cloudinary earns its place and where it tends to cause trouble.

Where Cloudinary is strong

  • URL-based transformations are genuinely powerfulCrop, resize, format, quality, overlay and watermark are all URL parameters, which means marketing can iterate without a deploy and front-end code can request exactly the variant it needs.
  • Auto format and auto quality save real bandwidthf_auto and q_auto will serve WebP or AVIF to supported browsers at a sensible quality, which is the single highest-value setting most sites never enable.
  • Video transcoding without a pipelineHLS, MP4 renditions and adaptive bitrate are available from the same URL API, which saves building a FFmpeg pipeline and CDN integration from scratch.
  • Decent DAM featuresTags, metadata, folders, structured metadata and search let marketing teams run it as a real digital asset manager rather than a dumping ground.
  • SDKs cover the real client surfaceReact, Vue, iOS, Android and the common server languages have official SDKs that include signed uploads, so most of the security-critical plumbing is already written.

Where Cloudinary bites

  • Bills can spiral through URL variantsEach new transformation combination is a new derived asset. A design tweak that changes 'w_400,h_400' to 'w_500,h_500' can quietly double the derived asset count overnight.
  • Unsigned upload presets are a security hazardAn unsigned preset on the public web is an open invitation for anyone to upload arbitrary content to your account, and teams discover this when the storage bill or an abuse report arrives.
  • Transformation chains get unreadable fastPast a few steps the URL becomes a dense comma-separated string that nobody wants to touch, and the eager vs on-the-fly distinction confuses new engineers for months.
  • Vendor lock-in on URL formatTransformations encoded in URLs do not port to Imgix, imgproxy or self-hosted ImageMagick in any straight way, so changing providers means rewriting URLs across the site.
  • Cold uploads are slow for large videosDirect-to-Cloudinary uploads for multi-gigabyte video files can time out from the browser without a resumable chunked upload setup, which is not the default.
  • Delivered assets are sometimes third partyUser-uploaded images sit in Cloudinary, and some compliance regimes want media inside a provider or region you control, which is a conversation worth having early.

Sound familiar?

Common Cloudinary problems we fix

The Cloudinary problems that bring people to us, and what you have once each one is fixed.

transformations 118,220 / 100,000

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

upload preset allows unsigned uploads

An unsigned upload preset is exposed

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

Invalid Signature

Signed uploads keep failing

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

insufficient memory 240MB source

Large source images fail to transform

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

bandwidth 4.2 TB / 3 TB

Bandwidth is over plan

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

Rate limited on /image/upload

Bulk uploads trip the rate limit

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

chained transformation length 12

Transformation chains are too long

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

Cannot decode image

Some uploads come in corrupted

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

Cloudinary help, from presets to pipelines

Hire us for one failing preset, or let us run the entire media stack.

Rescue
Transformations failing, presets exposed, or the bill several times its normal size. We stabilize the account first and then show you what was driving the usage.
Upload security
Signed presets, scoped API keys, server-side signature generation and client integrations that cannot be abused by an inspector-wielding visitor.
Transformation strategy
A smaller set of base variants, aggressive f_auto and q_auto usage, and eager transformations for the shapes that every page needs, so on-the-fly counts fall.
Bandwidth and CDN
Cache headers, named transformations, and a delivery configuration that cooperates with upstream CDNs rather than bypassing them on every request.
Migrations
Moving onto Cloudinary from S3 and ImageMagick, or off Cloudinary onto Imgix or self-hosted imgproxy, including URL rewriting across the front end.
Managed Tech
Ongoing coverage: we watch credit usage, bandwidth, failed uploads and preset exposure, and respond when the numbers drift the wrong way.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Cloudinary alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Cloudinary questions

Something else? Call+1 737 727 7327

Why is our Cloudinary bill climbing every month?

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.

Someone is uploading junk to our Cloudinary account, how did that happen?

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.

Should we use Cloudinary, Imgix, or self-host?

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.

How do we stop transformation counts from exploding?

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.

Can you migrate us from S3 and ImageMagick to Cloudinary?

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.

How much does Cloudinary help cost?

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

Cloudinary giving you trouble?

Tell us how the account is wired up and what is going wrong and we come back with a plan and a price.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.